RIN implementation guidance and best practice

Below please find guidance and best practice articles for RIN by using the search function or by browsing the articles by category.

General guidance for RIN

Page:

Acknowledgements and non-repudiation
Page:

Allowed-value sets and UserDefinedValues
Page:

Artist name changes over time
Page:

Artist roles and DisplayCredits
Page:

Avoiding the use of proprietary Identifiers
Page:

Band members
Page:

Bar codes of various lengths
Page:

Canonical spellings for names
Page:

Classical Music – Genre vs Structure
Page:

Comments
Page:

Common language and script code combinations
Page:

Communicating classical releases and resources
Page:

Communicating old currencies
Page:

Communicating remixes and remixers
Page:

Communication of identifiers in DDEX messages
Page:

Communication of percentages
Page:

Contents of a RIN message
Page:

Creation dates
Page:

Date/time tags and Time Zone Designators
Page:

Dealing with uncommon use cases
Page:

Direction of writing
Page:

Do DPIDs have hyphens?
Page:

Do not use CDATA to concatenate data
Page:

Exclusive vs inclusive deals
Page:

Field length and precision
Page:

GDPR and UGC
Page:

Genres
Page:

Handling 'odd' characters
Page:

How many DPIDs Do I need?
Page:

Identifiers for resources and releases and parties
Page:

Identifying sound recordings and videos containing the same audio
Page:

Importing RIN files into RIN files (RIN 1.0 only)
Page:

Instrumental music in ERN-3
Page:

Invalid Messages
Page:

Java library's date bug for 2020
Page:

Keywords
Page:

Lengths of artist names
Page:

Limitations of proprietary identifiers
Page:

Locations of XSDs
Page:

Malformed identifiers
Page:

Metadata in different languages
Page:

Multiple proprietary identification systems
Page:

Namespace and file locations for the XSD for allowed value sets
Page:

One artist with two roles
Page:

Opus and composer catalogue numbers
Page:

Order of XML attributes
Page:

Origin and trustworthiness of MEAD and PIE information
Page:

Parental advice labels
Page:

PLine and CLine
Page:

Preambles for XML-based DDEX messages
Page:

Precision of numeric values in MWN
Page:

Priorities for metadata items
Page:

Proprietary identifiers
Page:

Public domain works
Page:

Referencing composites using ID and IDREF
Page:

Resource types
Page:

Rights controller information in ERNs to Music Licensing Companies
Page:

Role code synonyms and credits
Page:

Semantics of repeating XML tags
Page:

Special characters
Page:

Special XML characters (and how to avoid &amp;)
Page:

Specialising DDEX-Defined Values
Page:

Splitting names and the importance of the KeyName
Page:

Subtitles in multiple languages
Page:

Territorial variations in release descriptions
Page:

Territory codes using ISO 3166-1 or ISO 3166-3 or TIS
Page:

Time stamp for data accuracy
Page:

Translating and Transliterating Names
Page:

Translating and transliterating titles
Page:

Use of ISRCs as the primary database key
Page:

User-defined values
Page:

Version compatibility
Page:

Versioning Allowed Value Sets
Page:

What can I do if I have data requirements not addressed by DDEX
Page:

Who owns which rights?
Page:

Worldwide
Page:

Writer roles

Guidance on Releases, Resources and Works

Page:

Classical Music – Genre vs Structure
Page:

Communicating classical releases and resources
Page:

Contents of a RIN message
Page:

Creation dates
Page:

Genres
Page:

Identifiers for resources and releases and parties
Page:

Instrumental music in ERN-3
Page:

Keywords
Page:

Metadata in different languages
Page:

Opus and composer catalogue numbers
Page:

Parental advice labels
Page:

PLine and CLine
Page:

Public domain works
Page:

Resource types
Page:

Subtitles in multiple languages
Page:

Territorial variations in release descriptions
Page:

Translating and transliterating titles
Page:

Use of ISRCs as the primary database key
Page:

Who owns which rights?

Guidance on Parties

Filter by label

There are no items with the selected labels at this time.

Guidance on Identifiers and Allowed Value Sets

Page:

Allowed-value sets and UserDefinedValues
Page:

Avoiding the use of proprietary Identifiers
Page:

Bar codes of various lengths
Page:

Can a release be identified by an ISRC?
Page:

Communication of identifiers in DDEX messages
Page:

Do DPIDs have hyphens?
Page:

