Copy
Overview
Copies images and videos, together with their annotations, from one dataset to another. Assets already in the destination dataset are skipped.
Copied assets stay in the source dataset. Use Move instead if you want to remove them from the source.
Use it when a flow needs to reuse the same assets in another dataset.
After a successful run, the node shows a badge with the number of assets added in that run.
How it works
FAQ
What does Copy ignore?
Copy handles images and videos only. It ignores other asset types, and the badge does not count annotations.
What happens when data already exists in the destination?
The node skips both the data and its annotations. It does not add missing annotations to an existing destination membership.
Copy writes into the destination as it is and never creates a new dataset version, so a rerun adds only the assets that aren’t there yet.
Why does the badge show +0 assets?
Why does the badge show +0 assets?
The source has no images or videos, or all supported data is already in the destination. Check both datasets. If the destination already has everything, no action is needed.
Inputs
Source dataset the assets are copied from. Its own contents stay untouched. Key: SRC_DATASET.
Destination dataset where assets are added, along with their annotations. Existing assets are left alone, so a second run adds nothing. Key: DST_DATASET.
Outputs
ID of the destination OvalBee dataset. Key: DST_DATASET.
Short badge with the number of images and videos newly added to the destination in the latest run. Shown on the node as a badge. Key: LAST_COPIED_ASSETS_COUNT.
JSON config
Machine-readable node interface for automation and advanced usage.