Create version
Overview
Saves what a dataset holds right now as a numbered version, for example Cats@v2. The saved version doesn’t change afterwards, while the dataset itself stays editable: imports, labeling, and other nodes keep adding to it under its own name.
Nodes wired to this node’s output read the saved version, so a training run downstream sees the same data every time. Saving is cheap: it records references to the assets, not copies of their files.
How it works
FAQ
Why does the node fail with "is an older version"?
The input names a saved version such as Cats@v1 rather than the dataset. Saving an older version would bring its contents back over the dataset, so the node refuses. Pick the dataset itself in the input. To bring an older version back on purpose, use Restore version.
What do other nodes read after I save a version?
A node wired to the output of this node reads the saved version and always gets the same contents. A node wired to the output of any other node, or set to the dataset rather than one of its versions in its picker, reads the dataset as it is when that node runs, including changes made after the version was saved.
Does the version store image and video files?
No. It stores references to the existing assets, so the version stays complete only while those assets exist in OvalBee.
Is the description required?
No, it’s optional.
Inputs
Dataset to save a version of. Its assets and annotations are recorded as they are at the moment the node runs. Key: DATASET.
Note shown next to this version, to help you recognise it later. Key: DESCRIPTION.
Outputs
The saved version. Nodes that read it always get these exact contents, even after the dataset changes. Key: DATASET.
Number of the saved version, as shown on the dataset page. Key: VERSION.
JSON config
Machine-readable node interface for automation and advanced usage.