Using Inherit Catalogue as a Parent User
If you are a Parent user, you can use the Inherit Catalogue functionality to sync catalogue items into another client automatically. This can help you manage multiple accounts while keeping catalogue data consistent without duplicating work.
Where to switch it on
This feature is only accessible when your Curve client belongs to a Parent account.
Go to Clients > edit the target client > open the Inherit Catalogue panel. From there, select the source client, assign an optional Catalogue Group if needed, and check the applicable item types.
How It Works
Once enabled, the Inherit Catalogue feature automatically pulls in relevant items from the original (source) client into the new (target) client. However, for the sync to trigger successfully, there's an important step to be aware of:
The sync only triggers when items in the original client are saved.
This means if the items have not been saved in the source client after the new client has been created, they won’t sync over to the new client - even if the Inherit Catalogue setting is enabled.
When an item syncs, the copy in the target client stays linked to the original item in the source client. Any later changes you save to the original are then applied to the linked copy as well. Because of this, all catalogue updates should be made in the source client. Changes made directly in the target client are not synced back to the source.
Forcing the Sync
To force the sync to run and copy catalogue items into your new client:
- Go to the relevant page in the original (source) client - e.g., the Works or Tracks/Releases page.
- Ensure no search filters are applied to your view.
- Click Export to download the full list of items.
- Without making any changes to the export file, go to the same page in the original client and import the file back in.
This re-import will bulk “re-save” all items, which triggers the Inherit Catalogue sync to copy them over into the new (target) client. Repeat these steps for each catalogue page you need to sync.
Multiple sources are allowed, and Cat Group must match the group name exactly.
Things To Be Aware Of
- Existing items aren’t linked automatically. If the same Composer, Publisher, or Work was created separately in both clients, the two entries aren’t connected.
- May create a duplicate if the target item has different identifiers. You can tidy these up with the Review and Merge Duplicate Publishers, Composers or Works tool. If it shares the same CAE (Publisher/Composer) or identifier (Work), the sync would simply fail.
- Deleting is not synced. Deleting an item in the source client doesn’t delete it in the target client. If you need to remove it from both, delete it in each client separately.
- Work Main Identifiers, ISWCs, and Tunecodes must be unique. If a Work in the target client already uses the same Main Identifier, the Work from the source client won’t sync.
- Edits made in the target to synced fields are overwritten by the next save in the source. Aliases and society IDs are merged, not replaced, so removing one in the source doesn't remove it in the target.
- Contracts and royalty data are not copied. Syncing a Work also creates its Tracks and chain Publishers/Composers in the target, even if those boxes aren't ticked.