Move
Overview
Moves images and videos, together with their annotations, from one dataset into another. Assets the destination dataset already holds are skipped.
Moved assets are removed from the source dataset. Use Copy instead if you want to keep assets in the source dataset.
Use it when you want to move data from a temporary or review dataset.
How it works
FAQ
What happens to assets already in the destination?
They are skipped. The node does not add them again, and it leaves them in the source dataset. Only assets missing from the destination are moved out of the source.
Does the node move annotations and videos too?
Yes. Images and videos are both moved, and each asset’s linked annotations are attached to the destination and detached from the source.
Why did the badge show +0 assets?
Why did the badge show +0 assets?
The source dataset is empty, or every asset is already in the destination. Nothing is moved in that run.
Can I get the moved assets back into the source?
Not from a version. Move changes both datasets in place and doesn’t create a new dataset version of either. The assets themselves aren’t deleted, so a Copy or Move in the other direction puts them back.
Inputs
Source dataset the assets are taken from. They no longer belong to it afterwards. Key: SRC_DATASET.
Destination dataset where the assets end up, along with their annotations. Assets it already holds are left alone and stay in the source dataset too. Key: DST_DATASET.
Outputs
ID of the destination OvalBee dataset. Key: DST_DATASET.
Short badge with the number of assets moved in the latest run. Shown on the node as a badge. Key: LAST_MOVED_ASSETS_COUNT.
JSON config
Machine-readable node interface for automation and advanced usage.