Inventory
The inventory, its three kinds of asset, and when an asset is complete.
Inventory, in the sidebar under My work, holds everything your organization could sell. Each row is an asset. Any member of an organization with the vendor side can use it; an organization that only buys has no inventory.
Kinds of asset
| Kind | What it is |
|---|---|
| Codebase | A repository, with its history. |
| Raw data | Files: a ZIP archive, a folder or loose files. |
| Tasks | Tasks for training or evaluating models, one asset per task. |
The type bar above the table shows All types or one kind. Deprecated is for asset kinds that are retired; none is today.
Complete and incomplete
The platform decides an asset's stage from what it holds:
- Incomplete: a detail it owes is still missing. The row shows a warning sign that opens the asset's edit page at the first missing field.
- Complete: every detail is given and its data is linked. The row shows a check. Only a complete asset can go into a listing.
Raw data and a codebase whose details are all given but that has no data yet are not complete either: they are shown as incomplete until data is linked.
What each kind owes:
- Raw data and tasks: a title, a description and at least one domain.
- A codebase: the same, and thirteen figures about the repository: history start and end, lines of code, commits, pull requests, merged pull requests, contributors, source files, test files, primary languages, test coverage, whether CI runs on pull requests, and a confirmation that the code is private.
The asset page
Open a row to see its asset page. Owner tools at the top is for your organization: a checklist of what the asset still needs with an Add link for each, its status, its Revisions, the listings it is in, and the buttons Edit and Delete asset. List for sale makes a draft listing holding this asset and opens its editor, as Add listing does (see Create a listing); only a complete asset can be listed, and otherwise nothing is made. For a task imported from Ember Data, Quality signals show its graded runs and how many of its QA checks passed at the last refresh; Ember Data's environment build is not read. Below the line Under this line: what buyers see is what a buyer will be shown.
Edit opens the edit page. A banner says what is still missing, each missing field is marked Missing, and Save changes saves what you changed. Domains offers the same list as the marketplace's; Primary languages suggests a language by its name or a short name (py, golang); a language the list does not hold is added as you typed it, and one the asset already names is kept. Replace data uploads new data for the asset through the same upload tray as Add asset: one ZIP of the repository for a codebase, a ZIP or files for raw data. Once the upload is checked it becomes the asset's next revision. Notes you write there are seen only by your organization. A task's title is set when it is imported and cannot be changed.
Revisions
Each time data is linked to an asset, it gets a new numbered revision; the newest complete one is current, marked Current. A listing keeps the revision it was built with.
Filtering and sorting
The filter box above the table takes words and three kinds of term: status: (incomplete or complete), type: (codebase, raw_data or task) and domain:. Any other word matches an asset's title. Each column's menu sorts or hides it; the Columns button shows hidden ones again. Sorting, hidden columns and selected rows stay in your own browser and change nothing for anyone else.
Groups
Rows can be grouped. An asset that is in no named group is under Ungrouped, which cannot be renamed or deleted. New group, beside the filter box, makes a group: give it a name and tick the assets it holds (an asset is in one group at a time, so ticking one moves it). Each row's folder button moves the asset to another group or takes it out, back to Ungrouped; the pencil on a group's row renames it. Two groups cannot share a name. Deleting a group keeps its assets: they move to Ungrouped. A group that holds no asset is not shown in the table, but it is still offered by the rows' folder buttons.
Deleting an asset
Delete asset, on the asset page, takes the asset out of your inventory at once after you confirm. It is marked deleted and kept until a date the inventory shows, then removed for good with everything it stored, unless a listing still holds it or a buyer's purchase names it. An asset in a listing cannot be deleted: take it out of the listing first. A task cannot be deleted.
Limits
An organization holds a limited number of assets; a deleted asset counts until it is removed for good. See Fees and limits.