Catalog and artist management
Manage the releases, tracks, artists, and labels in your SpaceMedia organization, and plan a catalog migration safely.
Your catalog is four connected record types. Changing one affects the others, which is why bulk edits deserve care.
| Record | Holds | Detail |
|---|---|---|
| Releases | Singles, EPs, albums and their state | Release library |
| Tracks | Recordings, audio, and per-track metadata | Track library |
| Artists | Store-facing identities releases attach to | Artists and labels |
| Labels | Label records releases are issued under | Artists and labels |
Artist records are the sensitive ones
An artist record determines which store artist page a release lands on. Merging, renaming, or remapping one affects every release attached to it, including releases already delivered.
Treat artist edits as catalog-wide changes rather than record edits. See Artist profiles for the store-side consequences your customers experience.
Migrating a catalog
Moving an existing catalog in is a project, not an import:
- Start with a representative sample, not the full catalog. Include an album, a single, a compilation, and anything with unusual credits.
- Verify artist mapping on the sample before scaling. A mapping error repeated across a thousand releases is a thousand corrections.
- Confirm identifiers. Existing ISRCs and UPCs must carry over so history and reporting stay attached.
- Check what delivery a migrated release actually needs. Not everything should be redelivered.
- Plan rollback before you start.
Bulk and API workflows need separate planning and validation. Contracts and endpoints are at docs.spacemedia.uk.
Permissions
Catalog areas are gated individually: view releases, view tracks, view artists. Grant what each role needs and no more. See Members and roles.