Summary
The Projects page lists a workspace’s projects and is the starting point for everything you do with them: create one, import one from elsewhere, duplicate one to build on existing work. Each project carries a fixed identifier chosen at creation — the one field you cannot change later.
Creating a project
A project needs three things: a name, a description, and an identifier.
The first two can be changed at any time. The third cannot — and it is the one point to watch at creation.
The identifier is permanent
The identifier appears in the project’s address and in its exported tree. It is set at creation and cannot be changed afterwards: 2 to 50 characters, lowercase letters, digits and hyphens. Linkr suggests one from the name; pick something short and stable — mimic-mortality rather than test-project-2.
Starting from an existing project
Starting from scratch is not always the right move.
Import
Bring in a project produced elsewhere, from an archive or a git repository. See Import and export.
Duplicate
Build on a project from the same workspace — useful to run the same analysis over another period or another unit.
An import reports what is wrong
An imported project may contain format anomalies — a broken reference, an unknown column. Linkr imports it anyway and tells you what it found, rather than refusing outright. A project to fix beats an import that fails without explanation.
Finding a project
As projects multiply, two mechanisms help.
- Search filters the list by name.
- Badges are labels you define at workspace level, then attach to projects: a domain, a unit, a funding source. The categories that make sense are yours to choose.
Each project also carries a status, separating work in progress from finished or archived projects.
Actions on a project
From the list, a project can be edited (name, description, badges, status), exported as an archive, versioned to a git repository, or deleted.
Deletion cannot be undone
Deleting a project erases its cohorts, datasets, dashboards and code. If that work has value, export it first — or better, version it.
Going further
- Your first project — the full walkthrough, from creation to dashboard.
- The data pipeline — how data moves inside a project.
- Versioning — tracking a project’s history and sharing it.