Excluded Territories and Worldwide
Page:

How many DPIDs Do I need?
Page:

Identifiers for resources and releases and parties
Page:

Identifying chapters
Page:

Identifying sound recordings and videos containing the same audio
Page:

Limitations of proprietary identifiers
Page:

Malformed identifiers
Page:

Multiple CommercialModelTypes or UseTypes in one deal
Page:

Multiple proprietary identification systems
Page:

Opus and composer catalogue numbers
Page:

Proprietary identifiers
Page:

Referencing composites using ID and IDREF
Page:

Specialising DDEX-Defined Values
Page:

Territory codes using ISO 3166-1 or ISO 3166-3 or TIS
Page:

Use of ISRCs as the primary database key
Page:

User-defined values
Page:

Worldwide

Guidance on Dates and Time

Page:

Creation dates
Page:

Date/time tags and Time Zone Designators
Page:

Exclusive vs inclusive deals
Page:

Java library's date bug for 2020
Page:

Time stamp for data accuracy

Guidance on Choreography issues

Page:

Acknowledgements and non-repudiation

Guidance on XML issues

Page:

Comments
Page:

Direction of writing
Page:

Do not use CDATA to concatenate data
Page:

Handling 'odd' characters
Page:

Importing RIN files into RIN files (RIN 1.0 only)
Page:

Invalid Messages
Page:

Java library's date bug for 2020
Page:

Locations of XSDs
Page:

Namespace and file locations for the XSD for allowed value sets
Page:

Order of XML attributes
Page:

Preambles for XML-based DDEX messages
Page:

Referencing composites using ID and IDREF
Page:

Semantics of repeating XML tags
Page:

Special XML characters (and how to avoid &amp;)
Page:

Specialising DDEX-Defined Values
Page:

User-defined values

All RIN-related guidance

Page:

Acknowledgements and non-repudiation
Page:

Allowed-value sets and UserDefinedValues
Page:

Artist name changes over time
Page:

Artist roles and DisplayCredits
Page:

Avoiding the use of proprietary Identifiers
Page:

Band members
Page:

Canonical spellings for names
Page:

Classical Music – Genre vs Structure
Page:

Comments
Page:

Communicating classical releases and resources
Page:

Communicating remixes and remixers
Page:

Communication of identifiers in DDEX messages
Page:

Contents of a RIN message
Page:

Creation dates
Page:

Date/time tags and Time Zone Designators
Page:

Direction of writing
Page:

Do DPIDs have hyphens?
Page:

Do not use CDATA to concatenate data
Page:

Exclusive vs inclusive deals
Page:

Field length and precision
Page:

Genres
Page:

Handling 'odd' characters
Page:

How many DPIDs Do I need?
Page:

Identifiers for resources and releases and parties
Page:

Importing RIN files into RIN files (RIN 1.0 only)
Page:

Instrumental music in ERN-3
Page:

Invalid Messages
Page:

Java library's date bug for 2020
Page:

Keywords
Page:

Limitations of proprietary identifiers
Page:

Locations of XSDs
Page:

Malformed identifiers
Page:

Metadata in different languages
Page:

Multiple proprietary identification systems
Page:

Namespace and file locations for the XSD for allowed value sets
Page:

One artist with two roles
Page:

Opus and composer catalogue numbers
Page:

Order of XML attributes
Page:

Parental advice labels
Page:

PLine and CLine
Page:

Preambles for XML-based DDEX messages
Page:

Priorities for metadata items
Page:

Proprietary identifiers
Page:

Public domain works
Page:

Referencing composites using ID and IDREF
Page:

Resource types
Page:

Rights controller information in ERNs to Music Licensing Companies
Page:

Role code synonyms and credits
Page:

Semantics of repeating XML tags
Page:

Special characters
Page:

Special XML characters (and how to avoid &amp;)
Page:

Specialising DDEX-Defined Values
Page:

Splitting names and the importance of the KeyName
Page:

Subtitles in multiple languages
Page:

Territorial variations in release descriptions
Page:

Territory codes using ISO 3166-1 or ISO 3166-3 or TIS
Page:

Time stamp for data accuracy
Page:

Translating and Transliterating Names
Page:

Translating and transliterating titles
Page:

Use of ISRCs as the primary database key
Page:

User-defined values
Page:

Version compatibility
Page:

Who owns which rights?
Page:

Worldwide
Page:

Writer roles

Search