01
ValueOne source of truth
Keep content, versions, and delivery files aligned in one place.
Catalog
Catalog asset management
Bring scattered music assets, metadata, and delivery materials into one governed catalog.
Product language preview
Release statusLive on 12 DSPs
Data completenessMissing ISRC × 2
Upload draftDraft autosaved 5s ago
Delivery protocolDDEX ERN 4.3.2 ready
Business value
Standardize assets before the rest of the pipeline
02
ValueLess duplicated effort
Reduce repeated naming, archiving, and search work across teams.
03
ValueFoundation for downstream work
Carry a reusable asset standard into later processes.
Core capabilities
A capability set built around catalog, version, and delivery controls
Capability · 01
Catalog structure
Arrange assets by business rules so they stay easy to find and reuse.
Capability · 02
Metadata consistency
Tie key fields to the same governance path as delivery requirements.
Capability · 03
Delivery readiness
Validate the minimum asset state before the next workflow starts.
Workflow
A four-step loop from intake to release prep
01Step
Ingest assets
Import content, metadata, and supporting delivery files.
02Step
Organize catalog
Group assets by project, version, or partner relationship.
03Step
Validate rules
Check that fields, files, and access are ready for downstream use.
04Step
Move to distribution
Hand off prepared assets into the distribution lane.
Asset backbone
What SEUNOR brings into a governable asset layer
Catalog is more than file storage. It pulls every object the music business keeps referencing into one layer that can be governed, searched, and reused.
01
Album and track metadata
Keep the identity, version, artists, and language of each work consistent in one place so they stop drifting between teams.
- Release type and version are registered for albums, singles, and EPs alike
- Multiple artists, multilingual aliases, and explicit-content marks are captured once
- Label, original release date, and copyright year stay bound to the work
02
Audio, cover, and lyrics assets
Every delivery file is registered by purpose and version, so missing materials never surface only at delivery time.
- Master audio, preview, and waveform data are ingested together, never re-uploaded
- Cover art is served at thumb, display, and original tiers to keep bandwidth in check
- Plain and time-aligned lyrics are maintained side by side without format drift
03
Rights and contracts
Publishing rights, recording rights, and contract files belong to the work itself, not to a local folder on someone's laptop.
- Publishing and recording rights are tracked separately with their own holders and shares
- C-Line and P-Line are bound to the work and reused automatically downstream
- Contracts are archived against tracks or albums so rights changes leave a paper trail
04
Artists, labels, and external links
Artists are real entities that can be identified, searched, and connected to outside platforms, not just a line of text.
- Artist legal name, multilingual aliases, and sort name are maintained once
- Industry identifiers such as ISNI and IPI are attached to the artist entity
- Streaming-platform artist pages are reviewed and stored for delivery-time reuse
Who uses Catalog
Different teams, the same underlying answer
SEUNOR Catalog is not designed for digital-only operators. The asset layer applies regardless of how your business is organized.
01
Record labels
Artists, albums, and label data live across several systems, and every release demands a fresh rights and contract review.
Bring works, artists, labels, and contracts into one asset layer so no one asks who owns a recording right at release time again.
02
Independent labels
No dedicated data team, yet every release must stay consistent across multiple channels.
Replace manual checklists with admission rules in Catalog so every delivery file is structurally validated as soon as it is saved.
03
Rights agencies
Representing a long tail of third-party works, with publishing, recording, contract, and royalty boundaries to maintain for each one.
Keep rights data attached to the work itself. Rights changes and contract updates leave a fully auditable trail.
Identifiers and allocation
How SEUNOR governs the identifiers global distribution depends on
UPC, ISRC, ISNI, IPI, GRid, and DPID decide whether a work can be correctly recognized across the global supply chain. SEUNOR turns these into pooled, allocated, and traceable assets rather than something teams type in by hand.
01Identifier | 02Scope | 03How SEUNOR handles it |
|---|---|---|
| UPC | Album-level product code | Managed as a prefix pool and allocated automatically at release, removing manual numbering conflicts |
| ISRC | Track-level recording identifier | Pool + per-year sequence, with sequences carrying over cleanly across years |
| ISNI | Creator identity | Bound to the artist entity and captured alongside artist maintenance |
| IPI | Composition rights party | Bound to the artist entity for CMO reconciliation and identification |
| GRid | Release batch identifier | Generated as the release lane progresses and attached automatically at delivery |
| DPID | DDEX party identifier | Maintained in tenant configuration and injected into DDEX messages automatically |
UPC
- Scope
- Album-level product code
- How SEUNOR handles it
- Managed as a prefix pool and allocated automatically at release, removing manual numbering conflicts
ISRC
- Scope
- Track-level recording identifier
- How SEUNOR handles it
- Pool + per-year sequence, with sequences carrying over cleanly across years
ISNI
- Scope
- Creator identity
- How SEUNOR handles it
- Bound to the artist entity and captured alongside artist maintenance
IPI
- Scope
- Composition rights party
- How SEUNOR handles it
- Bound to the artist entity for CMO reconciliation and identification
GRid
- Scope
- Release batch identifier
- How SEUNOR handles it
- Generated as the release lane progresses and attached automatically at delivery
DPID
- Scope
- DDEX party identifier
- How SEUNOR handles it
- Maintained in tenant configuration and injected into DDEX messages automatically
Catalog governance
Surface last-mile risk before the release lane begins
Catalog is not just storage. It applies a set of governance moves so problems show up before the DDEX message is generated, not after.
4Gates · Pre-release
Gate · 01
Rights consistency checks
C-Line, P-Line, publishing rights, and recording rights are validated on save, so missing fields are caught at the asset layer rather than during DDEX assembly.
Gate · 02
AI involvement disclosure
Track-level AI involvement statements live with the work, ready to be carried into delivery to meet the increasing disclosure expectations of the industry.
Gate · 03
Traceable change history
Metadata, artist, rights, and platform changes leave a timestamped trail for review, reconciliation, and cross-team retrospectives.
Gate · 04
Delete and takedown boundaries
Deletes require double confirmation. For works already in distribution, catalog-side delete and channel-side takedown are treated as distinct actions so live releases stay safe.
Formats and delivery readiness
Assets reach a deliverable state before distribution ever begins
The handoff between Catalog and distribution is not the DDEX file. It is the moment the asset itself is declared deliverable.
01Stage
Audio and integrity checks
Audio, cover, and lyrics files are checksummed with SHA-256 on ingest. Distribution requests the right tier on demand, preserving integrity without wasting bandwidth.
02Stage
Lyrics and time-aligned lyrics
Plain lyrics, LRC, and TTML word-level lyrics are supported together at both album and track scope so lyric work is never duplicated.
03Stage
DDEX ERN coverage
DDEX ERN 4.3.2, 4.1, and 3.8.2 are all built in. Each channel can receive the version it requires without an extra translation step.
Before vs after
From scattered files to a single asset layer
The same people, the same catalog, just a different way of working.
Before standardization
- Metadata lives in spreadsheets and local folders
- Rights data is confirmed verbally and by email
- Identifiers are numbered manually, year-over-year conflicts appear
- Pre-release prep is repeatedly the bottleneck
With Catalog in place
- Metadata lives in one shared asset layer that every team reads from
- Publishing and recording rights are maintained on the work and stay auditable
- UPC and ISRC are allocated from pools, with sequences continuing cleanly across years
- Pre-release prep becomes a confirmation step, not a cleanup project
FAQ
The questions teams ask most often before adopting Catalog
These answers cover the highest-frequency topics. Detailed limits live in the product documentation and contracts.
No. SEUNOR supports DDEX ERN 4.3.2, 4.1, and 3.8.2 simultaneously. Existing metadata can be ingested first, with missing fields filled in against the asset-layer rules; teams do not have to finish everything before starting to use the platform.
Get started
Keep assets in a governable state
SEUNOR uses Catalog to consolidate the front-loaded organization work.