For the complete documentation index, see llms.txt. This page is also available as Markdown.
Create a dataset
Create a named reusable cohort from validated assets or Data Groups.
Create the dataset only after the candidate membership has been inspected. The dataset name and description should communicate why the cohort exists—not merely repeat its source folder.
Before you make the change
Confirm the membership question and owner.
Resolve invalid, duplicate, or incomplete grouped items according to policy.
Choose a naming and versioning convention that downstream teams can interpret.
New Dataset dialog with name, description, Folders, Assets, search, and source selection
From Data Space › Datasets, choose New Dataset, name and describe the reusable cohort, then attach the exact Folders or Assets that passed curation. Source count is visible before creation.
Understand the product behavior
The user selects New Dataset.
The user enters a name and optional description.
The user chooses at least one folder or asset from the lazy-loaded, server-searched source picker.
Unitlab creates the mutable working draft.
The dataset detail page opens with its folders and assets.
The user publishes v1 before the dataset can be attached to a project.
Adding files to an existing dataset adds existing workspace folders/assets to the working draft. It is not an upload-directly-into-dataset operation.
Create the reusable membership
1
1. Open New Dataset
Go to Data Space › Datasets and choose New Dataset.
2
2. Name the reusable cohort
Enter the purpose-oriented name and an optional description that explains its intended consumer.
3
3. Choose Folders or Assets
Use the source tabs and search to select exact folders, individual assets, or grouped output; review the selected-source summary.
4
4. Create and inspect
Choose Create Dataset, open the new dataset, and reconcile item count, data type, source provenance, and representative content.
5
5. Control later additions
Use the dataset’s Add files or Attach Data surface; every accepted membership change creates or advances history rather than rewriting an earlier version silently.
Decisions that affect production
Decision
Production guidance
Name
Use a durable purpose-oriented name; keep environment and date in version metadata where possible.
Owner
Assign a role accountable for membership and version changes.
Source scope
Keep enough provenance to explain every member later.
Groups
Include the grouped unit when project work requires shared context.
Continue the operating flow
Publish the first dataset version.
Attach the exact version to a pilot project.
Record future additions as a new version rather than silently changing history.
