diff --git a/.DS_Store b/.DS_Store new file mode 100644 index 0000000..946579b Binary files /dev/null and b/.DS_Store differ diff --git a/README.rst b/README.rst index aec1879..ca7b173 100644 --- a/README.rst +++ b/README.rst @@ -1,7 +1,7 @@ CWR Data Model API ================== -This projects offers a domain model for the CISAC CWR standard v2.1 to be +This projects offers a domain model for the CISAC CWR standard v2.2 to be used on Python applications, along a series of parsing which allow transformations between the model and various data structures. @@ -13,6 +13,9 @@ works data. While the CWR standard has been created by `CISAC`_ this library has been developed by `WESO`_ independently, with help from `BMAT`_. +This is a fork of the `official CWR-DataApi repository`_ by WESO, updated to +support CWR standard v2.2 by `max1millions`_. + .. image:: https://badge.fury.io/py/cwr-api.svg :target: https://pypi.python.org/pypi/cwr-api :alt: CWR-API Pypi package page @@ -51,9 +54,10 @@ Prerequisites The project has been tested in the following versions of the interpreter: -- Python 3.4 -- Python 3.5 -- Python 3.6 +- Python 3.9 +- Python 3.10 +- Python 3.11 +- Python 3.12 All other dependencies are indicated on the requirements.txt file. The included makefile can install them with the command: @@ -146,9 +150,11 @@ The project has been released under the `MIT License`_. .. _BMAT: http://www.bmat.com/ .. _WESO: http://www.weso.es/ .. _project issues page: https://github.com/weso/CWR-DataApi/issues -.. _Pyparsing: https://pyparsing.wikispaces.com/ +.. _Pyparsing: https://pyparsing-docs.readthedocs.io/ .. _Pypi package: https://pypi.python.org/pypi/CWR-API .. _Sphinx: http://sphinx-doc.org/ .. _latest docs: http://cwr-dataapi.readthedocs.org .. _GitHub project page: https://github.com/weso/CWR-DataApi +.. _official CWR-DataApi repository: https://github.com/weso/CWR-DataApi +.. _max1millions: https://github.com/max1millions .. _MIT License: http://www.opensource.org/licenses/mit-license.php diff --git a/config_cwr/accessor.py b/config_cwr/accessor.py index 3f1dcea..5693f45 100644 --- a/config_cwr/accessor.py +++ b/config_cwr/accessor.py @@ -43,7 +43,7 @@ def read_yaml_file(self, file_name): """ with open(os.path.join(self.__path(), os.path.basename(file_name)), 'rt') as yamlfile: - return yaml.load(yamlfile) + return yaml.load(yamlfile, Loader=yaml.FullLoader) def read_config_file(self, file_name): """ diff --git a/config_cwr/default_values.yml b/config_cwr/default_values.yml index 48e4368..3270061 100644 --- a/config_cwr/default_values.yml +++ b/config_cwr/default_values.yml @@ -1 +1 @@ -default_version: 2.1 \ No newline at end of file +default_version: 2.2 \ No newline at end of file diff --git a/config_cwr/field_config_common.yml b/config_cwr/field_config_common.yml index 811c121..90f784c 100644 --- a/config_cwr/field_config_common.yml +++ b/config_cwr/field_config_common.yml @@ -137,7 +137,7 @@ date_publication_printed_edition: duration: type: time - size: 8 + size: 6 name: Duration ean13: @@ -153,6 +153,12 @@ edi_standard: values: - '01.10' +hdr_version_type: + type: alphanum + size: 3 + name: Header Version Type + results_name: version_type + entire_work_title: type: alphanum size: 60 @@ -599,7 +605,7 @@ submitter_work_n: name: Submitter Work Number tax_id: - type: numeric + type: alphanum size: 9 name: Tax ID Number @@ -765,4 +771,34 @@ writer_unknown: year_production: type: numeric size: 4 - name: Year of Production \ No newline at end of file + name: Year of Production + +recording_title: + type: alphanum_ext + size: 60 + name: Recording Title + +version_title: + type: alphanum_ext + size: 60 + name: Version Title + +display_artist: + type: alphanum_ext + size: 60 + name: Display Artist + +record_label: + type: alphanum + size: 60 + name: Record Label + +isrc_validity: + type: alphanum + size: 20 + name: ISRC Validity + +submitter_recording_identifier: + type: alphanum_end + size: 14 + name: Submitter Recording Identifier \ No newline at end of file diff --git a/config_cwr/record_config_common.cml b/config_cwr/record_config_common.cml index 7ea5de4..a5d0aa4 100644 --- a/config_cwr/record_config_common.cml +++ b/config_cwr/record_config_common.cml @@ -340,7 +340,7 @@ transaction_record: transaction_record: id: publisher_territory - head: SPT + head: SPT,OPT rules: [ field: ip_n @@ -396,6 +396,14 @@ transaction_record: optional [ field: media_type ] + optional [ + field: recording_title + field: version_title + field: display_artist + field: record_label + field: isrc_validity + field: submitter_recording_identifier + ] ] transaction_record: @@ -422,6 +430,7 @@ record: optional [ field: character_set + field: hdr_version_type ] ] @@ -573,6 +582,7 @@ transaction_record: field: submitter_agreement_n field: society_assigned_agreement_n field: writer_ip_n + field: publisher_sequence_n ] transaction_record: diff --git a/cwr/.DS_Store b/cwr/.DS_Store new file mode 100644 index 0000000..2a24786 Binary files /dev/null and b/cwr/.DS_Store differ diff --git a/cwr/grammar/factory/config.py b/cwr/grammar/factory/config.py index dfe87dd..083a00a 100644 --- a/cwr/grammar/factory/config.py +++ b/cwr/grammar/factory/config.py @@ -15,7 +15,7 @@ pp.Word(pp.nums).setResultsName('count') rule_at_least.setParseAction(lambda v: int(v[0])) -_rule_config_string = pp.Regex('[^()\[\]\\n,:]*') +_rule_config_string = pp.Regex(r'[^()\[\]\n,:]*') _rule_config_string.setParseAction(lambda v: v[0].strip()) _rule_identifier = _rule_config_string + pp.Literal(':').suppress() diff --git a/cwr/grammar/field/basic.py b/cwr/grammar/field/basic.py index baf7878..65bb39c 100644 --- a/cwr/grammar/field/basic.py +++ b/cwr/grammar/field/basic.py @@ -3,7 +3,6 @@ import datetime import pyparsing as pp -from pyparsing import ParseResults """ CWR fields grammar. diff --git a/cwr/group.py b/cwr/group.py index 8a1b275..26f2b06 100644 --- a/cwr/group.py +++ b/cwr/group.py @@ -44,7 +44,7 @@ def __init__(self, record_type='', group_id=0, transaction_type='', - version_number='02.10', + version_number='02.20', batch_request_id=0 ): super(GroupHeader, self).__init__( diff --git a/cwr/interested_party.py b/cwr/interested_party.py index cc95280..86b5135 100644 --- a/cwr/interested_party.py +++ b/cwr/interested_party.py @@ -115,7 +115,7 @@ def __init__(self, record_type='', transaction_sequence_n=0, record_sequence_n=0, - first_recording_refusal='U', + first_recording_refusal='N', usa_license='', pr_society=None, pr_ownership_share=0, @@ -292,7 +292,7 @@ def usa_license(self, value): class IPTerritoryOfControlRecord(TransactionRecord): """ - Represents a CWR Publisher or Writer Territory of Control (SPT/SWT). + Represents a CWR Publisher or Writer Territory of Control (SPT/OPT/SWT). This indicates if a Publisher or Writer has control or not over a Territory, and the shares it has on it. @@ -551,7 +551,7 @@ def __init__(self, sr_society=None, sr_ownership_share=0, special_agreements=None, - first_recording_refusal='U', + first_recording_refusal='N', usa_license='' ): """ @@ -995,7 +995,8 @@ def __init__(self, publisher_name='', writer_ip_n='', submitter_agreement_n=None, - society_assigned_agreement_n=None + society_assigned_agreement_n=None, + publisher_sequence_n=0 ): super(PublisherForWriterRecord, self).__init__( record_type, @@ -1011,6 +1012,9 @@ def __init__(self, self._submitter_agreement_n = submitter_agreement_n self._society_assigned_agreement_n = society_assigned_agreement_n + # Publisher chain link + self._publisher_sequence_n = publisher_sequence_n + @property def publisher_ip_n(self): """ @@ -1082,6 +1086,21 @@ def publisher_name(self): def publisher_name(self, value): self._publisher_name = value + @property + def publisher_sequence_n(self): + """ + Publisher Sequence # field. Numeric. + + Must match the Publisher Sequence # of the relating SPU/OPU record. + + :return: the publisher sequence number in the chain + """ + return self._publisher_sequence_n + + @publisher_sequence_n.setter + def publisher_sequence_n(self, value): + self._publisher_sequence_n = value + class WriterRecord(InterestedPartyRecord): """ @@ -1100,9 +1119,9 @@ def __init__(self, writer=None, writer_designation=None, work_for_hire=False, - writer_unknown='F', - reversionary='U', - first_recording_refusal='U', + writer_unknown='', + reversionary='', + first_recording_refusal='N', usa_license='', pr_society=None, pr_ownership_share=0, diff --git a/cwr/parser/decoder/dictionary.py b/cwr/parser/decoder/dictionary.py index 43918d0..4007003 100644 --- a/cwr/parser/decoder/dictionary.py +++ b/cwr/parser/decoder/dictionary.py @@ -587,6 +587,8 @@ def decode(self, data): edi_standard=data['edi_standard']) if 'character_set' in data: header.character_set = data['character_set'] + if 'version_type' in data: + header.version_type = data['version_type'] return header diff --git a/cwr/parser/encoder/dictionary.py b/cwr/parser/encoder/dictionary.py index f90da17..d568ebf 100644 --- a/cwr/parser/encoder/dictionary.py +++ b/cwr/parser/encoder/dictionary.py @@ -627,6 +627,7 @@ def encode(self, record): record.society_assigned_agreement_n encoded['submitter_agreement_n'] = record.submitter_agreement_n encoded['writer_ip_n'] = record.writer_ip_n + encoded['publisher_sequence_n'] = record.publisher_sequence_n return encoded @@ -924,6 +925,12 @@ def encode(self, record): encoded['media_type'] = record.media_type encoded['recording_format'] = record.recording_format encoded['recording_technique'] = record.recording_technique + encoded['recording_title'] = getattr(record, 'recording_title', '') + encoded['version_title'] = getattr(record, 'version_title', '') + encoded['display_artist'] = getattr(record, 'display_artist', '') + encoded['record_label'] = getattr(record, 'record_label', '') + encoded['isrc_validity'] = getattr(record, 'isrc_validity', '') + encoded['submitter_recording_identifier'] = getattr(record, 'submitter_recording_identifier', '') return encoded @@ -1097,6 +1104,7 @@ def encode(self, record): encoded['transmission_date'] = record.transmission_date encoded['edi_standard'] = record.edi_standard encoded['character_set'] = record.character_set + encoded['version_type'] = record.version_type return encoded diff --git a/cwr/parser/encoder/standart/field.py b/cwr/parser/encoder/standart/field.py index 211881e..6e99ba3 100644 --- a/cwr/parser/encoder/standart/field.py +++ b/cwr/parser/encoder/standart/field.py @@ -79,7 +79,7 @@ def format(self, value): if value is None: return self._blank() tpl = "{!s:<%d}" % self._rule['size'] - return tpl.format(str(value)) + return tpl.format(str(value))[:self._rule['size']] class NumericCwrFieldEncoder(CwrFieldEncoder): @@ -90,7 +90,7 @@ def format(self, value): if value is None or value == '': value = 0 tpl = "{:0>%d}" % self._rule['size'] - return tpl.format(str(value)) + return tpl.format(str(value))[:self._rule['size']] class NumericEmptyCwrFieldEncoder(CwrFieldEncoder): @@ -102,7 +102,7 @@ def format(self, value): return self._blank() else: tpl = "{:0>%d}" % self._rule['size'] - return tpl.format(str(value)) + return tpl.format(str(value))[:self._rule['size']] class BooleanCwrFieldEncoder(DefaultCwrFieldEncoder): @@ -170,9 +170,13 @@ def set_values(self, values): class LookupNumericCwrFieldEncoder(NumericEmptyCwrFieldEncoder, LookupCwrFieldEncoder): """ - Lookup_int type encoder. Mu + Lookup_int type encoder for numeric table codes (e.g. society codes). + Treats 0 as blank since code 0 is not a valid lookup value. """ - pass + def format(self, value): + if value == 0: + return self._blank() + return super(LookupNumericCwrFieldEncoder, self).format(value) class BlankCwrFieldEncoder(DefaultCwrFieldEncoder): """ diff --git a/cwr/parser/encoder/standart/record.py b/cwr/parser/encoder/standart/record.py index 189e2a0..619504f 100644 --- a/cwr/parser/encoder/standart/record.py +++ b/cwr/parser/encoder/standart/record.py @@ -192,6 +192,13 @@ def _process_record(rules): processed[rule_id].append(rule) else: processed[rule_id] = [rule] + # Add aliases for equivalent territory-of-control record types: + # - Treat OWT as SWT for field templates + # - Treat OPT as SPT for field templates + if 'SWT' in processed and 'OWT' not in processed: + processed['OWT'] = processed['SWT'] + if 'SPT' in processed and 'OPT' not in processed: + processed['OPT'] = processed['SPT'] return processed def get_format_encoders(self, record_id): @@ -201,7 +208,7 @@ def get_format_encoders(self, record_id): def get_encoder(self, entity): if entity.record_type not in self._record_configs: - raise NameError('The record type %s not found in config %s' % entity.record_type) + raise NameError('The record type %s not found in config %s' % (entity.record_type, list(self._record_configs.keys()))) record_configs = self._record_configs[entity.record_type] if isinstance(entity, TransactionRecord): return TransactionCwrRecordEncoder(record_configs, self._field_configs) diff --git a/cwr/transmission.py b/cwr/transmission.py index c2484ef..7d70216 100644 --- a/cwr/transmission.py +++ b/cwr/transmission.py @@ -34,7 +34,8 @@ def __init__(self, creation_date_time=None, transmission_date=None, edi_standard='01.10', - character_set='' + character_set='', + version_type='' ): """ Constructs a TransmissionHeader. @@ -47,6 +48,7 @@ def __init__(self, :param record_type: the CWR record type :param edi_standard: EDI standard version (01.10 by default) :param character_set: file encoding set (ASCII by default) + :param version_type: version type (2.2 by default) """ super(TransmissionHeader, self).__init__(record_type) @@ -62,7 +64,8 @@ def __init__(self, # Other info self._edi_standard = edi_standard self._character_set = character_set - + self._version_type = version_type + def __str__(self): return '%s (%s, %s) on %s' % ( self._sender_name, self._sender_id, self._sender_type, @@ -70,11 +73,12 @@ def __str__(self): def __repr__(self): return '(sender_id=%r, sender_name=%r, sender_type=%r, ' \ - 'creation_date=%r, transmission_date=%r)' % ( + 'creation_date=%r, transmission_date=%r, version_type=%r)' % ( 'TransmissionHeader', self._sender_id, self._sender_name, self._sender_type, self._creation_date_time, - self._transmission_date) + self._transmission_date, + self._version_type) @property def character_set(self): @@ -96,6 +100,21 @@ def character_set(self): def character_set(self, value): self._character_set = value + @property + def version_type(self): + """ + Version Type field. Alphanumeric. + + Indicates the CWR version used (e.g., '2.2'). + + :return: the version type string + """ + return self._version_type + + @version_type.setter + def version_type(self, value): + self._version_type = value + @property def creation_date_time(self): """ diff --git a/cwr/work.py b/cwr/work.py index e9b89ea..1703fb1 100644 --- a/cwr/work.py +++ b/cwr/work.py @@ -1322,7 +1322,13 @@ def __init__(self, isrc=None, recording_format=None, recording_technique=None, - media_type=None): + media_type=None, + recording_title='', + version_title='', + display_artist='', + record_label='', + isrc_validity='', + submitter_recording_identifier=''): super(RecordingDetailRecord, self).__init__( record_type, transaction_sequence_n, @@ -1343,6 +1349,14 @@ def __init__(self, self._recording_format = recording_format self._recording_technique = recording_technique self._media_type = media_type + # CWR 2.2 additional fields + self._recording_title = recording_title + self._version_title = version_title + self._display_artist = display_artist + self._record_label = record_label + # Additional V2.2 trailing optional fields + self._isrc_validity = isrc_validity + self._submitter_recording_identifier = submitter_recording_identifier @property def ean(self): @@ -1504,6 +1518,54 @@ def recording_technique(self, value): self._recording_technique = value + @property + def recording_title(self): + return self._recording_title + + @recording_title.setter + def recording_title(self, value): + self._recording_title = value + + @property + def version_title(self): + return self._version_title + + @version_title.setter + def version_title(self, value): + self._version_title = value + + @property + def display_artist(self): + return self._display_artist + + @display_artist.setter + def display_artist(self, value): + self._display_artist = value + + @property + def record_label(self): + return self._record_label + + @record_label.setter + def record_label(self, value): + self._record_label = value + + @property + def isrc_validity(self): + return self._isrc_validity + + @isrc_validity.setter + def isrc_validity(self, value): + self._isrc_validity = value + + @property + def submitter_recording_identifier(self): + return self._submitter_recording_identifier + + @submitter_recording_identifier.setter + def submitter_recording_identifier(self, value): + self._submitter_recording_identifier = value + class InstrumentationDetailRecord(TransactionRecord): """ Represents a CWR Instrumentation Detail (IND) record. diff --git a/data_cwr/cwr_record_type.csv b/data_cwr/cwr_record_type.csv index 48f0fe8..4c030e6 100644 --- a/data_cwr/cwr_record_type.csv +++ b/data_cwr/cwr_record_type.csv @@ -1 +1 @@ -GRH,GRT,HDR,TRL,ACK,AGR,EXC,NWR,ISW,REV,ALT,ARI,COM,EWT,IPA,IND,INS,MSG,NAT,NCT,NET,NOW,NPN,NVT,NWN,OPU,ORN,OWR,PER,PWR,REC,SPT,SPU,SWR,SWT,TER,VER \ No newline at end of file +GRH,GRT,HDR,TRL,ACK,AGR,EXC,NWR,ISW,REV,ALT,ARI,COM,EWT,IPA,IND,INS,MSG,NAT,NCT,NET,NOW,NPN,NVT,NWN,OPU,OPT,ORN,OWR,PER,PWR,REC,SPT,SPU,SWR,SWT,TER,VER \ No newline at end of file diff --git a/docs/.DS_Store b/docs/.DS_Store new file mode 100644 index 0000000..d8a42c2 Binary files /dev/null and b/docs/.DS_Store differ diff --git a/docs/diagrams/Acknowledgements_PART_II.png b/docs/diagrams/Acknowledgements_PART_II.png new file mode 100644 index 0000000..dabead4 Binary files /dev/null and b/docs/diagrams/Acknowledgements_PART_II.png differ diff --git a/docs/diagrams/Bulk_work_flow_PART_I.png b/docs/diagrams/Bulk_work_flow_PART_I.png new file mode 100644 index 0000000..cf2abde Binary files /dev/null and b/docs/diagrams/Bulk_work_flow_PART_I.png differ diff --git a/docs/diagrams/CWR_Header:Group_Records.png b/docs/diagrams/CWR_Header:Group_Records.png new file mode 100644 index 0000000..008c155 Binary files /dev/null and b/docs/diagrams/CWR_Header:Group_Records.png differ diff --git a/docs/diagrams/CWR_Standard_High_Level.png b/docs/diagrams/CWR_Standard_High_Level.png new file mode 100644 index 0000000..1d2f93c Binary files /dev/null and b/docs/diagrams/CWR_Standard_High_Level.png differ diff --git a/docs/diagrams/CWR_Submission_Template.pdf b/docs/diagrams/CWR_Submission_Template.pdf new file mode 100644 index 0000000..7e76fb6 Binary files /dev/null and b/docs/diagrams/CWR_Submission_Template.pdf differ diff --git a/docs/diagrams/High_Level_Data_Flow.png b/docs/diagrams/High_Level_Data_Flow.png new file mode 100644 index 0000000..c877a15 Binary files /dev/null and b/docs/diagrams/High_Level_Data_Flow.png differ diff --git a/docs/source/.DS_Store b/docs/source/.DS_Store new file mode 100644 index 0000000..28ff01d Binary files /dev/null and b/docs/source/.DS_Store differ diff --git a/docs/source/_downloads/.DS_Store b/docs/source/_downloads/.DS_Store new file mode 100644 index 0000000..dd79535 Binary files /dev/null and b/docs/source/_downloads/.DS_Store differ diff --git a/docs/source/_downloads/CWR06-1950_CWR_Implementation_spreadsheet_2016-07-01_EN.pdf b/docs/source/_downloads/CWR06-1950_CWR_Implementation_spreadsheet_2016-07-01_EN.pdf new file mode 100644 index 0000000..9bfcf1c Binary files /dev/null and b/docs/source/_downloads/CWR06-1950_CWR_Implementation_spreadsheet_2016-07-01_EN.pdf differ diff --git a/docs/source/_downloads/CWR06-1972_CWR_sender_ID_and_codes_(April_2026)_2026-04-03_EN.xlsx b/docs/source/_downloads/CWR06-1972_CWR_sender_ID_and_codes_(April_2026)_2026-04-03_EN.xlsx new file mode 100644 index 0000000..93487ae Binary files /dev/null and b/docs/source/_downloads/CWR06-1972_CWR_sender_ID_and_codes_(April_2026)_2026-04-03_EN.xlsx differ diff --git a/docs/source/_downloads/CWR07-1411_CWR_Society_Questionnaire_2010-10-01_EN.xls b/docs/source/_downloads/CWR07-1411_CWR_Society_Questionnaire_2010-10-01_EN.xls new file mode 100644 index 0000000..74aa0a4 Binary files /dev/null and b/docs/source/_downloads/CWR07-1411_CWR_Society_Questionnaire_2010-10-01_EN.xls differ diff --git a/docs/source/_downloads/CWR08-1983_Survey_CWR_Publisher_Questionnaire_2010-10-06_EN.xls b/docs/source/_downloads/CWR08-1983_Survey_CWR_Publisher_Questionnaire_2010-10-06_EN.xls new file mode 100644 index 0000000..762b018 Binary files /dev/null and b/docs/source/_downloads/CWR08-1983_Survey_CWR_Publisher_Questionnaire_2010-10-06_EN.xls differ diff --git a/docs/source/_downloads/CWR08-2493_Specifications_CWR_Error_messages_2014-01-16_EN.pdf b/docs/source/_downloads/CWR08-2493_Specifications_CWR_Error_messages_2014-01-16_EN.pdf new file mode 100644 index 0000000..20251bc Binary files /dev/null and b/docs/source/_downloads/CWR08-2493_Specifications_CWR_Error_messages_2014-01-16_EN.pdf differ diff --git a/docs/source/_downloads/CWR08-3540_Specifications_CWR_Light_2008-11-13_EN.pdf b/docs/source/_downloads/CWR08-3540_Specifications_CWR_Light_2008-11-13_EN.pdf new file mode 100644 index 0000000..87c7f36 Binary files /dev/null and b/docs/source/_downloads/CWR08-3540_Specifications_CWR_Light_2008-11-13_EN.pdf differ diff --git a/docs/source/_downloads/CWR08-3615R1_CWR_2x_Lookup_Table_2021-09-16_EN.xlsx b/docs/source/_downloads/CWR08-3615R1_CWR_2x_Lookup_Table_2021-09-16_EN.xlsx new file mode 100644 index 0000000..720d1ef Binary files /dev/null and b/docs/source/_downloads/CWR08-3615R1_CWR_2x_Lookup_Table_2021-09-16_EN.xlsx differ diff --git a/docs/source/_downloads/CWR11-1991R4_Functional_specifications_CWR_version_2-1_Rev8_2019-10-18_EN.pdf b/docs/source/_downloads/CWR11-1991R4_Functional_specifications_CWR_version_2-1_Rev8_2019-10-18_EN.pdf new file mode 100644 index 0000000..3ec1859 Binary files /dev/null and b/docs/source/_downloads/CWR11-1991R4_Functional_specifications_CWR_version_2-1_Rev8_2019-10-18_EN.pdf differ diff --git a/docs/source/_downloads/CWR19-0479_Common_Works_Registration_User_Manual_2019-04-04_EN.pdf b/docs/source/_downloads/CWR19-0479_Common_Works_Registration_User_Manual_2019-04-04_EN.pdf new file mode 100644 index 0000000..d184d59 Binary files /dev/null and b/docs/source/_downloads/CWR19-0479_Common_Works_Registration_User_Manual_2019-04-04_EN.pdf differ diff --git a/docs/source/_downloads/CWR19-0479_Common_Works_Registration_User_Manual_2019-04-04_EN.txt b/docs/source/_downloads/CWR19-0479_Common_Works_Registration_User_Manual_2019-04-04_EN.txt new file mode 100644 index 0000000..dc9482a --- /dev/null +++ b/docs/source/_downloads/CWR19-0479_Common_Works_Registration_User_Manual_2019-04-04_EN.txt @@ -0,0 +1,1719 @@ + +CWR19-0479 + + +Source language: English +Published on: 04/04/2019 + + + + + + + + + + + + +Common Works Registration User Manual + +Recipient Submitter Forum + + +--- Page 2 --- + +Common Works Registration User Manual +CWR19-0479 2 of 39 + +Table of Contents +1. Introduction ................................ ................................ ................................ ................................ ......... 4 +1.1 CWR Process Overview ................................................................................................................................4 +2. File Structure ................................ ................................ ................................ ................................ ....... 7 +2.1 File Naming Convention ..............................................................................................................................7 +2.2 Control Records ...........................................................................................................................................8 +2.2.1 HDR: Transmission Header ......................................................................................................................8 +2.2.2 GRH: Group Header .................................................................................................................................8 +2.2.3 GRT: Group Trailer ...................................................................................................................................8 +2.2.4 TRL: Transmission Trailer ........................................................................................................................8 +2.3 Transactions ................................................................................................................................................8 +3. Registering Work Information ................................ ................................ ................................ .............. 9 +3.1 Work Title and Core Information ............................................................................................................. 10 +3.2 Interested Parties and Collection Shares ................................................................................................. 11 +3.2.1 Publishers ............................................................................................................................................. 12 +3.2.2 Publisher Collection Shares ................................................................................................................. 14 +3.2.3 Writers ................................................................................................................................................. 16 +3.2.4 Writer Collection Shares ...................................................................................................................... 18 +3.2.5 Linking Writers to Publishers .............................................................................................................. 18 +3.3 Alternative Titles ...................................................................................................................................... 19 +3.4 References to Other Works ..................................................................................................................... 20 +3.5 Live Performing Artists ............................................................................................................................ 21 +3.6 Recording Detail ....................................................................................................................................... 21 +3.7 Work Origin .............................................................................................................................................. 23 +3.8 Audio-visual Productions ......................................................................................................................... 24 +3.9 Instrumentation ....................................................................................................................................... 25 +3.9.1 Instrumentation Summary .................................................................................................................. 25 +3.9.2 Instrumentation Detail ........................................................................................................................ 26 +3.10 Work ID Cross Reference ......................................................................................................................... 26 +4. Retracting Work Registrations ................................ ................................ ................................ ............ 26 +5. Acknowledgements ................................ ................................ ................................ ............................ 27 +5.1 Transaction Status ................................................................................................................................... 28 +5.1.1 CO: Transaction in Conflict .................................................................................................................. 28 +5.1.2 RA: Registration Accepted - Passed Validations ................................................................................ 29 +5.1.3 AS: Registration Accepted – Not Ready for Payment ......................................................................... 29 +5.1.4 AC: Registration Accepted With Changes– Not Ready for Payment ................................................. 29 +5.1.5 SR: Registration Accepted –Ready for Payment ................................................................................. 29 +5.1.6 CR: Registration Accepted With Changes – Ready for Payment ........................................................ 29 +5.1.7 RJ: Registration Rejected - Failed Validations .................................................................................... 29 +5.1.8 NP: No Participation ............................................................................................................................ 29 +5.1.9 DR: De-registered ................................................................................................................................ 30 +5.1.10 UN: Unknown Work in DRW ........................................................................................................... 30 +5.1.11 LD: Unable to De-register ............................................................................................................... 30 +5.1.12 NA: No Society Agreement Number ............................................................................................... 30 +5.1.13 WA: Wrong Society Agreement Number ........................................................................................ 30 + +--- Page 3 --- + +Common Works Registration User Manual +CWR19-0479 3 of 39 + +5.2 Messages .................................................................................................................................................. 30 +5.3 Existing Work in Conflict with Submitted Work ..................................................................................... 31 +6. ISWC Confirmation and Allocation ................................ ................................ ................................ ...... 31 +6.1 Request for Confirmation/Allocation of ISWC ........................................................................................ 31 +6.2 Confirmation of ISWC .............................................................................................................................. 31 +6.3 Writer for ISWC ........................................................................................................................................ 32 +7. License Reporting Transaction ................................ ................................ ................................ ............ 32 +8. Workflow Diagrams ................................ ................................ ................................ ........................... 33 +9. Implementing CWR ................................ ................................ ................................ ............................ 35 +9.1 Testing Procedures – Submitter .............................................................................................................. 35 +9.2 Testing Procedures – Recipients.............................................................................................................. 36 +9.3 Production ................................................................................................................................................ 36 +10. Examples of the file structure ................................ ................................ ................................ ......... 37 +11. Glossary ................................ ................................ ................................ ................................ ......... 38 + + + + +--- Page 4 --- + +Common Works Registration User Manual +CWR19-0479 4 of 39 + +1. Introduction + +The purpose of the Common Works Registration (CWR) format is to provide Submitters and Recipients with a +standard format for the communication data relating to works and specifically publisher and writer collection +shares in those work. Throughout this document , the Submitter can usually be taken to be a publisher and a +Recipient can usually be taken to be a society. + +CWR v3.0 was adopted as a CISAC standard by the Information Services Committee (ISC) at its meeting on April +4th, 2019 in Nice. + +The CWR employs data standards that have been developed for the Common Information System (CIS) project +of CISAC. Using existing standards for codes will eliminate confusion. + +In this user manual you will find all the necessary tools to develop and implement the CWR format. Please read +through the information carefully and contact your local representative with any inquiries. + +Welcome to CWR! + +1.1 CWR Process Overview + +After a Submitter acquires a work and enters it into its database, the work is formatted to meet CISAC CWR +standards. The Submitter may choose one two methods to circulate the file. + +Some Submitters may have their office send the same CWR file to all Recipients at once. + + +Other Submitters may send CWR files with only Recipient relevant data to each Recipient. + + + + +--- Page 5 --- + +Common Works Registration User Manual +CWR19-0479 5 of 39 + +Once the Recipient retrieves the file from its server and applies a first round of technical validation rules (known +as edits) to the data included in the file, the 1st acknowledgement is returned to the Submitter within 24 to 48 +hours. The 1st acknowledgement will contain the status of the file, its contents, and will include any errors that +were encountered. When the works with in the file pass the CWR edits and Recipient validation, the 1st +acknowledgement will be an ‘RA’ (Registration accepted). If the works in the file do not meet the minimum file +requirements, they will be rejected (RJ status) and returned to the Submitter to correct and resubmit. Message +(MSG) records explain the reason for the rejection. The Recipient will then process the works in ‘RA’ status. + + + +After the Recipient has processed the contents of the file, 2nd acknowledgements will be sent in groups as works +are registered and made payment-ready. When and how Recipients send 2nd acknowledgments will vary, but a +weekly file with the works processed in that time period is common. This is known as the “drip-feed” method. +Due to the volume of works in some CWR files, the “drip-feed” method is used so that Submitters begin to receive +2nd acknowledgements in a timely manner as works are processed. Other CWR Recipients may choose to only +send 2nd acknowledgements once the entire file has been processed. This is called the “one file method.” + +The 2nd acknowledgement file will include Recipient work numbers for the individual works, IPI Number’s for +interested parties, names for all interested parties, and ISWC numbers (if the work meets the necessary criteria). +ISWCs are only issued when all interested parties on a work are identified by their IPI number. Works with +participants who are not affiliated with a Recipient, or works that list any “unknown” shares are not eligible for +ISWC numbers. In some instances, multiple ISWC numbers may be issued by 2 or more Recipients. When this +occurs, the ISWC number issued first is labelled as the “preferred ISWC.” Any subsequent ISWC numbers issued +will be labelled as “archived ISWC” and will be linked to the “preferred.” + +The 2nd acknowledgement will also include codes and error messages for works that could not be registered. +Some common reasons for rejection are: +• Writer and Submitter Recipient affiliation does not match +• Incomplete sample information +• The sample indicator flagged with no composite information included +• Conflicting administrator information +• The information submitted conflicts with a previous registration received by the Recipient. + +Where share or IP information conflicts with what is on file at the Recipient, a record (EXC) can be sent by the +Recipient to the Submitter indicating the IP/share information in the Recipient database. The Submitter should +use the EXC record to resolve work dis crepancies before re-submitting the work in a subsequent CWR file. It is +essential that Submitters populate their databases with the information included in the 2nd acknowledgement. + + +--- Page 6 --- + +Common Works Registration User Manual +CWR19-0479 6 of 39 + + + +Equally important is the processing of CWR rejections in the 2nd acknowledgement file. These messages notify +the Submitter of issues with their song information that may also result in delayed royalty payments. Timely +processing and resolution of issues th at arise from these rejections will reduce and many times prevent these +delays. When information submitted by a Submitter is rejected due to conflicting information on a previous +registration, the EXC record returned with the 2nd acknowledgement is a vital tool in resolving share +discrepancies. Processing the EXC record provided by the Recipients will allow the Submitter to review the +conflicting information and resolve any issues directly with the interested parties on the registration. This cuts +out the step of inquiry with the Recipients and creates efficiencies in the resolution process. + +By developing and utilizing CWR, both Submitters and Recipients benefit from efficiencies in the form of time +and cost savings. In addition, the common format result s in a more accurate flow of song data between +Submitters and Recipients within the country of origin and throughout the world. This shared standard reduces +time intensive inquiries as well as increases the accuracy of royalty payments from the Recipients to the +Submitters. + + + +--- Page 7 --- + +Common Works Registration User Manual +CWR19-0479 7 of 39 + +2. File Structure + +Note that the File Naming Convention has been modified by the CWR Management Committee to better suit the +needs of CWR. It no longer conforms to the convention specified in the CISAC Standards. + +2.1 File Naming Convention + +The file naming convention is as follows and should be used for all regular submissions from a given Submitter +to a Recipient: +CWYYnnnnSUB_REP_VM-m-r.EXT +Where: +CW Indicates that the file is a CWR file +YY Is the 2 digit year +nnnn Is a file number. The number must be ascending within a year, but need not be contiguous. +SUB Is the 2 -4 alphanumeric Transmitter ID of the file submitter +REP Is the 2 -4 alphanumeric Transmitter ID of the file recipient +VM-m Is the CWR version in use M=Major Version number m=minor version number +r Is the revision number. +EXT “SUB” – Submitted Work Registration Data File / “ACK1” – Technical Acknowledgement File / “ACK2” – +Claim Acknowledgment File / “ISWS” – ISWC Allocation and Resolution Services Submission File / +“ISWA” – ISWC Allocation and Resolution Services Acknowledgement File + +It is recommended that all files are compressed using the standard zip format and that If the file is zipped, it will +be named CWYYnnnnSUB_REP_VM-m-r_EXT.zip +The unzipped file contained in a zipped file should be named as per the standard naming convention above. +Note that if the same file is being sent to several Recipients, use ‘000’ as the Transmitter ID. +EXAMPLE: +A Submitter SA sends its regular CWR file number 37 using the CWR 3.0 revision 0 to SACEM: + CW170037SA_058_V3-0-0.SUB + +SACEM would send the ACK1 for that submitted file: + CW170058058_SA_V3-0-0_ACK1.zip + +SACEM would then “drip-feed” ACK2 files containing works from the submitted file, perhaps zipped: + CW170048058_SA_V3-0-0_ACK2.zip + CW170053058_SA_V3-0-0_ACK2.zip + CW170058058_SA_V3-0-0_ACK2.zip + + +--- Page 8 --- + +Common Works Registration User Manual +CWR19-0479 8 of 39 + +2.2 Control Records +The following record layouts are used to partition and control the submission of files between participants. +Proper control records are required within the file to insure the integrity of transmission over telecommunication +lines, as well as confirming that the data within the file has not been altered as a result of intentional or +unintentional tampering with data. Control records defined within this version of the standard are: +• HDR: Transmission Header +• GRH: Group Header +• GRT: Group Trailer +• TRL: Transmission Trailer + +2.2.1 HDR: Transmission Header +The Transmission Header Record (HDR) is a required “cover sheet” for transmissions submitted by a participant. +It will contain the file control information as well as the name of the submitter. + +2.2.2 GRH: Group Header +The Group Header Record (GRH) is used to indicate the presence of a group (or batch) of transactions within the +file. A group can only contain one type of transaction and this is indicated in the Transaction Type field. Also, all +transactions of the same type should be contained in the same group (e.g. all WRK transactions should appear +in one single WRK group) and each group type can only be used once per file (e.g. there can only be one WRK or +one ACK group per file). + +2.2.3 GRT: Group Trailer +The Group Trailer Record (GRT) indicates the end of a group and provides both transaction and record counts for +the group. + +2.2.4 TRL: Transmission Trailer +The Transmission Trailer Record (TRL) indicates the end of the transmission file. Control totals representing the +number of groups, transactions, and records within the file are included on this record. + +2.3 Transactions +A transaction is defined as “all the information required to complete a logical unit of work that is to be passed +between two or more participants in the electronic relationship.” This version of the format contains definitions +for the following transaction types: +• WRK: Submission of a work details for registration. +• DRW: Retraction of a WRK submitted in error. +• ISW: Request for an ISWC from the ISWC Allocation Service or the ISWC Resolution Service. +• ISA: Notification of ISWC assigned to a work. +• EXC: Existing work which is in conflict with a work as submitted. +• ACK: Provides acknowledgment of WRK or DRW transactions and subsequent work history. +• LIC: Licensing information relating to an existing work. + + +--- Page 9 --- + +Common Works Registration User Manual +CWR19-0479 9 of 39 + +3. Registering Work Information + +When you are registering a new work or updating an old work, use the WRK transaction. Detail records are listed +subsequent to the WRK Header Record providing further information on the content and collection shares and +territories of the work. For revised works it is mandatory to provide all work details in the transaction (not just +the information which has changed). It is possible (because of Recipient editing rules) that a work may be rejected +by one Recipient and accepted by another. + +As a Submitter, you may choose to send one file containing registration information for many territories to many +Recipients, or you may choose to send to each Recipient a file containing only information pertinent to that +Recipient. If, when processing a file, a Recipient determines that it has no interest in a particular work +registration, the Recipient will acknowledge that work with a status code of ‘no interest’ (NP). A work is generally +of interest to a Recipient if a shareholder belongs to that Recipient, or if the collection rights are for a territory +that the Recipient administers on behalf of the submitting Submitter. Otherwise the work will be of no interest. +Also, the work may be of no interest because of the type of rights. For example, if a performing rights Recipient +receives a registration for only mechanical rights for a work, the work will be returned as NP. + +There is a temptation to store other information in the title e.g. “background”. This is not a good idea. In the +past when each title registration was done manually, a person could sort the other information from the title +and act appropriately. Now that registrations are automated this does not happen. The title match routines will +not work properly and the additional information is lost. The additional information formerly stored in that title +should have a place of its own. If it does not, please raise it to our attention so that we can add new fi elds to +store this information. + +If there are other versions of this work that have a different set of interested parties, or a different percentage +split among the interested parties, submit separate registrations. + +The collection shares for each right being registered must total 100% for each work in all territories for which the +Submitter is making a claim. + +A composite musical work such as a symphony may contain several movements. If the movements are likely to +be performed or recorded on their o wn, then it is advisable to register each movement as a separate musical +work. Each movement can refer to the symphony as the entire work from which it is derived in the original work +record (OWK). + +A composite musical work such as a medley or sample c an use the original work record (OWK) to describe the +works that are included. + + + +--- Page 10 --- + +Common Works Registration User Manual +CWR19-0479 10 of 39 + +3.1 Work Title and Core Information + +The Submission of Work Record (WRK) contains core information about the work itself, such as title and the +unique codes that have been assigned to it. Other information, like writer names, recordings, and other versions +will be asked for later in the transaction in separate record types. + +Record Prefix. This allows you to indicate a work (WRK). + +Work Title. List the title by which the work is best known. You will have an opportunity to list variations on this +title in the ALT record. Do not store additional information in the title field e.g. “instrumental” or “background”. +Such information should be stored in the designated field. + +Language Code. Indicate the language of the work title. If the title crosses languages (e.g., Maria), list the +language of the lyrics. This information will assi st Recipients in identifying the work. These values reside in the +Language Code Table. + +Submitter Work Number. This is your unique numerical code for this work. It is important that this number refer +only to the work named on the registration, since further electronic communication (ACK, ISW, EXC) that includes +this number will point to this work and its interested parties. + +ISWC. The International Standard Work Code assigned to this work. + +Copyright Date. This is the date that your national copyright office has registered this work. + +Copyright Number. This is the number that your national copyright office has assigned to this work upon +registration. + +Musical Work Distribution Category. Certain rights organizations have special distribution rules t hat apply to +certain genres of music. All such genres for participating Recipients can be found in the Musical Work +Distribution Category Table in the layout document. + +Duration. Duration is required: +• by all Recipients if the Musical Work Distribution Category is Serious (e.g., music intended for symphonic, +recital and chamber settings); +• if there is a BMI interested party in this work and the Musical Work Distribution Category is Jazz. + +Recorded Indicator. Indicate whether a recording of this work exists that has been made available to the public. + +Text-Music Relationship. Indicate whether this work contains text only, music only, or a combination of both. (It +is understood that a work with lyrics may be p erformed instrumentally, and that a work with music may be +performed spoken-only.) + +Composite Type. Certain works incorporate other works. If this work is such a case, choose the type of composite +from the values in the table. + + +--- Page 11 --- + +Common Works Registration User Manual +CWR19-0479 11 of 39 + +Version Type. Indicate whether this work is entirely original, or based on another work. If the work is based on +another work, values must be given for the Music Arrangement and Lyric Adaptation fields. If the work is a +modified version of a copyrighted work, it is necessary for it to be authorized. + +Excerpt Type. If this work is part of a larger work, indicate whether this is a movement or another, unspecified +type of excerpt. + +Music Arrangement. If you’ve indicated that this is a modified version of another work, you must indicate here +what changes, if any, have occurred to the original music. + +Lyric Adaptation. If you’ve indicated that this is a modified version of another work, you must indicate here what +changes, if any, have occurred to the original lyric. + +Grand Rights Indicator. It can be of interest whether or not this work is originally intended for live theatrical +performance. + +Composite Component Count. If a work consists of one original work and one sample, then the component count +is two. + +Date of Publi cation of Printed E dition. The date that the printed, new edition published by the submitting +Submitter appeared. This information is especially relevant for the notification of sub-published works by GEMA- +sub-Submitters. + +Exceptional Clause. This is for registrations with GEMA. By entering Y (Yes), the submitting GEMA-sub-Submitter +declares that the exceptional clause of the GEMA distribution rules with regard to printed editions applies +(GEMA-Verteilungsplan A Anhang III). + +Opus Number. The number assigned to this work, usually by the composer. Part numbers are to be added with +a # e.g. 28#3 (meaning Opus 28 part 3). + +Catalogue Number. The work catalogue number. The abbreviated name of the catalogue is to be added (like +BWV, KV), without dots. Part numbers are to be added with a # e.g. KV 297#1 (meaning Köchel Verzeichnis Nr.297 +part 1). + +Priority Flag. Use this flag to indicate that the registration of this work should be expedited. This flag should be +used sparingly – only when the work is high on the charts, etc. + +3.2 Interested Parties and Collection Shares + +CWR requires that you distinguish between those writers and Submitters under your control, i.e., on whose +behalf you are submitting this registration, and those whose interest will be submitted by another organization. +Information that you give about those writers and Submitters not under your control will be subject to les s +stringent editing rules than information about your writers and Submitter(s). + + + + +--- Page 12 --- + +Common Works Registration User Manual +CWR19-0479 12 of 39 + +It is important to note that if you supply unique identifiers to the interested parties, particularly, IPI numbers, +your registration will be processed much faster. The Recipient of affiliation is also a key piece of information that +should be provided whenever possible – particularly if the IPI number cannot be determined. + +Even though it is not necessary to provide much detail about interested parties not under your control, you are +required to account for 100% of the work’s collection in all territories in which you are claiming publisher +collection rights. This means the percentages allocated across all writers, arrangers and original Submitters must +total 100. If you have no information about writers and Submitters in your work other than your own, you may +so indicate via the “writer unknown” or “Publisher unknown” indicator and you must allocate to that unknown +entity the balance of the share entitlement. + +Some Recipients do not accept Unknown Writer or Unknown Submitter. Please contact your local Recipient to +learn about this. + + +Note that there is a tolerance of plus or minus .06% while applying the edits relating to the sum of shares. + +3.2.1 Publishers +CWR requires that you group your original publisher with any local administrator or foreign sub-publisher(s) in a +publisher chain. + +The original publisher starts the chain. It is followed by the administrators, sub-publishers, and income +participants. + +An income participant may start a chain, or be included in a chain begun by the original publisher which has +allocated rights to the income participant. + +If a publisher is both a co-publisher and an administrator, it must appear in two chains – in one, it will start the +chain as an original publisher; in the other it will follow the co-publisher on whose behalf it administers the rights. + +An Acquirer is a publisher that has acquired some or all of the rights of a work from the Original publisher. +Furthermore, the acquirer has the direct relationship to the writers of the musical work (unlike the sub-publisher +and the administrator that have a direct re lationship with another publisher). The difference between an +Acquirer and an original publisher being that the original publisher has passed its direct relationship with the +writer to the acquirer. To be clear, where a publisher becomes the owner as a re sult of reversion or copyright +termination/renewal they are the original publisher (E) not the acquirer (AQ). + + +--- Page 13 --- + +Common Works Registration User Manual +CWR19-0479 13 of 39 + +The Acquirer would act very much like an Original publisher (role code 'E'), although the Original publisher would +still be shown on the work before the Acquirer. + +The only differences between an Original publisher and an Acquirer would be: +• You can only have one Original publisher per chain of title, but you could have more than one Acquirer. +• The Acquirer comes after an Original publisher, so it doesn't start the chain of title. + +An example of the structure of the work would be as follows: +Record Name Role Collection +SPU A Original Publisher +SPU B Acquirer +SPT B Acquirer Collection share for +home territory +SPU C Sub-Publisher +SPT C Sub-Publisher Collection share for +other territories + +CWR enables you to indicate every territory or set of territories where your original publisher, administrators, or +sub-publisher have a collection interest. For those publishers under your control that have a collection interest, +you must indicate at leas t one territory and corresponding share entitlement in which that collection interest +applies. If there is an administrator with no collection shares for any territory, it is possible to list it on a publisher +record. It, of course, would have no territory records. + +Record Prefix. This allows you to distinguish whether or not this publisher is under your control (SPU) or the +control of another organization (OPU). + +Publisher Sequence Number. This enables a rights organization to link sub- publisher s and administrators to the +proper original publisher. Each original publisher will start a new chain. An income participant may start a chain, +or be included in a chain begun by the original publisher which has allocated rights to the income participant. + +Interested Party Number. This is your unique numerical code for this publisher. It is important that this number +refer only to the publisher named on the registration. Never re -use an interested party number for a different +publisher since this could cause the Recipients to merge the catalogue of the first publisher with the catalogue +of the second publisher with the same interested party. + +Publisher Name. The name of this publishing company as it is on file with its rights organization. +For a publisher not under your control, it is not required to provide a name, however it should be indicated using +the Publisher Unknown Indicator below. + +Publisher Unknown Indicator. For a publisher in this work not under your control and for whom you do not have +a name on file, this flag may be set to “Y” for yes, however otherwise it should be left blank . Do not enter a +publisher name if you choose this option. However, by providing the name (if kno wn), the registration can be +made payable more quickly. + +Publisher Role. Role played by this publisher in this work, i.e. role codes E, SE or AM. + +Tax ID Number. A number used to identify this publisher for tax reporting. + + +--- Page 14 --- + +Common Works Registration User Manual +CWR19-0479 14 of 39 + +Publisher IPI Name Number. The unique identifier associated with this publisher name. + +Publisher IPI Base Number. The unique identifier associated with this publisher. + +USA License Ind. This field indicates whether rights for this publisher flow through ASCAP, BMI, AMRA, or SESAC +for the U.S. + +Note, for publishers with non -Roman alphabet names, an additional Non -Roman Alphabet Publisher Name +Record (NPN) can be used to identify the language and the script or alphabet in which the language is written. + +3.2.2 Publisher Collection Shares +The collection shares for each set of territories are defined using the territory record. The original publishers, or +income participants, and their administrators and sub- publishers are tied together using the interested party +number. It is possible to show a publisher that has no collection shares. + +For example, if Warner US has an agreement with Warner International for the administration for the world +except for the US. Warner International does not collect any shares, but has agreements with Warner affiliates +for each territory. Warner International can be present with no SPT. + +You can use more than one territory record to describe the territories assigned. For example, if you wish to +register a work showing a sub-publisher for Europe excluding Germany, supply an SPT including territory of +Europe with the collection shares, and another SPT to exclude the territory of Germany with no collection shares. +Note that the exclude always refers to the territory in the previous include. + +The total collection shares for a territory for a rights type for a work cannot exceed 100%. + +The sequence number should run from 1 to the number of SPTs for each SPU. +Example: A works notification has three SPU records. Each SPU record is linked with a number of SPT records +that indicate the territory of control of the publisher in that SPU record. + +• SPU for Original Publisher +The Original Publisher collects in the whole world. This SPU record is connected with one SPT record: +Sequence nr Incl / Excl TIS Numeric +1 I 2136 + +• SPU for Administrator Publisher +The Administrator Publisher collects in the world ex cluding Commonwealth but including Canada. This SPU +record is connected with three SPT records: +Sequence nr Incl / Excl TIS Numeric +1 I 2136 +2 E 2114 +3 I 124 + + + + + + + +--- Page 15 --- + +Common Works Registration User Manual +CWR19-0479 15 of 39 + +• SPU for Sub-Publisher +The Sub-Publisher collects in Europe excluding UK and excluding Ireland. This SPU record is connected with three +SPT records: +Sequence nr Incl / Excl TIS Numeric +1 I 2120 +2 E 826 +3 E 372 + +Exclusions from exclusions must be entered positively, i.e. with Inclusion Indicator I. See above example with the +Administrator Publisher. The agreement is valid for “World excluding Commonwealth but including Canada ”. +This is to be entered as (for clarit y sake the full territory names and not the territory codes together with their +territory start dates are used here): ++World +-British Commonwealth ++Canada + +The individual territories are to be entered in their correct (logical) order. The order is defined by the sequence +number of territory. The inclusions and exclusions are to be interpreted according to these sequence numbers. +The above example must be entered with the following sequence numbers: +Sequence#1 +World +Sequence#2 -British Commonwealth +Sequence#3 +Canada + +The following order is illogical: +Sequence#1 -British Commonwealth +Sequence#2 +World +Sequence#3 +Canada + +Please also note the difference between: +Sequence#1 +World +Sequence#2 -British Commonwealth +Sequence#3 +Canada (Result: Canada is included) +and: +Sequence#1 +World +Sequence#2 +Canada +Sequence#3 -British Commonwealth (Result: Canada is not included) + +Record Prefix. This allows you to specify the collection shares for each set of territories for publishers. It allows +you to distinguish whether or not this collection is under your control (SPT) or the control of another organization +(OPT). ( + +Interested Party Number. This is your unique number that identifies the publisher that has collection rights in +this territory. This publisher was described in the preceding SPU/OPU record. + +PR Collection Share. This field records the percentage of performing rights royalties that are to be collected. + +MR Collection Share. This field records the percentage of mechanical rights royalties that are to be collected. + + +--- Page 16 --- + +Common Works Registration User Manual +CWR19-0479 16 of 39 + +SR Collection Share. This field records the percentage of synchronization rights royalties that are to be collected. + +Inclusion/Exclusion Indicator. This indicates an “I” for include or an “E” for exclude for the following territory. + +TIS Numeric Code. This is a code that describes a territory or group of territories. + +PR Affiliation Society Number. The number assigned to the Performing Rights Society with which the publisher +is affiliated in the territory described in this territory record. + +MR Affiliation Society Number. The number assigned to the Mechanical Rights Society with which the publisher +is affiliated in the territory described in this territory record. + +SR Affiliation Society Number. The number assigned to the Synchronization Rights Society with which the +publisher is affiliated in the territory described in this territory record. + +Special Agreements Indicator. This field indicates that the publisher claims reversionary rights in the territory +described in this record. Note that this flag only applies to societies that recognize reversionary rights (for +example, SOCAN). + +First Recording Refusal Ind This field indicates that the submitter needs to be asked before the Recipient can +authorize a first recording. Note that this field is mandatory for registrations with the UK Recipients. + +Submitter Agreement Number. This field contains your unique number used to identify the agreement under +which this publisher has acquired the rights to this work. + +Society-Assigned Agreement Number. This field contains the agreement number assigned to this agreement by +the society of the sub-publisher. + +Agreement Type. This field contains the code defining the category of the agreement. + +Recipient ID. This field contains the intended recipient of this SPT/OPT record. + +Sequence Number. A number assigned sequentially to each territory record which applies to the immediately +preceding interested party. + +3.2.3 Writers +Writers under your control must be linked to those publishers to whom they have assigned their publishing +interest. There is the requirement to specify the territory and collection share (if greater than zero) for each right +for writers. If the writer has no collection share for any right being registered, then it is not necessary to submit +a territory/collection record (SWT). + +A writer should appear only once per role within a work. It is necessary to submit at least one composer, or +author for each work. If a work is in the public domain, the writer must still be specified. + +If you’ve indicated that your work is a modified version of another work, at least one of the writers must be given +as an arranger, sub-arranger, translator, adapter, or sub-author. + + +--- Page 17 --- + +Common Works Registration User Manual +CWR19-0479 17 of 39 + +Record Prefix. This allows you to tell Recipients whether or not this writer is under your control (SWR) or the +control of another organization (OWR). + +Interested Party Number. This is your unique numerical code for this writer. It is important tha t this number +refer only to the writer named on the registration. Do not reuse the interested party number as some Recipients +store this number as a reference. + +Writer Last Name. The last name of the writer. If you do not have the ability to separate the last name from the +first name, then you may include both the last and first name in this field separated by a comma. This field is +mandatory for writers that you control. For writers which you do not control, you can check the Writer Unknown +Indicator if you do not know the name. + +Writer First Name. The first name of the writer. + +Writer Unknown Indicator. For a writer in this work not under your control and for whom you do not have a +name on file, this flag may be set to “Y” for yes. + +Writer Role C ode. This code describes the role of the writer with respect to this work e.g. composer, author, +arranger. This field is required for all writers. + +Tax ID Number. A number used to identify this writer for tax reporting. + +Writer IPI Name Number. The unique identifier associated with this writer name + +Writer IPI Base Number. The unique identifier associated with this writer. + +Personal Number. This field contains the personal number assigned to this individual in the country of residence. +For Sweden, it has the format YYMMDD9999. + +Reversionary Indicator. This indicates that the writer is claiming the work under the reversionary provisions. +Only some Recipients recognize reversionary rights. + +First Recording Refusal Ind This field indicates that the submitter needs to be asked before the Recipient can +authorize a first recording. Note that this field is mandatory for registrations with the UK Recipients. + +Work For Hire Indicator. This field indicates that this writer was hired to write this work. + +USA License Ind. This field indicates that this writer has elected to have this work represented in the U.S. by BMI, +ASCAP, AMRA, or SESAC. + +Note, for writers with non -Roman alphabet names, an additional Non -Roman Alphabet Writer Name Record +(NWN/NOW) can be used to identify the language and the script or alphabet in which the language is written. + + + +--- Page 18 --- + +Common Works Registration User Manual +CWR19-0479 18 of 39 + +3.2.4 Writer Collection Shares +The collection shares for writers by territory work in the same way as the collection shares for publishers. If the +writer’s share changes on sub-publication, then you will need an SWT /OWT to describe the shares collected in +the originating territory, and one or more SWT/OWT to describe the shares collected in the territories where the +work is sub-published. + +Record Prefix. This allows you to specify the collection shares for each set of territories for writers. It enables +you to distinguish whether or not thi s writer is part of a controlled chain (SWT) or of a non -controlled chain +(OWT). + +Interested Party Number. This is your unique number that identifies the writer that has collection rights in this +territory. This writer was described in the preceding SWR/OWR record. + +PR Collection Share. This field records the percentage of performing rights royalties that are to be collected. + +MR Collection Share. This field records the percentage of mechanical rights royalties that are to be collected. + +SR Collection Share. This field records the percentage of synchronization rights royalties that are to be collected. + +Inclusion/Exclusion Indicator. This indicates an “I” for include or an “E” for exclude for the following territory. + +TIS Numeric Code. This is a code that describes a territory or group of territories. + +PR Affiliation Society Number. The number assigned to the Performing Rights Society with which the writer is +affiliated in the territory described in this territory record. + +MR Affiliation Society Number. The number assigned to the Mechanical Rights Society with which the writer is +affiliated in the territory described in this territory record. + +SR Affiliation Society Number. The number assigned to the Synchronization Rights Society with which the writer +is affiliated in the territory described in this territory record. + +Recipient ID. This field contains the intended recipient of this SWT/OWT record. + +Sequence Number. A number assigned sequentially to each territory record which applies to the immediately +preceding interested party. + +3.2.5 Linking Writers to Publishers +It is valuable for the Recipients to know the publisher associated with each writer. This provides a complete trail +of the rights -- from the creator to the publisher to sub- publisher or administrators. For each writer who is under +your control, complete one Publisher for Writer Record (PWR) for each publisher to which they have assigned +rights for this work. + + + +--- Page 19 --- + +Common Works Registration User Manual +CWR19-0479 19 of 39 + +Some Recipients require that the Recipient-assigned agreement numbers be present in a work registration. The +writer-to- publisher agreement numbers are recorded in this record. The reason is that if two or more writers +for a work have an agreement with the same original publisher, it is possible to record each Society-Assigned +Agreement Number and Submitter Agreement Number in the PWR record that links that writer to the original +publisher. + +Record Prefix. This allows you to indicate writer to publisher links (PWR). + +Publisher IP Number. This field contains the unique identifier of the publisher to whom this writer has assigned +rights. + +Writer IP Number. This field contains the unique identifier of the writer. + + PR Affiliation Society Number. The number assigned to the Performing Rights Society with which the agreement +between the writer and the publisher is registered. + +MR Affiliation Society Number. The number assigned to the Mechanical Rights Society with which the +agreement between the writer and the publisher is registered. + +SR Affiliation Society Number. The number assigned to the Synchronization Rights Society with which the +agreement between the writer and the publisher is registered. + +Submitter Agreement Number. This field contains your unique number used to identify the agreement between +the writer and publisher being linked. + +Society-Assigned Agreement Number. This field contains the agreement number assigned to this agreement by +the society of the sub-publisher. + +Agreement Type. This field contains the code defining the category of the agreement. + +Publisher Sequence Number. Reference to the publisher chain this writer-publisher link relates to. + +3.3 Alternative Titles + +If the work is known by more than one title, then all titles should be documented. The 'official' title appears in +the WRK record. All other titles are recorded in the alternative title record. There are several types of titles. The +most common type is th e alternative title (AT). There is also the first line of text (TE). A formal title (FT) for a +serious work has a pre-defined format. + +Sometimes you may be aware of the title as it is translated into another language. This is particularly useful for +the identification of usages. Please note that if the lyrics or music has been changed, it should be considered a +different work. However, if only the title has been translated, then the language and the translated title (TT) can +be provided in the ALT record. + +Record Prefix. This allows you to indicate alternative titles (ALT) for a work. + +Alternative Title. This field is for the alternative titles. Do not store additional data with the title. + +--- Page 20 --- + +Common Works Registration User Manual +CWR19-0479 20 of 39 + +Title Type. This field describes the type of title. + +Language Code. This field contains the code used to describe the language of the alternative title. These values +reside in the Language Code Table. + +Note, for alternative titles using a non -Roman alphabet, an additional Non-Roman Alphabet Title Record (NAT) +can be used to identify the language and the script or alphabet in which the language is written. + +3.4 References to Other Works + +Often a work has a relationship to another work. It is useful to know this relationship. The CWR provides a way +of documenting three types of relationships amongst works - excerpts, versions, and composites - by populating +the relevant fields in the WRK Record and by popula ting the Original Work Details Record (OWK) to document +the referenced (original) work. To help us to identify the original work, provide one or two of the writers of the +original work. + + +Record Prefix. This allows you to specify details of the Original Work. + +Original Work Title. This field contains the title of the original work. + +ISWC of Original Work. If you know the ISWC of the original work, record it here. + +Submitter Original Work Number. The unique number that you have assigned to the original work that is unique +to you. + +Opus Number. The number assigned to the original work, usually by the composer (e.g. 28#3 meaning Opus 28 +part 3). + +Catalogue Number. The catalogue number of the original work including the abberviated name wihtout dots +and the part numbers with a # (e.g. KV 297#1 meaning Köchel Verzeichnis Nr.297 part 1) + +Duration. The duration of the original work. + +Language Code. Indicates the language of the original work title. These values reside in the Language Code Table. + +Writer 1 Last Name. If the ISWC is not known, then the last name of a writer is helpful to identify the work. + +Writer 1 First Name. The first name of the writer. + +Writer 1 IPI Name Number. The unique identifier associated with the first writer name. + +Writer 1 IPI Base Number. The unique identifier associated with the first writer name. + + +--- Page 21 --- + +Common Works Registration User Manual +CWR19-0479 21 of 39 + + +Writer 2 Last Name. If the ISWC is not known, then the last name of a second writer is helpful to identify the +work. + +Writer 2 First Name. The first name of the second writer. + +Writer 2 IPI Name Number. The unique identifier associated with the second writer name. + +Writer 2 IPI Base Number. The unique identifier associated with the second writer name. + + +Note, for original work titles using a non-Roman alphabet, an additional Non-Roman Alphabet Original Work Title +(NOT) can be used to identify the language and the script or alphabet in which the language is written. + + +3.5 Live Performing Artists + +The name of performing artists and performing groups can be particularly valuable to Recipients trying to identify +usages of a work. Please include all of the performing artists or performing groups who perform this musical +work in public, using one record per artist or group. + +Record Prefix. This allows you to specify the performing artists (PER). + +Performing Artist Last Name. The last name of the performing artist. If the performing artist has only one name, +e.g. Cher, then record it here. Use this field also for group names. + +Performing Artist First Name. The first name of the performing artist. + +Performing Artist IPI Name Number. The unique identifier associated with this artist name. + + +International Standard Name Identifier. The ISNI number associated with this artist. + +Note, for artists with non -Roman alphabet names, an additional Non -Roman Alphabet Live Performing Artist +Name Record (NPR) can be used to identify the language and the script or alphabet in which the language is +written. + +3.6 Recording Detail + +Information regarding the recording of the submitted work is entered in the Recording Detail Record (REC). + +Record Prefix. This allows you to include recording (REC) detail. + +Release Date. Date the work was or will be first released for public consumption. This date can be a past, present, +or future date. + +Recording Duration. Duration of the recording of the work. + +--- Page 22 --- + +Common Works Registration User Manual +CWR19-0479 22 of 39 + +Album Title. The name of the album in which the work was included if the work was first released as part of an +album. + +Album Label. Name of the organization that produced and released the album in which the first release of the +work was included. + +Release Catalog Number. Number assigned by the organization releasing the album for internal purposes such +as sales and distribution tracking + +EAN. European Article Number of release (EAN-13). + +ISRC. International Standard Recording Code of the recording of the work on the release (according to ISO 3901). + +Recording Format. The code that identifies the content of the recording: “A” (audio), “V” (video). This field is +required for registrations to SESAC. + +Recording Technique. Identifies the recording procedure using “A” for Analogue and “D” for Digital. This field is +required for registrations to SESAC. + +Media Type. BIEM/CISAC code for media type. + +Recording Title. Title of the sound recording. + +Version Title. Title given to the version of the Sound Recording (for example: “remixed by”). + +Display Artist. The name of the artist of the recording. + +Performing Artist IPI Name Number. The unique identifier associated with this artist name. + + +International Standard Name Identifier. The ISNI number associated with this artist. + +Record Label. The name of the organization that produced the recording. + +ISRC Validity. If an ISRC is supplied, Indicates that the validity of the ISRC:“Y” is valid, “U” the link is invalid, “N” +the ISRC is invalid. + +Submitter Recording Identifier. The submitter’s unique identifier for this recording. + +Note, for recording titles using a non -Roman alphabet, an additional Non -Roman Alphabet Recording Title +Record (NRC) can be used to identify the language and the script or alphabet in which the language is written. + + + +--- Page 23 --- + +Common Works Registration User Manual +CWR19-0479 23 of 39 + +3.7 Work Origin + +The purpose of the Work Origin Record (ORN) is to describe the origin of the work. The origin may be a library, +or an audio -visual production or both. If the work originated in an AV production, additional information +regarding the usage of the work within the production can be helpful. The cue sheet is always the final authority +for usage data. + +A ‘Recommendation for Best Practice’ adopted by CISAC and the publishing community in 2008 outlines how +music in AV productions should be registered and interpreted: all background cues should be ‘rolled up’ and +registered under the Production title only. +There is no need to register individual cues, unless they subsequently appear on a soundtrack album or in another +form. + +Only one registration per writer/publisher/shares combination is necessary. Please also use the designated fields +in this record. For more information, please look up the PUB -CUE08-2679 on CISAC’s website or contact your +local society. + +Record Prefix. This allows you to describe the origin (ORN) of the work. + +Intended Purpose. Indicates the type of production from which this work originated, for example, commercial, +film, radio, television, library, multi-media, etc. + +CD Identifier. If this is a library work, enter the identifier associated with the CD upon which the work appears. + +Cut Number. If this is a library work, enter the track number on the CD Identifier where the work appears. This +field is required when CD Identifier is entered. + +Library. The library from which this work originated. + +Production Title. Title of the production from which this work originated. + +BLTVR. An indication of the primary use of the work within the AV production (background/logo/theme). The +definitive source for cue usage is the cue sheet. + +Production Number. The number generated by the production company to identify the work. + +Episode Title. Title of the episode from which this work originated + +Episode Number. Number assigned to the episode by the producer. + +Year of Production. The year in which the production of the film or episode was completed. + +The following two fields form the unique key for the audio-visual work within the AV Index: +AVI Society Code. The society code of the society whose audio visual work detail entry is referenced in the AV +Index +Audio-Visual Number. Unique number used by the owning Recipient to identify the AV works as refereed in the +AV Index. + + +--- Page 24 --- + +Common Works Registration User Manual +CWR19-0479 24 of 39 + +V-ISAN. Unique identifier for audio-visual production in which this work is first used. This number is assigned by +the producer. It is made up of the following: +ISAN. Root segment. +Episode. The episode or part number. +Check Digit 1. The check character for the root and episode segment. + +Version. The version segment. + +Check Digit 2. The check character for the version segment. + +The following two fields are used for the unique identifier EIDR: +EIDR. The root number. +Check Digit. The check character for the EIDR. + +Version Name. The title or description of the particular version to which the specific ISAN or EIDR relates. + +3.8 Audio-visual Productions + +The purpose of the Audio-visual Productions Record (FTV) is to describe audio-visual production into which the +submitted work has been licensed over and above any AV production described in the original work record (ORN). +Note that the cue sheet is always the final authority for usage data. The ORN would only be used for the Film or +TV Production in which the work originated, i.e. the production for which it was created. If a commercial work is +used in an AV production or an existing AV work is reused in another AV production, then the FTV record can be +used. + +Record Prefix. This allows you to describe the audio-visual production (FTV) of the work. + +Intended Purpose. Indicates the type of production from which this work originated, for example, commercial, +film, radio, television, library, multi-media, etc. + +Production Title. Name of the production from which this work originated. + +Production Number. The number generated by the production company to identify the work. + +Episode Title. Title of the episode from which this work originated + +Episode Number. Number assigned to the episode by the producer. + +Year of Production. The year in which the production of the film or episode was completed. + +The following two fields form the unique key for the audio-visual work within the AV Index: +AVI Society Code. The society code of the society whose audio visual work detail entry is referenced in the AV +Index +Audio-Visual Number. Unique number used by the owning Recipient to identify the AV works as refereed in the +AV Index. + + +--- Page 25 --- + +Common Works Registration User Manual +CWR19-0479 25 of 39 + +V-ISAN. Unique identifier for audio-visual production in which this work is first used. This number is assigned by +the producer. It is made up of the following: +ISAN. Root segment. +Episode. The episode or part number. +Check Digit 1. The check character for the root and episode segment. + +Version. The version segment. + +Check Digit 2. The check character for the version segment. + +The following two fields are used for the unique identifier EIDR: +EIDR. The root number. +Check Digit. The check character for the EIDR. + +Version Name. The title or description of the particular version to which the specific ISAN or EIDR relates. + +3.9 Instrumentation + +If the work being registered is a serious work, then it is necessary to describe the instrumentation of the work. If +the work is a jazz work, then instrumentation should also be provided. Instrumentation documentation can be +provided in the following three ways: +• standard instrumentation +• individual instrument records +• description + +If the work is for a standard set of instruments such as a wind quintet, use the Standard Instrumentation Type +field. If you know all of the individual instruments used, then complete an instrument detail record for each +instrument. If neither of these options is viable, you may complete the free form instrumentation description. + +It is possible to use a combination of standard instrumentation and individual instrument records, for example, +a wind ensemble for standard instrumentation, and a piano for an individual instrument. It is possible to have +more than one Instrumentation Summary Record (INS). This is to allow more than one standard instrumentation +e.g. string quartet and brass quartet. If any other field is present on the second or subsequent Instrumentation +Summary (INS), it will be ignored. + +3.9.1 Instrumentation Summary +The Instrumentation Summary Record (INS) provides information on standard and non-standard instrumentation +for serious works. + +Record Prefix. This allows you to provide instrumentation summary (INS) information. + +Number of Voices. This field indicates the number of lines or individual parts in the musical work. + +Standard Instrumentation Type. This field contains a value from the table of Standard Instrumentation e.g. brass +band, piano quartet. + +Instrumentation Description. This field contains a free form description of the instrumentation. + +--- Page 26 --- + +Common Works Registration User Manual +CWR19-0479 26 of 39 + +3.9.2 Instrumentation Detail +The Instrumentation Detail Record (IND) provides information on standard instruments or voices for serious +works. + +Record Prefix. This allows you to provide instrument detail (INS) information for the above summary record. + +Instrument Code. Select a code from the table of Instruments. + +Number of Players. Indicates the number of players for the above instrument. Note that if the number of players +is not a significant detail, enter zero. + + +3.10 Work ID Cross Reference + +The Work ID Cross Reference Record (XRF) contains identifiers issued by any or ganization including but not +limited to the intended recipient of the file. + +Record Prefix. This allows you to specify work ids (XRF). + +Organization Code. The number assigned to the organization (e.g. Society, publisher, DSP etc...) which generated +the Work ID. + +Identifier. The work identifier from the organization. + +Identifier Type. The type of identifier (“W” for Work, “R” for Recording, “P” for Product, “V“ for Video). + +Validity. Indicates whether the Identifier is valid or not: “Y” is valid, “U” the link is invalid, “N” the identifier is +invalid. +4. Retracting Work Registrations + +The Work Retraction Record (DRW) is to allow a submitter to communicate to a recipient (or multiple recipients) +that a recently submitted WRK transaction was invalid (i.e. filed in error) and that the publishers indicated on +the WRK transaction make no cla im to the work in question. Information to aid in identifying the work will be +asked for later in the transaction in a separate record type. + +Record Prefix. This allows you to retract a work registration (DRW). + +Work Title. List the title by which the work is best known. + +Language Code. Indicate the language of the work title. These values reside in the Language Code Table. + +Script Code. Indicate the script in which the work title is written. These values reside in the Script Code Table. + +Submitter Work Number. This is your unique numerical code for this work. + +ISWC. The International Standard Work Code assigned to this work. + +--- Page 27 --- + +Common Works Registration User Manual +CWR19-0479 27 of 39 + +Retraction Reason Code. The reason you are submitting a retraction, including the following reasons: +• Prior publishing agreement still in place +• The claimed writer is not a writer of this work +• The work was in dispute and the publisher relinquishes its claim +5. Acknowledgements + +When y ou send a group of work registrations to a Recipient, the Recipient will send first acknowledgement +records (ACK) for that group back to you. The second acknowledgement record will be sent as the work is created +in the Recipient’s data base. It is important that the Submitters process the acknowledgements, taking note of +errors and additional information returned. + +There are two types of ACK file: CWR_ACK1 and CWR_ACK2. The ACK transactions within the file type CWR_ACK1 +should deal only with technical compliance with the CWR format and edits of the WRK transaction as submitted. +The ACK transaction within the file type CWR_ACK2 should deal with the actual work status, the shares claimed, +any conflicting claims and the “readiness f or payment” of the corresponding work record in the Recipient’s +systems + +An ACK may include any error or warning messages associated with the original WRK transaction. In addition, an +ACK transaction within a CWR_ACK2 will include a WRK transaction represe nting the work record in the +Recipient’s system after processing the submitted WRK transaction. If a work is subject to conflicting claims from +parties other than the submitter, then the CWR_ACK2 ACK transaction may include an EXC transaction detailing +the conflicting claims. + +Some Recipients make all works payment ready as soon as possible. Others wait until the first performance of +the work. Still others make domestic works payable immediately and others when the work is performed. +Contact your local Recipient to determine what their policy is. + +You will receive at least one acknowledgement record for every work registration sent. The WRK transaction +included in the acknowledgement contains the equivalent of all of the records sent by the Submitter that have +relevance to the Recipient. This includes your work number in the Submitter Work Number field, which allows +you to easily match to the work in your database. The acknowledgement records will contain additional data +about the work that you will want to add to your database, such as: +• Recipient's Creation Number which is the work number assigned by the Recipient. It is understood that the +number should be in the same format as when used in distribution files (suggestion from EMI, CWR meeting +Berlin June 2010). +• IPI Name Numbers for interested parties +• Names for all interested parties +• ISWC for the work (if already on file) + +The following principles apply: +• It is necessary for Recipients to edit only the territories of interest +• It is necessary for Recipients to acknowledge only edited terr itories on first and subsequent +acknowledgements +• Registrations that do not contain a territory of interest will be acknowledged with status “NP” (no interest) + + +--- Page 28 --- + +Common Works Registration User Manual +CWR19-0479 28 of 39 + +Along with the status and any additional information being supplied back, the acknowledgement data contains +information to help you identify which work registration is being acknowledged. + +Record Prefix. This allows you to specify an acknowledgement (ACK). + +Creation Date. The date stamp from the file that you created for the work registrations + +Creation Time. The time stamp from the file that you created for the work registrations. + +Original Group ID. The group identification for the work registration as defined in the file you sent. + +Original Transaction Sequence Number. The transaction sequence number for the work registration as defined +in the file you sent. + +Original Transaction Type. The transaction type (usually WRK) of the work registration. + +Creation Title. The title of the musical work which is being acknowledged. + +Submitter Creation Number. The unique identifier which you have assigned to this work. + +Recipient Creation Number. The unique identifier assigned to this work by the Recipient. + +Recipient Temporary Creation Number. A unique identifier assigned to this work by the Recipient temporarily +until the work is ready for payment. + +Processing Date. The date that the Recipient processed the work registration. + +Transaction Status. A code indicating whether the work registration was accepted or rejected. + +5.1 Transaction Status + +One of the most important items of information in the Acknowledgement transaction is the status of your work +registration. Each status is listed below: + +5.1.1 CO: Transaction in Conflict +An acknowledgement with status code “CO” indicates that the Recipient has an existing work registration that +contains data that conflicts with the registration submitted by you. The acknowledgement will be followed by +the work registration as sent by you. This may be followed by an EXC transact ion that provides you with details +on the existing work that contains the conflicting claim. Note that in this event, a Recipient may contact you in +person rather than sending you an electronic transaction. It is your responsibility to resolve the conflict with the +other interested parties, and resubmit the work if appropriate. Please note that not all Recipients use this status. + + + +--- Page 29 --- + +Common Works Registration User Manual +CWR19-0479 29 of 39 + +5.1.2 RA: Registration Accepted - Passed Validations +An acknowledgement with status code “RA” indicates that the transaction has been received, and it has passed +all of the mandatory edits. There may be some warning messages to indicate that a field or record has been +rejected. There also may be a message indicating that this registration is a possible duplicate. At this stage the +Recipient has not yet determined whether the registration is ready for payment -- further processing is required. +This is an intermediate transaction that provides you with a quick acknowledgment if a further review of the +registration is necessary. If a w ork can readily be determined to be ready for payment or not , the +acknowledgement will contain the status code of “AS”,”AC”,”SR”, or “CR”. + +5.1.3 AS: Registration Accepted – Not Ready for Payment +An acknowledgement with status code “AS” indicates that the registration has been accepted and a work has +been created with the information given by the submitting Submitter, however the work is not yet ready for +payment. Writers may have to be identified or additional shares added to complete the work. Some Recipients +complete the work right away while others wait until the work becomes active. + +5.1.4 AC: Registration Accepted With Changes– Not Ready for Payment +An acknowledgement with status code “AC” indicates that the registration was accepted but changes were made +to the submitted claim data (other than the addition of IPI name Numbers or ISWC). The status code of “AC” +indicates to you that there is additional data that can be used to augment the data in yo ur works database. +Furthermore, the work is not yet ready for payment. + +5.1.5 SR: Registration Accepted –Ready for Payment +An acknowledgement with status code “SR” indicates that the registration has been accepted and a work has +been created with the information given by the submitting Submitter. This work is ready for payment. + +5.1.6 CR: Registration Accepted With Changes – Ready for Payment +An acknowledgement with status code “CR” indicates that the registration was accepted but changes were made +to the submitted claim data (other than the addition of IPI name Numbers or ISWC). The status code of “AC” +indicates to you that there is additional data that can be used to augment the data in your works database. This +work is ready for payment. + +5.1.7 RJ: Registration Rejected - Failed Validations +The edits in the CWR document will be applied to the data. If errors are found, an acknowledgement with status +code of “RJ” will be sent detailing the errors in a message record that precedes the record in error. The +registration will be rejected. You need to correct the errors and resubmit the registration. Note that processing +will not stop at the first error encountered, but will continue to the end of the data. The only exception to this is +if a severe error is found which makes further processing inadvisable e.g. a group header record is missing. A +message detailing the error will precede the record you sent that is in er ror. It is not necessary to resend the +entire file -- only the work registrations which were in error. + +5.1.8 NP: No Participation +An acknow ledgement with status code “NP” indicates that the Recipient that has no participation in the +controlled shares of the wo rk. As a result, the work may not have been subjected to the full range of edits. An +example would be a work with all BMI interested parties sent to ASCAP. ASCAP would send an acknowledgement +with status “NP”. + + +--- Page 30 --- + +Common Works Registration User Manual +CWR19-0479 30 of 39 + +5.1.9 DR: De-registered +An acknowledgement with status code “DR” indicates that the publisher’s claim has been relinquished. + +5.1.10 UN: Unknown Work in DRW +An acknowledgement with status code “UN” indicates that the Recipient has no record of the Submitter’s claim +to the work sent in the DRW transaction. + +5.1.11 LD: Unable to De-register +An acknowledgement with status code “LD” indicates that the Recipient was not able to retract the Submitter’s +claim to the work sent in the DRW transaction. + +5.1.12 NA: No Society Agreement Number +An acknowledgement with status code “NA” indicates that the work was rejected because there was no Society +Agreement Number supplied where an edit required one. + +5.1.13 WA: Wrong Society Agreement Number +An acknowledgement with status code “WA” indicates that the work was rejected because the Society +Agreement Number supplied was either invalid or does not relate to the interested parties submitted on the +work. + +5.2 Messages + +The message record details the error, warning, or information condition. It precedes the record containing the +error condition. All messages can be found in the CWR Lookup Table. + +The Message Type indicates the severity of the message – whether the registration has been rejected (T), the +entire file has been rejected (E), or whether this is a warning. + +You can use the Record Type, Message Level, and Validation Number to refer to the CWR Functional +Specifications manual for the full explanation of the error. For example WRK, T, 001 refers to the first Transaction +Level validation for the record WRK. The message text is a more user friendly version of the text in the Functional +Specifications. + +Record Prefix. This allows the Recipient to provide back any messages (MSG) that may result from the edits or +validations processes unique to a Recipient. + +Message Type. Indicates whether this information is a warning, error, or for information only. Values are “F” for +Field Rejected, “R” for Record Rejected, “T” for Transaction Rejected, “G” for Group Rejected and “E” for Entire +File Rejected. + +Original Record Sequence Number. The sequence number of the record within the work registration which +caused the message to be generated. + +Record Type. The record type within the original transaction that caused generation of this message. + + +--- Page 31 --- + +Common Works Registration User Manual +CWR19-0479 31 of 39 + +Message Level. The level of editing that was responsible for the generation of this message. Values are “F” for +Field, “R” for Record, “T” for Transaction, “G” for Group and “E” for Entire File. + +Validation Number. The number of the failed edit. The combination of record type, message level, and validation +number uniquely identifies the error. + +Message Text. A description of the error or warning. + +5.3 Existing Work in Conflict with Submitted Work + +The Existing Work in Conflict with Submitted WRK Record (EXC) will be sent from a Recipient to a Submitter to +provide information on the details of the work that is in conflict with the details of the WRK transaction sent by +the Submitter. + +If a work registration conflicts with an existing work, then an acknowledgement is sent with a status of “CO”. The +work registration is returned using the WRK transaction. Finally, the details of the existing work are included in +the EXC transaction. The EXC transaction has the same f ormat as the WRK. Note that if the existing work was +not sent using CWR, it may be missing some data that is required under CWR. +6. ISWC Confirmation and Allocation + +6.1 Request for Confirmation/Allocation of ISWC + +The Request for Confirmation/Allocation of ISWC Record (ISR) may be sent by a Submitter to a society requesting +that the society pass the transaction on to the ISWC Allocation Service, which will then either issue a new ISWC +for the work or confirm the existing Preferred ISWC for that work. Information to aid in confirming the identity +of the work will be asked for later in the transaction in a separate record type. + +Record Prefix. This allows you to specify a request for confirmation/allocation of ISWC (ISW) work or an existing +work in conflict (EXC). + +Work Title. List the title by which the work is best known. + +Language Code. Indicate the language of the work title. These values reside in the Language Code Table. + +Submitter Work Number. This is your unique numerical code for this work. + +ISWC. The International Standard Work Code assigned to this work. + +ISWC Preferred Indicator. Indicates whether the ISWC is one of the numbers marked as preferred by the ISWC +Resolution Service. + +6.2 Confirmation of ISWC + +The Confirmation of ISWC Record (ISA wri) may be sent in response to a request from a society to the ISWC +Allocation Service. The record format is the same as that used for the request record (ISW). + +--- Page 32 --- + +Common Works Registration User Manual +CWR19-0479 32 of 39 + +6.3 Writer for ISWC + +The Writer for ISW/ISA Record (WRI) contains the writer details for the works submitted in a request for +confirmation or allocation of an ISWC. + +Record Prefix. This allows you to indicate writers (WRI) for ISRC confirmation/allocation. + +Submitter Work Number. This is your unique numerical code for this work. + +Writer IPI Name Number. The unique identifier associated with this writer name. + +Writer Last Name. The last name of the writer. + +Writer First Name. The first name of the writer. + +Writer Role Code. This code describes the role of the writer with respect to this work e.g. composer, author, +arranger. +7. License Reporting Transaction + +The License Reporting Record (LIC) allows Submitters to report to Recipients details of licensed usages of a work. +This includes new or existing recordings, live performers, other work identifiers and synchronizations in audio +visual productions. LIC transactions will only be reported in a separate CWR_LIC file. No ACK file or return +transaction is required for CWR_LIC files. The license reporting header identifies the work to which the licensing +and usage information in the LIC transaction relates. Other information, like recordings, artist, etc. will be asked +for later in the transaction in separate record types. + +Record Prefix. This allows you to indicate license reporting or usage information (LIC) for a work. + +Work Title. List the title by which the work is best known. + +Submitter Work Number. This is your unique numerical code for this work. + +ISWC. The International Standard Work Code assigned to this work. + + +--- Page 33 --- + +Common Works Registration User Manual +CWR19-0479 33 of 39 + +8. Workflow Diagrams + +The Submitter work flow below shows how new work registrations and revisions are delivered to the Recipient +and how the Submitter should respond based on the acknowledgement status codes that they are returned. + + +--- Page 34 --- + +Common Works Registration User Manual +CWR19-0479 34 of 39 + +The Recipient work flow below shows how a Recipient should process CWR new work registrations +and revisions and how they should respond back to the submitting Submitter. + + + +--- Page 35 --- + +Common Works Registration User Manual +CWR19-0479 35 of 39 + +9. Implementing CWR + +At this part of the user manual you already know the importance and the complexity of the CWR format. After +developing your system according to the technical specifications described in the other technical manual, let's +review the implementation process of the CWR. + +9.1 Testing Procedures – Submitter + +At this point your system is ready to start using the CWR and all the information is according to the latest +documents of the CWR web site (www.cisac.org).The next steps are follows: +• Contact your local Recipient to verify which version they are using. A Submitter can test with many +Recipients at the same time but we recommend testing with one Recipient at the time. +• The Submitter should create a new email that will be used for the transference of all information related +to CWR. The Recipient you are dealing with must do the same. The testing phase is the time when you +are testing something new and it may take some time, so we recommend you to establish good +communication with the responsible contact for the CWR at the Recipient. +• If the Submitter is sending a file to a Recipient in another country, you must copy all the emails to your +local office. It is very important to link all the participants in this process. +• You must inform the Recipient if the works you are going to register are international or domestic. Some +Submitters are not able to register domestic works or international works and we recommend you to +put these works in separate files. The format of the information could be different so it is a good +precaution. +• Before you send the file to the Recipient you must contact t hem asking about other information you +might need to put in the CWR file. +• After all the initial correspondence with the Recipient, you should send them the first test file. This first +CWR file is very important to check the integrity of your file. We recommend you to use 100 works in +this first file. In this first file the structure and the layout of your file will be checked by the Recipient. +• The result of this first test will help the Submitter to know if the layout of the file is 100% correct. If it is +not correct, the Submitter should consult with the Recipient regarding the problem how it can be solved. +As the result of the first test the Recipient must send an ACK file to the Submitter and this ACK file must +be tested by the Submitter in all the different aspects (integrity, layout, etc). +• We do recommend you to send a second, larger, CWR test file with different works (around 200 works). +This second test is not mandatory but is it to ensure that the problems of the 1º file were solved before +moving into the live phase. +• The Recipient will send you another ACK file for this second CWR file. If this file was correctly processed +in your data base, you should inform the Recipient that you are ready to move to the production phase. +• A Submitter can test CWR with many Recipients. You don't need to go live with all of them at the same +time. +• Because of some specific edits, it may take some time to complete the implementation of the CWR with +some Recipients but it is very important for the Submitters to follow these recommendations. + + + +--- Page 36 --- + +Common Works Registration User Manual +CWR19-0479 36 of 39 + +9.2 Testing Procedures – Recipients + +At this point your system is ready to start using the CWR and all the information is according to the latest +documents of the CWR web site (www.cisac.org). Let's review the next steps: +• The Recipient must be prepared to receive the inquiry from the Submitter regarding the CWR format. If +the Recipient has already implemented the CWR, the answer to the Submitter must be positive informing +the Submitter of the version of the CWR the Recipient is using (2.0 or 2.1). +• The Recipient must create a new email that will be used for the transference of all information related +to CWR. The Submitter you are dealing with must do the same. The testing period is the time when you +are testing something new and it may take some time, so we rec ommend you to establish good +communication with the responsible contact for the CWR at the Submitter that is sending you the files. +• If you are receiving a file from a Submitter based in another country, you must confirm that the +Submitter’s local office is copied on the correspondence. It is very important that the local Submitter is +included in all emails. +• After the first contact and before the first test file, the Recipient must ask the Submitter about the first +file (number of works, domestic or international repertoire, etc). We do not recommend files with more +than 100 works in the first test file. The Recipient must inform the Submitter about any Recipient specific +information. +• The Submitter will send the first file to be uploaded into your system. Some errors might have occurred +during this process. These errors could be caused by different reasons, including problems in the layout +of the file or problems with the information in the file. The Recipient should send an ACK file back to the +Submitter reporting all problems detected during the upload process. +• At this time the Recipient must help the Submitter to solve the problems in the layout and the structure +of the file. The Recipient must ask for more test files to ensure the problems were solved,. +• We do recommend that the second CWR test file be sent to the Recipient. This file should contain more +works that are different than the works included in the first test fil e. This second test is not mandatory +but is it good to ensure that the problems of the 1º file were solved. +• After the second file, the Recipient must send the ACK files to the Submitter with the information from +those works. The Recipient must also send other information they might consider relevant for the +implementation of the CWR. +• If the Recipient does not feel comfortable moving into the live phase, they can ask the Submitter for +more test files. +• After all of the testing has been completed the Recipient and the Submitter must agree to move on to +the live phase. + +The interchange of CWR files between Submitter and Recipient can happen in different ways: email, CD, FTP, etc. +For safety reasons we do recommend you to use e-mail during this process. + +9.3 Production + +After completing the testing process, both the Recipient and Submitter are ready to move to the live phase. + +The process that will be adopted by Submitters and Recipients will be almost the same from the testing phase. +The Submitter will create the files and sent it to the Recipients. +The Recipient will extract the information and upload this information to their data base. The information will +be processed in the Recipient data base and after that the Recipient will create the ACK file. + + +--- Page 37 --- + +Common Works Registration User Manual +CWR19-0479 37 of 39 + +The Recipient will send the correspondent ACK back file to the Submitter and the circle will be completed. + +The Recipients have different methods to proceed with the CWR files. Some of the Recipients send back two ACK +files in this process and some send only one file back to the Submitters. These methods must be considered +during the implementation process and the Submitter must be aware of this possibility. The final result is the +same and we do recommend you to stay in touch with the Submitter or the Recipient during the whole process +with the intention of avoiding problems during the implementation process. +10. Examples of the file structure +Examples can be found in supplemental documentation. + + + +--- Page 38 --- + +Common Works Registration User Manual +CWR19-0479 38 of 39 + +11. Glossary + +We know that CWR involves a lot very specific terms and this glossary is to help the user to better understand +some important principles. + +CHAIN / CHAIN OF TITLE: The chain of title is a line where rights are passed along, for example from a writer to +an original publisher to a sub- publisher. In a CWR file a chain shows how rights flow to the entitled parties, every +song will have at least one chain. + +CO-PUBLISHING: An agreement where there may be one writer and two co -existing publishers. For CWR +purposes, this means that a song will have two chains. + +DRIP FEED: This is a process where a Recipient sends a number of ACK files (ACK files defined above) back to the +Submitter, as the works from the original file are processed over a period of time. + +FTP SITE: An FTP (file transfer protocol) site is like a postbox where Submitters can securely send f iles to a +Recipient. Usually a numeric address and a password or other security is required. + +NON-PARTICIPATION: This is when a song is not intended for a particular Recipient, when the song is i ncluded +in a file to be sent to many Recipients. + +IPI NAME NUMBER: The unique identifier associated with the interested party name. The IP Name Number is a +unique identifier allocated automatically by the IPI System to each name. It consists of 11 digits 99999999999. +The last two digits are check -digits (modulus 101). An IP may have more than one IP name. New IP names will +get new IP Name Numbers. A name of an IP name number may only be changed in case of spelling corrections. + +IPI BASE NUMBER: This number is the unique identifier associated with the interested party. The IP Base Number +is a unique identifier allocated automatically by the IPI System to each interested party (IP), being either a natural +person or legal entity. The number consists of 13 characters: letter i (I), hyphen ( -), nine digits, hyphen ( -), one +check-digit. I-999999999-9. (weighted modulus 10, I weight = 2, adapted from ISO 7064). You can find more +information in the CISAC web site. + +TERRITORY INFORMATION SYSTEM (TIS): The TIS system contains four digit numeric codes for each country of +the world. It also contains codes for groupings of countries e.g. Europe, North America, as well as a code for +world. The TIS system is based on the ISO territory codes but it contains group names that the ISO does not, and +excludes some sub-territories that the ISO includes. + +VALIDATION: To send complex data to each other, the data must comply with rules. The rules can be simple, or +complex as required in some cases. Validation is the automatic process where a computer checks that the data +meets the required rules. + + + + + + +--- Page 39 --- + +Common Works Registration User Manual +CWR19-0479 39 of 39 + +Category of the document : User Manual +Status of the document : Draft +Distribution List : CISAC Recipients and their members + +Table of Revisions and main modifications +Revision # Date Main modifications +0 09/2017 • Updated to correspond to CWR 3.0 technical specification + +Summary +This document is written for music Submitters and Recipients administering performing, mechanical and/or +synchronization rights. It describes how to use version 3.0 of the Common Works Registration format. CWR v3.0 +was adopted as a CISAC standard by the Information Services Committee (ISC) at its meeting on April 4th, 2019 in +Nice. + +Send comments/questions regarding this manual to cwr@cisac.org or to any member of the CWR Management +Committee. \ No newline at end of file diff --git a/docs/source/_downloads/CWR19-1070R1_Functional_specifications_CWR_version_2-2_Rev2_2022-02-03_EN.pdf b/docs/source/_downloads/CWR19-1070R1_Functional_specifications_CWR_version_2-2_Rev2_2022-02-03_EN.pdf new file mode 100644 index 0000000..4dc4d8f Binary files /dev/null and b/docs/source/_downloads/CWR19-1070R1_Functional_specifications_CWR_version_2-2_Rev2_2022-02-03_EN.pdf differ diff --git a/docs/source/_downloads/CWR19-1070R1_Functional_specifications_CWR_version_2-2_Rev2_2022-02-03_EN.txt b/docs/source/_downloads/CWR19-1070R1_Functional_specifications_CWR_version_2-2_Rev2_2022-02-03_EN.txt new file mode 100644 index 0000000..bb989a2 --- /dev/null +++ b/docs/source/_downloads/CWR19-1070R1_Functional_specifications_CWR_version_2-2_Rev2_2022-02-03_EN.txt @@ -0,0 +1,4277 @@ + + Page 1 of 81 +CWR19-1070 +Information Services Committee +Conference Call, 05/11/2019 +Source Language: English +Published on: 05/11/2019 + + + + + + + + + + + +Functional specifications: +Common Works Registration +Version 2.2 – Revision 2 + +Society Publisher Forum + + +Status: ADOPTED by the Information Services Committee (Conference call, 05/11/2019) +(ISC17-1284) + +Date: 05/11/2019 + +Access rights: External to CISAC + + + +--- Page 2 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 2 of 81 + + +Latest Revisions and updates +(Previous revisions available at the end of the document) + +Number of revision Date Main modifications +2.2 05/2015 + + + + + + + + + + + + + + +14/04/2016 +➢ HDR: new fields for, version, revision, software package and +package release number +➢ SPU: IPI Name Numbers made mandatory for a submitter’s own +IPI Name Numbers +➢ PWR removed edit to allow PWR to follow OWR +➢ PWR to SPU Sequence Number link +➢ OPT New ‘non-controlled publisher collection’ record (optional) +➢ OWT new ‘other writer collection’ record (optional) +➢ REC New optional fields for Sound Recording Title, Sound +Recording version title, Record Label, Display Artist +➢ ORN removed previously invalid ISAN field and note relating to +its use +➢ ORN New optional Field for ISAN and EIDR +➢ XRF new Optional Record +➢ Society specific edits agreed at the New York meeting added +➢ Information Services Committee (Lisbon, 14/04/2016) approves +Version 2.2 +2.2R1 25.04.2017 ➢ Correction of missing edit PWRF006 and renumbering the edits +below. +2.2R2 16/09/2019 ➢ Update to transmission header record to account for IPI Name +Numbers (IPNN) greater than 9 digits. +➢ OPU validation updates. +➢ GRH record version number update. +➢ MSG record example removal. +➢ Addition of missing XREF record in Transaction Format table and +file skeletons. +➢ Update to XRF field description for Organisation Code. +➢ Approved by the ISC conference call on 05/11/2019 +2.2R2 16/09/2021 ➢ Update to exceptional clause +➢ Update to ARI +➢ Update to publisher chain + +Summary: This document contains the technical description of the Common Works Registration version 2.2 +Rev 2. This version of CWR contains minor changes (as outlined above) from the Common Works Registration +version 2.1 Rev 7 that has been approved by the Information Services Committee (Lisbon, 14/04/2016). The +format of transactions and records are included. + +Send comments/questions regarding this manual to CWR@cisac.org or any member of the CWR +Management Committee. + +--- Page 3 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 3 of 81 + + +TABLE OF CONTENTS +1 Introduction ................................ ................................ ................................ ....................... 5 +2 EDI Terminology ................................ ................................ ................................ ................. 6 +2.1 Properties of EDI Components ................................ ................................ ................................ . 7 +3 File Structure ................................ ................................ ................................ .................... 10 +3.1 File Naming Convention ................................ ................................ ................................ ......... 10 +3.2 Control Records ................................ ................................ ................................ ..................... 11 +3.3 Notification of Data Transmission & Acknowledgement of Notification/Validation Status ....... 11 +3.4 File Level Validation ................................ ................................ ................................ .............. 13 +3.5 HDR: Transmission Header................................ ................................ ................................ ..... 14 +3.6 GRH: Group Header ................................ ................................ ................................ ............... 16 +3.7 GRT: Group Trailer ................................ ................................ ................................ ................. 17 +3.8 TRL: Transmission Trailer ................................ ................................ ................................ ....... 17 +4 Transaction Header Records ................................ ................................ ............................. 18 +4.1 AGR: Agreement Supporting Work Registration ................................ ................................ ..... 18 +4.2 NWR: New Work Registration ................................ ................................ ................................ 22 +4.3 REV: Revised Registration ................................ ................................ ................................ ...... 22 +4.4 ISW: Notification of ISWC assign to a work ................................ ................................ ............. 22 +4.5 EXC: Existing work which is in Conflict with a Work Registration ................................ ............. 22 +4.1 ACK: Acknowledgement of Transaction ................................ ................................ .................. 30 +5 Detail Records ................................ ................................ ................................ .................. 32 +5.1 TER: Territory in Agreement ................................ ................................ ................................ .. 33 +5.2 IPA: Interested Party of Agreement ................................ ................................ ....................... 34 +5.3 NPA: Non-Roman Alphabet Agreement Party Name ................................ ............................... 36 +5.4 SPU: Publisher Controlled By Submitter ................................ ................................ ................. 36 +5.5 OPU: Other Publisher ................................ ................................ ................................ ............ 36 +5.6 NPN: Non-Roman Alphabet Publisher Name ................................ ................................ .......... 43 +5.7 SPT: Publisher Territory of Control ................................ ................................ ......................... 44 +5.8 OPT: Publisher Non-Controlled Collection ................................ ................................ .............. 44 +5.9 SWR: Writer Controlled By Submitter ................................ ................................ .................... 46 +5.10 OWR: Other Writer ................................ ................................ ................................ ................ 46 +5.11 NWN: Non-Roman Alphabet Writer Name ................................ ................................ ............. 49 +5.12 SWT: Writer Territory of Control ................................ ................................ ............................ 50 +5.13 OWT: Other Writer Collection ................................ ................................ ................................ 50 +5.14 PWR: Publisher For Writer ................................ ................................ ................................ ..... 52 + +--- Page 4 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 4 of 81 + + +5.15 ALT: Alternate Title................................ ................................ ................................ ................ 54 +5.16 NAT: Non-Roman Alphabet Title ................................ ................................ ............................ 54 +5.17 EWT: Entire Work Title for Excerpts ................................ ................................ ....................... 55 +5.18 VER: Original Work Title for Versions ................................ ................................ ..................... 56 +5.19 PER: Performing Artist ................................ ................................ ................................ ........... 58 +5.20 NPR: Performance Data in non-roman alphabet ................................ ................................ ..... 59 +5.21 REC: Recording Detail ................................ ................................ ................................ ............ 60 +5.22 ORN: Work Origin ................................ ................................ ................................ .................. 62 +5.23 INS: Instrumentation Summary ................................ ................................ .............................. 64 +5.24 IND: Instrumentation Detail ................................ ................................ ................................ ... 64 +5.25 COM: Component ................................ ................................ ................................ .................. 65 +5.26 MSG: Message ................................ ................................ ................................ ...................... 66 +5.27 NET: Non-Roman Alphabet Entire Work Title for Excerpts ................................ ...................... 67 +5.28 NCT: Non-Roman Alphabet Title for Components ................................ ................................ ... 67 +5.29 NVT: Non-Roman Alphabet Original Title for Version................................ .............................. 67 +5.30 NOW: Non-Roman Alphabet Other Writer Name ................................ ................................ ... 68 +5.31 ARI: Additional Related Information ................................ ................................ ...................... 69 +5.32 XRF: Work ID Cross Reference ................................ ................................ ................................ 69 +6 CWR Data Structure ................................ ................................ ................................ .......... 70 +6.1 Definition of CWR using BNF ................................ ................................ ................................ .. 70 +6.2 File skeleton sent from publisher to societies ................................ ................................ ......... 72 +6.3 File skeleton sent from society to publisher ................................ ................................ ........... 73 +6.4 File skeleton containing Non-Roman Alphabet Records ................................ .......................... 74 +7 Society-Specific Edits................................ ................................ ................................ ......... 75 +7.1 ABRAMUS and UBC ................................ ................................ ................................ ............... 76 +7.2 ASCAP ................................ ................................ ................................ ................................ ... 76 +7.3 BMI ................................ ................................ ................................ ................................ ....... 76 +7.4 GEMA ................................ ................................ ................................ ................................ ... 76 +7.5 Harry Fox ................................ ................................ ................................ .............................. 77 +7.6 ICE Societies ................................ ................................ ................................ .......................... 77 +7.7 MusicMark ................................ ................................ ................................ ............................ 78 +7.8 SACEM ................................ ................................ ................................ ................................ .. 78 +7.9 SESAC................................ ................................ ................................ ................................ .... 79 +7.10 SGAE ................................ ................................ ................................ ................................ ..... 79 +7.11 SIAE ................................ ................................ ................................ ................................ ...... 80 +8 Previous Revisions ................................ ................................ ................................ ............ 81 + +--- Page 5 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 5 of 81 + + +1 Introduction +CWR v2 was adopted as a CISAC standard by the CIS Steering Committee in its meeting February 27, 28 2001 +in Madrid. + +The purpose of the Common Works Registration (CWR) format is to provide publishers and societies with a +standard format for the registration of works. This provides many benefits for both publishers and societies. +Publishers will be able to create one registration file and send it to participating societies around the world. +Each society that receives that file will follow a similar process, and provide acknowledgement in a common +format back to the publisher. Similarly, as more and more publishers adopt the CWR format, soci eties will +receive the majority of the work registrations in the one standard format. This will result in significant savings +in time and resources. + +Another benefit of the CWR is that it is flexible enough to provide for all of the data elements that righ ts +organizations require in a registration for a work. Some of these data elements may not be available at +present, but they can be added to the database of publishers and societies alike so that in the future this +data can be captured. For some data elements, the CWR provides a means of capturing those data elements. +For example, the societies will provide IPI numbers for participants and ISWCs for works in their +acknowledgement records whenever possible. The publishers can then populate their databases wi th this +additional data. + +The electronic submission of unique identifiers such as the ISWC and IPI will provide a much more efficient +way for the societies and publishers to accurately and quickly identify works and interested parties. + +The CWR employs dat a standards that have been developed for the Common Information System (CIS) +project of CISAC. Using existing standards for codes will eliminate confusion. Version 1.1 of Standards for +Electronic Data Interchange and Communications developed in CIS is used as much as possible (based on the +document IS/IM/47). This provides a solid foundation for the CWR. + +Version 2 of the CWR format includes an option to include agreement transactions. Agreement transactions +can be used to refer to an existing agreement or to inform a society of a specific agreement. This transaction +is not meant as a vehicle for the notification of agreements - it is meant to provide agreement information +for the works that are being registered. + +Version 2 of the CWR format inc ludes records to allow titles and names in Chinese, Japanese, Korean, and +other non -Roman alphabets. Separate records have been provided so that societies and publishers that +cannot deal with non-Roman alphabets may simply ignore the data. + +Version 2.1 of the CWR format includes additional fields for the registration of cues, and a new record, ARI. +For a less technical description of the CWR format as well as examples, please see the CWR User Manual. + +Related Documents are: + +• CRF0028 – CWRv2.1 User Manual +• CRF020 – CWR Validation and Lookup Tables +• IM0047 – EDI Standards +• CWR06-1972– CWR Sender ID and Codes +• CWR08-2493– CWR Error Messages + +The latest version of all the documents can be found on the CISAC website: www.cisac.org. + +--- Page 6 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 6 of 81 + + +Standards applicable to all CIS transactions +This section has been extracted from the CIS Guidelines for Electronic Data Interchange (IS/IM/47). The +guidelines were developed by the International Modelling Group, and approved by the CISAC community for +general use by all societies for all types of data transmission. + +2 EDI Terminology +Data Element: the basic unit of information in the EDI standard. Data elements (also referred to as Fields) +contain information that represents a singular fact, for example, song title, date of birth, or production year. +Data elements can be codes, numeric values, or literal descriptions. Data element definitions must include a +description, specifications for data type, size, and if appropriate, a list of code values and definitions of each +value. + +Detail Record: a combination of functionally related data elements. An identifier or record type is placed at +the beginning of each detail record identifying its purpose. Detail record definitions must include a +description, the list of data elements that are included in the detail record along with an indication of whether +each data element is mandatory, optional, or conditional, and the validation rules to insure all data elements +are correct. + +Transaction Header: a combination of functionally related data elements that is also used to define the start +of a business transaction. An identifier or transaction code is placed at the beginning of each transaction +header identifying its purpose. Transaction header definitions must include a description, the list of data +elements that are included in the transaction header record along with an indication of whether each data +element is mandatory, optional, or conditional, and the validation rules to insure all data elements are +correct. + +Transaction: a transaction header that may or may not be followed by any number of supporting detail +records. A transaction contains all the data required to define a specific business transaction e.g. transactions +may represent the equivalent of + +• Work Registrations +• Agreements +• Interested Party Information + +Transaction definitions must include a list of what detail records can be included in the transaction along with +an indication of whether the detail record is mandatory, optional, or conditional. For each o f those detail +records, the definition must also indicate the repeat frequency for the record (how many times can this +record occur within this transaction). + +Group: composed of one or more transactions of the same type. Each group begins with a header record that +identifies the type of transaction contained in the group, and ends with a trailer that includes control totals +summarizing the content of the file. Note that a group can contain up to 10,000,000 transactions. +File: composed of one or more groups. Files are the unit that ends up getting transmitted between CISAC EDI +participants. Each file begins with a header record that identifies the file’s origination and ends with a trailer +that includes control totals summarizing the content of the file. + +Control Records: provide information about the content of a group or file. These records insure that only +authorized users of this facility are participating and that the integrity of each transaction is maintained as +the file travels through various telecommunication lines. + +--- Page 7 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 7 of 81 + + +2.1 Properties of EDI Components +Files transmitted within this standard must exhibit the following characteristics: + +• All data will be ASCII encoded. The valid ASCII characters are as defined in CIS character set SR06-1311, +which is available on the CISAC Website www.cisac.org. +Note: The CWR MC has allowed for other character sets to be used (to permit the registration of certain +works) if a character set is noted in the HDR record. +• Records are variable length and carriage return / line feed (CR/LF) delimited +• Fields within the records are fixed length and are not delimited +• All alphabetic characters will be presented in upper case + +The standard for transmission will be the File Transfer Protocol (FTP). Each participant will have to provide +the address for its public FTP site and each tr ansmission will be a push (i.e. the sender will deliver its file to +the recipients public FTP site). + +Data Element Properties +The following information will be defined for each data element within the CISAC EDI standard: +• Field: Indicates the name of the data element +• Start: The position in the record where this field starts (note the first position of the record is “1”). +• Size: The number of characters that this field will occupy. +• Format: The type of data included in this field. Data present in a field that i s inconsistent with the rules +defined below will cause that record (and potentially the entire transaction) to be rejected. The legend +of type abbreviations is... +Code Description Default Size Rules +A Alpha or +Alphanumeric None +Any string containing valid ASCII text. Note that nulls are not +acceptable and all alphabetic characters must be in upper case. If +there is no data to be entered in an alpha field, blanks must be +entered. +B Boolean 1 Field must be equal to es or o +F Flag 1 +Field must be equal to es, o, or nknown. Note that the +difference between Boolean and Flag is the allowance of an +unknown condition for all fields declared as Flag. +D Date 8 Dates are all formatted as YYYYMMDD. If there is no data to be +entered in a date field, zeroes must be entered. +N Numeric None +Numeric fields are to be right justified and zero filled. If there is an +implied decimal point, it will be defined in the record layout. If there +is no data to be entered in a numeric field, zeroes must be entered. +T Time or +Duration 6 +Time/Duration fields are all formatted as HHMMSS. Time of day is to +be expressed in 24 hour format, otherwise known as military time. If +there is no data to be entered in a time or duration field, zeroes must +be entered. +L List or Table +Lookup None +The valid entries for these fields come from a list in the field +description or a table. Note that the values for these tables are to be +found in the Lookup Table document. + +--- Page 8 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 8 of 81 + + +• Req: Indicates whether or not an entry must be present in this field. Values in the REQ field will be... + M: Mandatory, meaning this field must be filled out. If it is not filled out, this record will be +rejected and, depending on the record type, the entire tr ansaction may be rejected. Note that +not all record types are mandatory; however, there are mandatory fields within optional records. + C: Conditional, meaning this field may be Mandatory depending on other conditions that exist in +either the current record or the transaction. If the condition results in a mandatory field and this +field is not present, this record will be rejected and, depending on the record type, the entire +transaction may be rejected. + O: Optional, meaning this field may or may not be entered. +• Field Description: Provides a basic description of the field to be entered. Also included will be the +individual table where valid entries reside for fields with a format type equal to “L”. + +Detail Record Properties +The following information will be defined for each detail record within the CISAC EDI standard: +• Record Description: Provides a detailed description of the purpose of this record. +• Record Format: Lists the data elements from which this detail record is composed. Each data element +definition within the Record Format section will include all Data Element Properties as listed above. +• Record Level Validation: The validation criteria that will be applied by the recipient to this detail record +when received. Record level validation insures validity of this detail record. +• Field Level Validation: The validation criteria that will be applied by the recipient to this detail record +when received. Field level validation insures the validity of each data element contained in the detail +record. + +Transaction Header Properties +The following information will be defined for each transaction header within the CISAC EDI standard: +• Transaction Description: Provides a detailed description of the purpose of this transaction. +• Transaction Format: Lists the transaction header and the various detail records (if any) from which this +transaction is composed. For each detail record, three additional items are defined… +➢ Req: indicates whether the detail record/transaction header is Required (R), Optional (O), or +Conditional (C). +➢ Max Use: Indicates the number of times this detail record can appear within a transaction. Values +are either 1 meaning the record can only occur once, or M meaning the record can appear as many +times as is required. +➢ Comment: Used to communicate any additi onal information which may be helpful to those +implementing the transaction. +• Record Description: Provides a detailed description of the purpose of this transaction header. +• Record Format: Lists the data elements from which this detail record is composed. Ea ch data element +definition within the Record Format section will include all Data Element Properties as listed above. +• Transaction Level Validation: The validation criteria that will be applied by the recipient to this detail +record when received. Transaction level validation insures validity of this detail record as it relates to the +overall transaction. + +--- Page 9 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 9 of 81 + + +• Field Level Validation: The validation criteria that will be applied by the recipient to this detail record +when received. Field level validation insures t he validity of each data element contained in the detail +record. + +Validation +Subsequent to each detail record or transaction header description, a set of validation criteria will be +provided. These criteria are listed at different potential levels depending on the record being edited. The +levels of validation are File, Group, Transaction, Record, or Field. As a result of validation, the same levels of +detail may be rejected from the data. Rejections are indicated at the end of the validation criteri a with one +of the following codes… +• ER: Entire File is rejected +• GR: Entire Group is rejected +• TR: Entire Transaction is rejected +• RR: Entire Record is rejected +• FR: Field is rejected and a default value is specified for the field +Record Prefixes +Each Transaction Header and Detail Record contains a prefix that identifies both the record and the +transaction that is being delivered. The attached table describes the layout of the prefix area… +Field Start Size Fmt Req Field Description +Record Type 1 3 L M The three character transaction type or detail record type. +These values reside in the Record Type Table. +Transaction +Sequence # +4 8 N M If this is the first transaction within a group, the Transaction +Sequence # must be equal to 00000000. Otherwise, for +transaction headers, the Transaction Sequence # must be equal +to the previous transaction header’s Transaction Sequence # +incremented by 1. For detail records, the Transaction Sequence +# must be equal to the Transaction Sequence # of the previous +transaction header. +Record Sequence +# +12 8 N M For transaction headers, always set to 00000000. For detail +records, set this field to the Record Sequence # of the previous +record written to the file incremented by 1. + +Field Level Validation +1. Record Type must be either a valid transaction type or a valid detail record type. (ER) +2. If this is the first transaction header in the group, Transaction Sequence # must be equal to 0. (ER) +3. If this is a transaction header that is not the first transaction header in t he group, the Transaction +Sequence # must be equal to the previous transaction’s Transaction Sequence # incremented by 1. (TR) +[1] +4. If this is a detail record, the Transaction Sequence # must be equal to the previous record’s Transaction +Sequence #. (TR) [1] +5. If this is a transaction header record, the Record Sequence # must be equal to zero. (ER) +6. If this is a detail record, the Record Sequence # must be equal to the previous record’s Record Sequence +# incremented by 1. (ER) + +--- Page 10 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 10 of 81 + + +7. If the Transaction Sequence # on subsequent transactions are not in sequential order within a group, the +entire file will be rejected. (ER) +8. If any detail records belonging to a transaction header do not carry the same Transaction Sequence # as +the preceding transaction heade r, the subordinate records are out of sequence. In this case, the entire +file will be rejected. (ER) +9. Record length must match the record length specified within the specification. (ER) +[1] Note: When the NWR transaction follows an ACK transaction it is regarded as a continuation of the same +transaction (since the acknowledgement is for the work described in the NWR). Therefore the NWR has the +same transaction number as the ACK, and the record sequence numbers continue to be incremented by one. +Similarly when the EXC transaction follows an NWR, it will contain the same transaction number as the NWR +and the record sequence numbers continue to be incremented by one. + +3 File Structure +Note that the File Naming Convention has been modified by the CWR Management Committee to better suit +the needs of CWR. It no longer conforms to the convention specified in the EDI Standards. +3.1 File Naming Convention +As of August 2006 the file convention of CWyynnnnsss_rrr.Vxx was adopted for use in files sent by publishers +to societies and vice versa where +CW – identifies a CWR file + yy – identifies the year +nnnn – is the sequence # assigned by the publisher +sss – is the sender (2 or 3 char code for publisher, or the 3 digit code for society) +rrr – is the receiver (2 or 3 char code for publisher, or the 3 digit code for society) +Vxx – is the version +This replaces the previous file naming convention, which was exactly the same except that the file sequence +number only had 2 digits instead of 4. +If the file is zipped, it will be named CWyynnnnsss_rrr.zip. The unzipped file it contains will be named as +above with the version number. +Note that if the same file is being sent to several societies, use ‘000’ as the society code. +EXAMPLE: +CW060001EMI_044.zip would be the name of the first file sent by EMI to MCPS -PRS in 2006. This file is +zipped. When it is unzipped, the file name would be CW060001EMI_044.V21 indicating the data was in +CWRv2.1. + + +--- Page 11 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 11 of 81 + + +3.2 Control Records +The following record layouts are used to partition and control the s ubmission of files between participants. +Proper control records are required within the file to insure the integrity of transmission over +telecommunication lines, as well as confirming that the data within the file has not been altered as a result +of intentional or unintentional tampering with data. +Control records defined within this version of the standard are... + HDR: Transmission Header + GRH: Group Header + GRT: Group Trailer + TRL: Transmission Trailer + +3.3 Notification of Data Transmission & Acknowledgement of +Notification/Validation Status +Data Transmission Form +When a publisher or society sends a transaction file to a recipient for processing, the sender also notifies the +recipient of the transmission in an email. The suggested format of the data transmission notification email is +shown below. The recipient then removes the file from the ftp location, validates and processes it. +Notification Of Data Transmission +This form should be used to notify the intended recipient that a file has eit her been sent to them, or is ready +to be retrieved. +From +Sending Entity +Sender +File Details +Filename +Location +Description +File size +Date/Time Stamp +Number of Transactions +Number of Records +Notification Details +Date/Time of +Notification + Re-Notification YES/NO + + + +--- Page 12 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 12 of 81 + + +Explanation: +Sending Entity Name of Society or Publisher sending the Data +Sender Name of person responsible for data exchange. Receipt of +data or any problems will need to be sent to this person +Filename Filename of data file being sent. Should be from list of agreed +names +Location FTP location from which file can be retrieved. This should be of the +form: +ftp: // prs.co.uk/ftp/incoming where prs.co.uk is the FTP site name +ftp/incoming is the full hierarchical directory name of where the +file is placed. If file sent as e-mail attachment, just enter "e-mail" +Description Content of file +File size In bytes as indicated by the "DIR " command +Date/Time +Stamp +As indicated by "DIR" command. +Number of +Transactions +Number of transactions e.g. number of works added or modified in +each group +Number of +Records +Number of records added or modified in the file +Date/Time of +Notification +Date and time when notification sent +Re-Notification YES/NO to indicate if a previous notification has been sent + +Note: The standard for dates (YYYYMMDD) and time (HHMMSS) should be used when completing this form. + +Data Acknowledgement Form +After the transaction file has been processed, the recipient notifies the sender by email that the +acknowledgement file is available. The format of the data acknowledgement email is shown below. The +acknowledgment file can then be removed from the ftp location and processed. After processing the file +should be deleted from the ftp directory. +Acknowledgement Of Notification/Validation Status +From +Society +Sender + +File Details +Filename +Location +Description +File size +Date/Time Stamp +Number of Transactions +Number of Records + + +--- Page 13 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 13 of 81 + + +Status +The above file has been received and is awaiting validation/processing YES/NO +The above file has been received and has been successfully +validated/processed +YES/NO +The above file is no longer required and can be deleted YES/NO +The above file has been received and has failed validation/processing. +Please send again. Details of failure as below +YES/NO +Details of Failure + + + + + + + +Note: The standard for dates (YYYYMMDD) and time (HHMMSS) should be used when completing this +form. + +3.4 File Level Validation +Along with the control records, a number of validation checks are performed at a file level. The editing criteria +for full file submission are listed below: +1. If the file cannot be read, the entire file will be rejected. (ER) +2. If the first record on the file is not record type HDR, the entire file will be rejected. (ER) +3. If the second record on the file is not record type GRH, the entire file will be rejected. (ER) +4. If every subsequent GRH on the file is not preceded by a GRT, the entire file will be rejected. (ER) +5. If the last record on the file is not record type TRL, the entire file will be rejected. (ER) +6. If record type GRH is not foll owed by a transaction header record type, the entire file will be rejected. +(ER) +7. If record type GRT is not followed by a record type GRH or TRL, the entire file will be rejected. (ER) +8. If the file contains more than one record type HDR or TRL, the entire file will be rejected. (ER) +9. If the header (HDR) contains an invalid version number the entire file will be rejected (ER) +10. If the header (HDR) contains a invalid revision number the entire file will be rejected (ER) + + +--- Page 14 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 14 of 81 + + +3.5 HDR: Transmission Header +Record Description +This is a required “cover sheet” for transmissions submitted by a participant. It will contain the file control +information as well as the name of the submitter. + +The character set field added for Version 2.1 is simply intended to be a way of informing societies that there +is a non -ASCII character set (such as Chinese Characters) used somewhere in the file. Such files are only +intended to be sent to societies that accept and use such character sets (e.g. CASH), and the value in the field +will in form those societies which character set has been used. The list of the relevant character sets is +currently being developed and will appear in the lookup tables once it is ready. If such a file is sent to a society +that does not accept non -ASCII character s then it should get rejected in the normal way during the file +validation process. + +If a publisher must send a CWR Sender ID (IPNN) greater than 9 digits, then as a workaround the submitting +publisher can use the existing Sender Type field to provide the leading two numbers of the CWR Sender ID +(IPNN) and use the existing Sender ID field to provide the remaining 9 digits (2 + 9 = 11 Digits). This potential +workaround should be discussed between the submitting publisher and the receiving societies prior +implementation since the receiving societies will have to accept a numeric value in place of the Sender Type +and concatenate the Sender Type and Sender ID fields to render the 11 CWR Sender ID (IPNN). + +Record Format + +Field Start Size Fmt Req Field Description +Record Type 1 3 A M HDR = Transmission Header +Sender Type 4 2 A M Indicates if the sender of the file is a society or a publisher. +Values are PB = Publisher, SO = Society, AA = Administrative +Agency, WR = Writer . If CWR Sender ID (IPNN) greater than 9 +digits (without the 2 leading 0) then use Sender Type field to +provide leading numbers of the CWR Sender ID. +Sender ID 6 9 N M If Sender Type is equal to PB, AA, or WR, the sender must enter +their assigned CWR IPI # in this field. These values reside in the +CWR Sender ID and Codes Table. If Sender Type is equal to SO, +the sending society must enter their Society Code. These values +reside in the Society Code Table. If CWR Sender ID (IPNN) greater +than 9 digits then use Sender ID to p rovide remaining numbers +of the CWR Sender ID. +Sender Name 15 45 A M The name of the sender (publisher, society, agency) +EDI Standard +Version Number +60 5 A M Indicates which version of the header and trailer records was +used to create the data in this file. This field must be set to 01.10 +for this version of the standard. +Creation Date 65 8 D M The date that this file was created. +Creation Time 73 6 T M The time of day that this file was created. +Transmission +Date +79 8 D M The date that this file was transmitted to all receiving entities. + +Field Added for CWRv2.1 +Character Set 87 15 L O To be used if this file contains data in a character set other than +ASCII. + + +--- Page 15 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 15 of 81 + + +Field Added for CWRv2.2 +Version 102 3 A O CWR version (2.2) +Revision 105 3 N O CWR revision number +Software Package 108 30 A O Name of the software package from which the file originated +Software Package +Version +138 30 A O Version of the software package from which the file originated + +Field Level Validation +1. Record Type must be equal to HDR. (ER) +2. Sender Type must be equal to PB (publisher), SO (society), WR (writer), or AA (administrative agency) +except where sender needs to use the Sender Type field to supply the leading 2 numbers of their +IPNN. (ER) +3. If Sender Type is equal to PB, WR, or AA, Sender ID must be entered and must match the assigned +entry in the CWR Sender ID and Codes Table and if Sender Type has the leading 2 numbers of the +Sender’s IPNN, then Sender Type plus Sender ID must match the assigned entry in the CWR Sender +ID and Codes Table. (ER) +4. If Sender Type is equal to SO, Sender ID must be entered and must match an entry in the Society Code +Table. (ER) +5. If Sender Type is equal to PB, Sender Name must match the name on the corresponding entry in the +CWR Sender ID and Codes Table. (ER) +6. If Sender Type is equal to SO, Sender Name must match the name on the corresponding entry in the +Society Code Table. (ER) +7. If Sender Type is equal to AA, Sender ID must contain the IPI# of the Publisher that the Administrative +Agency is acting on behalf of. Note that transactions for multiple submitting publishers cannot be co- +mingled in a single file. (ER) +8. If Sender Type is equal to AA, Sender Name must match the name on the corresponding entry in the +Publisher Code Table. (ER) +9. EDI Standard Version Number must be equal to the constant value “01.10”. (ER) +10. Creation Date must be a valid date. (ER) +11. Transmission Date must be a valid date. (ER) +12. If the Sender Type is PB, the Sender ID must be for an approved CWR participant. (ER) +13. If the Sender Type is equal to WR, Sender ID must be a valid IPI # for a writer. (ER) + +Edit for CWRv2.1 +14. If entered, the Character Set must be one of Traditional [Big5] or Simplified [GB] or a value from the +Unicode table, UTF-8 (reference www.unicode.org/charts) (ER) + +Edit for CWRv2.2 + +--- Page 16 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 16 of 81 + + +15. Version if entered and must be 2.2 (ER) +16. Revision number if entered must be a valid CWR version 2.2 revision number from the version +number lookup table, the current value must be 1 (for this revision 1) (ER) +3.6 GRH: Group Header +Record Description +The GRH record is used to indicate the presence of a group (or batch) of transactions within the file. A group +can only contain one type of transaction and this is indicated in the Transaction Type field. Also all +transactions of the same type should be contained in the same group (e.g. all NWR transactions should +appear in one single NWR group) and each group type can only be used once per file (i.e. there can only be +one NWR and one REV group per file) +Record Format +Field Start Size Fmt Req Field Description +Record Type 1 3 A M GRH = Group Header +Transaction Type 4 3 L M Indicates the type of transactions included in this group. Values +for this field reside in the Transaction Type table. +Group ID 7 5 N M A unique sequential number for this group within this file. Group +ID should start at 00001. + +Version 2.10 fields +Version Number +for this +transaction type +12 5 A M Indicates the version of the previously referred to transaction +type that will follow within this group. For CWR version 2.1, set +to 02.10 +Batch request 17 10 N O A unique sequential number to identify the group. This number +is managed by the submitter to identify the group among +multiple submission files. +Submission/ +Distribution type +27 2 L C Set to blank - Not used for CWR + +Field Level Validation +1. Transaction Type must be entered and must match an entry in the Transaction Type table. (GR) +2. Group ID must be entered, must start at 1, and must increment by 1 sequentially for each new group in +the file. (GR) +3. GRH records must follow either a GRT record or an HDR record. (ER) +4. For use of the CWR version 2 as described in this document, the Version Number must be '02.20’. (GR) +5. Each Group Transaction type can only be used once per file. (GR) +Note: Submission / Distribution Type is used only in the case of audio -visual transactions. This field will be +ignored for CWR transactions. + +--- Page 17 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 17 of 81 + + +3.7 GRT: Group Trailer +Record Description +The Group Trailer Record indicates the end of a group and provides both transaction and record counts for +the group. +Record Format +Field Start Size Fmt Req Field Description +Record Type 1 3 A M GRT = Group Trailer +Group ID 4 5 N M The same group id that was present on the preceding GRH +record. +Transaction +Count +9 8 N M The number of transactions included within this group. +Record Count 17 8 N M The number of physical records included within this group +including GRH and GRT records. + +Version 1.10 fields – Not used for CWR +Currency +indicator +25 3 L C ISO Code of the currency used for the total monetary value. ISO +codes can be found in ISO 4217 table (actually ISO 3166 country +codes 2A plus the first letter of the currency of the country : for +example, USD for Dollar in US). +Total +monetary value +28 10 N O Total monetary value represented by the group. + +Field Level Validation +1. Group ID must be equal to the Group ID presented on the previous GRH record. (GR) +2. Transaction count must be equal to the total number of transactions within this group. (GR) +3. Record count must be equal to the total number of physical records inclusive of the GRH and GRT +records. (GR) +4. Currency Indicator is mandatory if Total Monetary Value is provided (GR). +Note: Currency Indicator and Total Monetary Value will be ignored for CWR. +3.8 TRL: Transmission Trailer +Record Description +The Transmission Trailer record indicates the end of the transmission file. Control totals representing the +number of groups, transactions, and records within the file are included on this record. +Record Format +Field Start Size Fmt Req Field Description +Record Type 1 3 A M TRL = Transmission Trailer +Group Count 4 5 N M The number of groups included within this file. +Transaction +Count +9 8 N M The number of transactions included within this file. +Record Count 17 8 N M The number of physical records included in this file +including HDR and TRL records. + +--- Page 18 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 18 of 81 + + + +Field Level Validation +1. Group Count must be equal to the number of groups within the entire file. (ER) +2. Transaction count must be equal to the number of transactions within the entire file. (ER) +3. Record count must be equal to the number of physical records inclusive of the HDR and TRL records. (ER) + + +Standards for Work Registrations + +4 Transaction Header Records +Within the Common Works Registration format, a transaction is defined as “all the information required to +complete a logical unit of work that is to be passed between two or more participants in the electronic +relationship.” This version of the standard contains definitions for the following transaction types: + AGR: Agreement supporting Work Registration + NWR: New Works Registration + REV: Revised Registration + ISW: Notification of ISWC assigned to a work + EXC: Existing work which is in conflict with a work registration + ACK: Acknowledgment of Transaction +Physically within the file, a transaction consists of a Transaction Header Record followed by the Detail Records +that further define the characteristics of the transaction. The content of each Transaction Hea der Record +along with valid combinations of detail records will be defined on the subsequent pages. + +Please refer to section 6 for a definition of the structure of the CWR transactions using Backus Naur Form +(BNF). BNF is a notation for defining in an unambiguous way the relationships amongst the transactions. + +4.1 AGR: Agreement Supporting Work Registration +The Agreement Supporting Work Registration (AGR) are transactions that may be used by publishers to +inform societies of the details of agreements relating to works that the publishers are registering elsewhere +in the same file using the NWR or REV transactions. The AGR can be used to document the agreement +between one or more writers and one or more publishers, or between a publisher and one or more +publishers. This transaction is not meant to be used to register general agreements. + +The AGR contains a Submitter Agreement Number that is used to link the agreement to a work registration. +If a society has assigned an agreement number, then it too can be used as the link. The link is established as +follows: + +• The writer to publisher agreement numbers are recorded in the record that links the writer to the +publisher (PWR). The reason is that if two or more writers for a work have an agreement with the same +original publisher, it is possible to record each Society-Assigned Agreement Number / Submitter +Agreement Number in the PWR record that links that writer to the original publisher. If the original + +--- Page 19 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 19 of 81 + + +Society-Assigned Agreement Number / Submitter Agreement Number were to be stored in the original +publisher record, then there is only place for one Society-Assigned Agreement Number / Submitter +Agreement Number. +• The publisher to publisher agreement numbers are recorded in the record for the sub -publisher or +administrator. + +It is the society of the original publisher that assigns the society-assigned agreement number to the writer to +publisher agreement. It is the society of the sub -publisher or the acquiring party that assigns the society - +assigned agreement number to the publisher to publisher agreement. + +Where given, the territories and interested parties within the NWR or REV will be validated against those +entered in the corresponding AGR transaction. +Transaction Format + +Record +Type +Name Req Max +Use +Comments +AGR Agreement Supporting Work +Registration +M 1 The first record within the AGR transaction must be an +AGR record. +TER Territory in Agreement M M Specifies the territories controlled by this agreement +IPA Interested Party of Agreement M M For each TER, lists all the Interested Parties (assignor and +acquirer(s)) associated with the territory. +NPA Non-Roman Alphabet +Agreement Party Name +O M If an assignor or acquirer has a non-Roman alphabet +name, enter it here. +Record Description +The AGR record contains basic information about an agreement that cover(s) work(s). Each AGR record must +be followed by a combination of at least one TER record and at least two IPA records. The shares within the +assignor and acquirer(s) records must total 100% for each type of right for each agreement. For further +examples, see the User Manual. +Record +Type +Agreement +Type +Territory Assignor/ +Acquirer +IP’s Role Interested Party Performing +Right Share +Mechanical +Right Share +AGR OS +TER Europe +IPA Assignor CA Dupont 33,34 25 +IPA Assignor CA Leblanc 33,33 25 +IPA Acquirer E Warner France 33,33 50 +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = AGR (Agreement) +Submitter +Agreement +Number +20 14 A M The submitter’s unique identifier for this agreement. +International +Standard +Agreement Code +34 14 A O The ISAC that has been assigned to this agreement. Note this +code is not yet available. +Agreement Type 48 2 L M Code defining the category of agreement. The values reside in +the Agreement Type Table. +Agreement Start +Date +50 8 D M The date on which the transfer of rights to the acquiring party +becomes effective. This field is mandatory. + +--- Page 20 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 20 of 81 + + +Agreement End +Date +58 8 D O The date on which the transfer of rights to the acquiring party +ceases except for the agreed provisions concerning entitlements +such as a collection. +Retention End +Date +66 8 D O The end date of the retention period. This date supersedes the +function of the Agreement End Date when a retention period is +part of the agreement. The Retention End Date must be equal to +or later than the Agreement End Date. +Prior Royalty +Status +74 1 A M Indicates whether or not the acquiring party is entitled to collect +monies that were accrued before the Agreement Start Date of +this agreement but not yet distributed by the societies. Possible +values are: "N"one, or "A"ll, or "D"ate (the latter indicating a +date is entered in Prior Royalty Start Date). +Prior Royalty +Start Date +75 8 D C Date before the Agreement Start Date of this agreement from +which royalties are accrued to which the acquiring party is +entitled to collect monies not yet distributed by societies. This +date must be entered if and only if the Pr ior Royalty Status is +'D'ate. +Post-term +Collection Status +83 1 A M Indicates whether the acquiring party is entitled to collect +monies that were accrued before the Retention End Date (if it +exists), or else the Agreement End Date but not yet distributed +by the societies. Possible values are "N"o, "O"pen -ended, or +"D"ate (the latter indicating a date is entered in Post -term +Collection End Date). +Post-term +Collection End +Date +84 8 D C The date until which the acquiring party is entitled to coll ect +monies that were accrued before the Retention End Date (if it +exists), or else the Agreement End Date but not yet distributed +by the societies. This date must be after the Retention End Date +(if it exists), or else the Agreement End Date. This date mus t be +entered if and only if the Post-term Collection Status is 'D'ate. +Date of Signature +of Agreement +92 8 D O The date when the written form of the agreement (the contract) +was signed. +Number of Works 100 5 N M Number of works registered subject to this agreement specific +to this file. + +Field Start Size Fmt Req Field Description +Sales/ +Manufacture +Clause +105 1 L C The S/M -clause-indicator is a marker that shows whether the +acquiring party has acquired rights either for products +manufactured or for products sold in the territories in +agreement. Synonym: Sales/Manufacture Clause. Only two +values are allowed according to BIEM/CISAC-rules: + S = Sales Clause: A stipulation which lays down that the acquiring +party has acquired ri ghts for products sold in the territories in +agreement irrespective of the country of manufacture. + M = Manufacture Clause: A stipulation which lays down that the +acquiring party has acquired rights for products manufactured +in the territories in agreement irrespective of the country of sale. +This field is mandatory for specific agreements i.e. if Agreement +Type = OS or PS. +Shares change 106 1 B O If the shares for the writer interest can change as a result of sub- +publication or similar reason, set this field to “Y”. Default is “N”. +Advance Given 107 1 B O If there is an advance paid for this agreement, set this field to +“Y”. Default is “N”. + +--- Page 21 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 21 of 81 + + +Version 2.1 field +Society-assigned +Agreement +Number +108 14 A O The agreement number assigned by the society of the sub - +publisher. This is generally not known when the AGR is +submitted but can be supplied by the societies in the ACK +transaction. + +Transaction Level Validation +1. Only one AGR is allowed per transaction (TR). +2. There must be at least one TER record per AGR transaction (TR). +3. There must be at least two IPA records per AGR transaction -- one with an agreement role code of +assignor; and one with an agreement role code of acquirer (TR). +4. The number of NWR/REV transactions in this file that contain reference to this agreement must be less +than or equal the Number of Works. (TR) +5. The shares within the assignor and acquirer(s) records must total 100% for each type of right covered by +the agreement within a tolerance of .06%. (TR) +6. The Transaction Type of the immediately preceding GRH must be AGR for submissions from a supplier. +This edit is ignored if the AGR is part of an ACK (GR). +Field Level Validation +1. Submitter Agreement Number must be entered and must be unique within the submitter’s database. +(TR) +2. The International Standard Agreement Code must, if entered, be a valid code. (FR - default to spaces) +3. Agreement Type must be entered and must be a valid entry in the Agreement Type Table. (TR) +4. The Agreement Start Date must be a valid date. (TR) +5. The Agreement Start Date must be entered for all agreement types. (TR) +6. If entered, the Agreement End Date must be a valid date. (TR) +7. If entered, the Retention End Date must be a valid date equal to or l ater than the Agreement End Date. +(TR) +8. Prior Royalty Status must be entered, and must be “N” for none, or “A” for all, or “D” for date. (TR) +9. If the Prior Royalty Status is “D”, the Prior Royalty Start Date must be entered and must be earlier than +the Agreement Start Date. (TR) +10. If the Prior Royalty Status is “N” or “A”, the Prior Royalty Start Date must not be entered. (TR) +11. If Prior Royalty Start Date is entered, it must be a valid date. (TR). +12. If Prior Royalty Start Date is entered, Prior Royalty Status must be “D”. (TR) +13. If entered, the Post-term Collection End Date must be a valid date and must be after the Retention End +Date (if it exists), or else the Agreement End Date. (TR) +14. If Post-Term Collection Status is “D”, the Post-term Collection End-Date must be entered. (TR) +15. If Post-Term Collection Status is “N” or “O”, the Post-term Collection End-Date must not be entered. (TR) +16. Post-term Collection Status must be entered, and must be “N” for no or “O” for open -ended or “D” for +date. (TR) + +--- Page 22 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 22 of 81 + + +17. If Post-Term Collection End Date is entered, Post-term Collection Status must be “D”. (TR) +18. If entered, the Date of Signature of Agreement must be a valid date. (FR- default to zeros) +19. If entered, the Sales/Manufacture Clause must be “S” or “M”. (FR- default to space) +20. The Sales/Manufacture Clause must be entered for Agreement Type “OS” or “PS”. (TR) +21. Number of works must be numeric and greater than zero. (TR) +22. If Shares change is entered, it must be “Y” or “N”. (FR - default to “N”) +23. If Advance Given is entered, it must be “Y” or “N”. (FR - default to “N”) +24. Edit has been removed. + +4.2 NWR: New Work Registration +4.3 REV: Revised Registration +4.4 ISW: Notification of ISWC assign to a work +4.5 EXC: Existing work which is in Conflict with a Work Registration +Transaction Description +The New Works Registration (NWR) and Revised Registration (REV) are transactions that will be formatted +by publishers and sent to societies. The purpose of these transactions is to allow publishers to register and +revise works that they either own a percentage of or where they represent the owner as an administrator or +sub-publisher. Note that on revisions, all work information must be included in the transaction. Note also +that the NWR and REV transactions are also contained within an Acknowledgement (ACK) transaction s ent +from the societies back to the submitting publisher. +The Notification of ISWC (ISW) will be sent from a society to a publisher to inform the publisher of the ISWC +that has been assigned to the musical work. When an ISWC is assigned to a work by a numbe ring agency, +duplicate checking takes place. It is possible that information originally sent on OWR, or OPU records has +changed as a result of another registration. Therefore publishers can update their databases with the +validated information in the ISW transactions. +The Details of Work in Conflict (EXC) will be sent from a society to a publisher to provide information on the +details of the work that is in conflict with the registration sent by the publisher. This transaction will follow +the Acknowledgement (ACK) transaction containing a status code of “CO” (for conflict). The EXC transaction +is only valid within an ACK, and following an NWR or REV transaction. Since the work described in the EXC +transaction may not have been registered via CWR, it may not meet the data standards outlined in this +document for the NWR/REV/ /ISW transactions. +A high priority flag has been introduced in version 2.1. It is meant to speed the registration of those works +that are on the charts, etc. It is expected that it will be used sparingly. +Transaction Format +Record +Type +Name Req Max +Use +Comments +NWR/ +REV/ +New Work Registration / +Revised Registration +M 1 NWR, REV are used to submit new or revised work +registrations to societies. +ISW/ Notification of ISWC + +--- Page 23 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 23 of 81 + + +EXC Details of Work in Conflict ISW, EXC are used by societies to provide information back +regarding the registrations +SPU Publisher Controlled by +Submitter +C M List all publishers controlled by submitter. This record is +mandatory if writer ownership shares are less than 100%. +NPN Non-Roman Alphabet Publisher +Name +O M List the publisher name if available in a non -Roman +alphabet +SPT Publisher Territory of Control C M For each applicable SPU, list all territories where collection +rights exist. +OPT Publisher non -controlled +collection +O M For each applicable SPU, list territories where collection +rights do not exist +OPU Other Publisher O M +OPT Publisher Non -controlled +collection +O M For each OPU, list territories and collection +SWR Writer Controlled by Submitter O M List all the writers controlled by submitter. +NWN Non-Roman Alphabet Writer +Name +O M List the writer name if available in a non-Roman alphabet +SWT Writer Territory of Control C M For each applicable SWR, list all territories where +collection rights exist +PWR Publisher for Writer O M For each SWR, list the original publishers representing this +writer. +OWR Other Writer O M +PWR Publisher for Writer O M For each OWR, list the original publishers representing this +writer. +OWT Other writer collection O M For each applicable OWR, list all territories where non - +controlled collection rights exist +ALT Alternate Title O M +NAT Non-Roman Alphabet Title O M List the main title and any alternate titles available in non- +Roman alphabets +EWT Entire Work Title for Excerpts O 1 +NET Non-Roman Alphabet Entire +Work Title for Excerpts +O 1 +VER Original Work Title for Versions O 1 +NVT Non-Roman Alphabet Original +Title for Version +O 1 +PER Performing Artist O M +NPR Performing Artist in Non-Roman +alphabet + +REC Recording O M +ORN Work Origin O M +INS Instrumentation Summary O M +IND Instrumentation Detail O M +COM Component O M +NCT Non-Roman Alphabet Title for +Components +O M +NOW Non-Roman Alphabet Other +Writer Name +O M The non -Roman alphabet name of a writer named in +Excerpt, Version, of Component record +ARI Additional Related Information O M Comments or Society work # +XRF Work ID Cross Reference O M + +--- Page 24 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 24 of 81 + + + +Record Description +The NWR/REV//ISW/EXC record contains information specific to a work and occurring at a work level. Detail +records are listed subsequent to the NWR/REV//ISW/EXC record providing further information on the +content and ownership of the work. +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = NWR (New Work Registration) for new +registrations, REV (Revised Registration) for revisions, or ISW +(Notification of ISWC) or EXC (Existing Work in Conflict) for +outgoing notifications. +Work Title 20 60 A M Name/Title of the work. +Language Code 80 2 L O The code representing the language of this title. These values +reside in the Language Code Table. +Submitter Work # 82 14 A M Number assigned to the work by the publisher submitting or +receiving the file. This number must be unique for the publisher. +ISWC 96 11 A O The International Standard Work Code assigned to this work. +Copyright Date 107 8 D O Original copyright date of the work. +Copyright +Number +115 12 A O Original copyright number of the work. +Musical Work +Distribution +Category +127 3 L M Describes the type of music as it applies to special distribution +rules. Values for this field reside in the Musical Work Distribution +Category Table. +Duration 130 6 T C Duration of the work in hours, minutes, and seconds. This field +must be greater than zero if Musical Work Distribution Category +is equal to SER. Note that some societies may also require +duration for works where the Musical Work Distribution +Category is equal to JAZ (e.g. BMI). +Recorded +Indicator +136 1 F M Indicates whether or not the work has ever been recorded. +Text Music +Relationship +137 3 L O Indicates whether this work contains music, text, and/or both. +Values reside in the Text Music Relationship Table. +Composite Type 140 3 L O If this is a composite work, this field will indicate the type of +composite. Values reside in the Composite Type Table. +Version Type 143 3 L M Indicates relationships between this work and other works. Note +that this field is used to indicate whether or not this work is an +arrangement. Values reside in the Version Type Table. +Excerpt Type 146 3 L O If this is an excerpt, this field will indicate the type of excerpt. +Values reside in the Excerpt Type Table. +Music +Arrangement +149 3 L C If Version Type is equal to “MOD”, this field indicates the type of +music arrangement. Values reside in the Music Arrangement +Table. +Lyric Adaptation 152 3 L C If Version Type is equal to “MOD”, this field indicates the type of +lyric adaptation. Values reside in the Lyric Adaptation Table. +Contact Name 155 30 A O The name of a business contact person at the organization that +originated this transaction. +Contact ID 185 10 A O An identifier associated with the contact person at the +organization that originated this transaction. +CWR Work Type 195 2 L O These values reside in the CWR Work Type table. + +--- Page 25 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 25 of 81 + + +Grand Rights Ind 197 1 B C Indicates whether this work is originally intended for +performance on stage. +Note that this field is mandatory for registrations with the UK +societies. +Composite +Component Count +198 3 N C If Composite Type is entered, this field represents the number +of components contained in this composite. +Note that this is required for composite works where ASCAP is +represented on the work. + +Society Specific Fields for Version 2.0 +Date of +publication of +printed edition +201 8 D O For registrations with GEMA: Indicates the date that the printed, +new edition published by the submitting publisher appeared. +This information is especially relevant for the notification of sub- +published works by GEMA-sub-publishers. +Exceptional +Clause +209 1 F O For registrations of GEMA works: By entering Y (Yes), the submitter +confirms to have obtained the consent of all entitled creators to the +freely agreed division of the shares for the distribution categories of +performing rights. The note field in the first ARI record indicates the +agreed ratio between role C and role A (role split). + Additional Fields for Version 2.0 +Opus Number 210 25 A O Indicates the number assigned to this work, usually by the +composer. Part numbers are to be added with an # e.g. 28#3 +(meaning Opus 28 part 3). +Catalogue +Number +235 25 A O The work catalogue number. The abbreviated name of the +catalogue is to be added (like BWV, KV), without dots. Part +numbers are to be added with an # e.g. KV 297#1 (meaning +Köchel Verzeichnis Nr.297 part 1). + Fields for Version 2.1 +Priority Flag 260 1 F O Indicates that this work should be processed faster because it is +on the charts, is by a well-known composer, etc. + +Transaction Level Validation +1. Only one NWR or REV or ISW or EXC is allowed per transaction. (TR) +2. If Record Type is equal to REV and this work has not been successfully registered with the receiving +society in a CWR transaction, then the record type will be changed to NWR. (FR) +3. Edit Replaced +4. Total Ownership shares across all SPU and OPU records must be less than or equal to 05000 (50%) for PR +Shares and must be less than or equal to 10000 (100%) for MR Shares and SR Shares. Note that a +tolerance of plus or minus 00006 (.06%) is allowed. (TR) +5. Edit has been removed. +6. Edit has been removed +7. For each publisher controlled by the submitter that has collection shares, there must be at least one SPT +record. (TR) +8. Detail records other than those listed in the Transaction Format table may not be submitted for this +transaction (RR) + +9. Total Ownership shares across all SWR and OWR records must be either 00000 (0%) or greater than or +equal to 05000 (50%) for performing rights shares and less than or equal to 10000 (100%) for all rights. +Note that a tolerance of plus or minus 00006 (.06%) is allowed. (TR) +10. If Version Type is equal to “MOD”, at least one SWR or OWR record must contain a Writer Designation +Code equal to “AR” (Arranger), “AD”: (Adapter), “SR” (Sub -Arranger), “SA” (Sub -Author), or “TR” +(Translator). (TR) +Version 1.1 Edits +11. The total ownership shares for all writers and publishers for each right must total either 10000 (100%) +plus or minus 00006 (0.06%) or 00000 (0%). (TR) +12. A transaction must contain at least one writer record, SWR, or OWR. (TR) +13. If Record Type is "NWR", the work can not previously have been sent and accepted on a CWR transaction. +(TR) +Version 1.2 Edits +14. The total of collection shares cannot exceed 100% for a given right for a territory. Note that a tolerance +of plus or minus 00006 (.06%) is allowed. (TR) +15. There must be at least one writer (Writer Designation Code = “CA”, “A”, “C”) in a work. (TR) +16. A non-controlled publisher (OPU) can not appear in a chain started with a controlled original publisher +(SPU). (TR) +17. There can only be one original publisher (Publisher Type = “E”) in a publisher chain. (TR) +18. Edit has been removed +Version 2.0 Edits +19. Edit has been removed. +20. For each writer controlled by the submitter that has collection shares, there must be at least one SWT. +(TR) +21. Edit has been removed. +22. The Transa ction Record Type (e.g. NWR or REV) must be the same as the Transaction Type of the +immediately preceding GRH record. (GR) +Version 2.1 Edits +23. If Version Type is equal to “ORI”, there cannot be an SWR or OWR record that contains a Writer +Designation Code equal to “AR” (Arranger), “AD”: (Adapter), “SR” (Sub-Arranger), “SA” (Sub-Author), or +“TR” (Translator). (TR) +24. If all writers (SWR/OWR) are in the public domain, then the total ownership shares for performing rights +must equal zero. (Since a PD work cannot be registered for performing rights). (TR) +25. For each SPU publisher chain (but not OPUs), the sum of at least one of PR Ownership Share, MR +Ownership Share, or SR Ownership Share for SPU records with publisher type ‘E’ and ‘AQ’ must be greater +than zero. (TR) +26. If an SPU record with publisher type “AQ” appears in a chain of title then the Ownership shares on the +preceding Original publisher must be zero. (TR) + +--- Page 27 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 27 of 81 + + +27. For performing rights: Within each chain of title, the sum of Collection Shares for any group of SPT records +within a territory must equal the total of Ownership shares on the preceding Original Publisher and +Acquirer SPU records provided: +• The Shares Changed when sub-published is ‘N’ +• There is no interested party (SPU/POP/SWR/OWR) with a role code of ‘PA’ (income participant) +Note that a tolerance of plus or minus 00006 (.06%) is allowed. (TR) +28. Edit Removed +29. Edit Removed +30. For registrations to GEMA only - A work transaction must contain at least one SPU with either “PR +Affiliation society” or “MR Affiliation so ciety” set to 035 (GEMA), otherwise the work will be rejected +with the transaction status set to “NP”. (TR – GEMA only) +31. For registrations to GEMA only – If all the Writer’s Last Names are entered as “DP” (i.e. Public Domain), +then the work will be rejected with Transaction Status “NP”. (TR – GEMA only) +32. For registrations to Harry Fox only – A transaction must contain at least one SWR record. (TR – Harry Fox +only) +33. Edit has been removed. +34. Edit has been removed +35. For registrations to SGAE only - All SPU records fo r Spanish sub -publishers must include a Society - +assigned Agreement Number, or a Specific agreement must already have been notified to SGAE. (TR – +SGAE only) +36. For Registrations to SGAE only - For SGAE territories, the total Ownership shares of non-controlled right- +owners (OPUs and OWRs) and the Collection shares of controlled right -owners (SPTs and SWTs) must +equal 100% for each right. Note that a tolerance of plus or minus 00006 (0.06%) is allowed. (TR – SGAE +only) +37. For Registrations to SGAE only - For SGAE territories, the total of PR Ownership shares of Non-Controlled +publishers (OPUs) and the PR Collection shares of controlled publishers (SPTs) must be less or equal to +50%. Note that a tolerance of plus or minus 00006 (0.06%) is allowed. (TR – SGAE only) +38. For registrations to SGAE only – If all the Writers are Public Domain, then the work will be rejected. (TR +– SGAE only) +39. If CWR Work Type is equal to “FM”, the transaction must include an ORN (Work Origin) record with a +Production Title. (TR) +40. For registrations to ABRAMUS and UBC only – all SPU records for final Sub -Publisher’s collecting shares +in the territory of Brazil must include the start date of the sub -publishing agreement in the Society - +assigned Agreement Number field. The date should be left-justified in the format YYYYMMDD, and the +rest of the field should be left blank. Invalid dates will be rejected. (TR – ABRAMUS and UBC only) +41. For registrations to SACEM only - A work transaction must contain at least one SPU with either “PR +Affiliation society” or “MR Affiliation society” set to 058 (SACEM), otherwise the work will be rejected +with the transaction status set to “NP”. (TR – SACEM only). +42. For registration SIAE only – There must be at least one writer designation code of C or CA on a transaction. +(TR – SIAE only) +Version 2.2 Edits + +--- Page 28 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 28 of 81 + + +43. The sequence of records within the transaction must be as follows: NWR/REV/ISW/EXC, SPU, NPN, SPT, +OPT, OPU, NPN, OPT, SWR, NWN, SWT, PWR, OWR, NWN, OWT , PWR, ALT, NAT, EWT, NET, NOW, VER, +NVT, NOW, PER, NPR, REC, ORN, INS, IND,COM, NCT, NOW, ARI, XRF (TR) +44. For any territory and any right type the total controlled collect ion (SPT/SWT)and non -controlled +collection (OPT/OWT) must not be greater than 100. Note that a tolerance of plus 00006 (.06%) is +allowed. (TR) +45. If the Text Music Relationship indicator is MUS (music only), then there should be no CA or A or SA or TR +role codes among the work creators in SWR and OWR records (they should only be C or AR) (TR) +46. For registrations to ICE Societies only – If writer designation code AR on work, a different writer's +designation code must be C or CA (TR – ICE only) + +47. For registrations to ICE Societies only – If writer designation code SA on work, a different writer's +designation code must be A or CA (TR – ICE only) + +48. For registrations to MusicMark societies only. If SWR is BMI then any related publisher must be BMI or +non-US PRO. If SWR is ASCAP then any related publisher must be ASCAP or non-US PRO (TR- MusicMark +only) + + +49. For registrations to SGAE only. Part of the agreements hierarchy missed. There is no agreements link +registered (notified) between original publisher and the submitter of the work (TR – SGAE only). +50. For registrations to SGAE only. The sub -publisher of the work is not the registered (notified) for the +original publisher (TR – SGAE only). +51. For registrations to SGAE only.The shares for the sub-publisher are different from the shares registered +(notified) in the agreement (TR – SGAE only). +52. For Registrations to ASCAP only: The sum of collection shares for the performing rights across all writers +and publishers for the territory of US must equal 100% (plus or minus th e usual tolerance). Note: if no +OPT or OWT is present for the US, collection will be defaulted to ownership. +53. If Musical Work Distribution Category is equal to ‘SER’, the transaction must include an INS +(Instrumentation Summary) record or an IND (Instrumentation Detail) record. (TR) + +Note: If the transaction type is “EXC”, then all edits except the first may be bypassed since the existing work +that is in conflict may have been from a non-CWR registration. +Field Level Validation +1. Work Title must be entered. (TR) +Revised in Version 1.2 +2. Language Code, if entered, must match an entry in the Language Code Table. (TR) +3. Submitter Work Number must be entered and must be unique for the party submitting the file. (TR) +4. If ISWC is entered, it must be a valid ISWC. (FR - default to spaces) +5. Copyright Date must be a valid date. (FR - default to zeros) +6. Musical Work Distribution Category must be entered and it must match an entry in the Musical Work +Distribution Category table. (TR) + +--- Page 29 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 29 of 81 + + +7. If Musical Work Distribution Catego ry is equal to “SER”, Duration must be greater than zero and be a +valid combination of hours, minutes and seconds. (TR) +8. If Music Work Distribution Category is not equal to “SER”, and Duration is entered, it must be a valid +combination of hours, minutes, and seconds. (FR) +9. Recorded Indicator must be equal to “Y”, “N”, or “U”. (FR - default to “U”) +10. If Text Music Relationship is entered, it must match an entry in the Text Music Relationship table. (FR - +default to spaces) +11. If Composite Type is entered, it must match an entry on the Composite Type table. (FR - default to spaces) +12. Version Type must be entered and must match an entry on the Version Type table. (TR) +13. If Excerpt Type is entered, it must match an entry on the Excerpt Type table. (FR - default to spaces) +14. If Version Type is equal to “MOD”, Music Arrangement must be entered and must match an entry in the +Music Arrangement table. (TR) +15. If Version Type is equal to “MOD”, Lyric Adaptation must be entered and must match an entry in the Lyric +Adaptation table. (TR) +16. If entered, Grand Rights Ind. must be equal to “Y” or “N”. (FR - default to spaces) +17. When entered, CWR Work Type must match an entry in the CWR Work Type table. (FR – default to +spaces) +18. If Composite Type is entered, Composite Component Count must be entered. (TR) +19. If Composite Component Count is entered, Composite Type must be entered. (TR) +20. If entered, Composite Component Count must be numeric and must be greater than 1. (TR) +21. For registration BMI only - If Musical Work Distribution Category is equal to “JAZ” and BMI is represented +on the work, duration must be greater than zero. (TR – BMI only) +Version 1.1 Edits +22. If entered, Music Arrangement must match an entry in the Music Arrangement table. (TR) +23. If entered, Lyric Adaptation must match an entry in the Lyric Adaptation table (TR). +24. Work Title must contain only valid ASCII characters from within the ‘Titles’ section of the allowed CIS +character set. (TR) +Version 2.0 Edits +25. Edit has been removed +26. Edit Removed +27. Edit Removed +28. For registrations to GEMA only - If an ISWC number is entered and is part of the GEMA number block +then that number must already be registered by GEMA. (FR – GEMA only – Replace with spaces) +29. For registrations to SACEM only - If an ISWC number is entered and is part of the SACEM number block +then that number must already be registered by SACEM. (FR – SACEM only – Replace with spaces) +Note: If the transaction type is "EXC", then all edits regarding mandatory fields may be bypassed since the +existing work that is in conflict may have been from a non-CWR registration. + + +--- Page 30 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 30 of 81 + + +4.1 ACK: Acknowledgement of Transaction +Transaction Description + +The ACK transaction allows for acknowledgements of transactions from a recipient back to a submitter. The +acknowledgement will indicate whether or not the recipient accepted the transaction. The ACK will include +any error or warning messages associated with the original transaction. In addition, the ACK includes the +NWR, or REV and possibly EXC transaction as the recipient processed it. The NWR/REV transaction will be as +the submitter sent it but supplemented with additional information such as IPI name numbers where +possible. In particular, the use of controlled/non -controlled record types will be as for the submitter. For +example, if a submitter sent a publ isher on an SPU, the ACK will contain an SPU for that publisher. The ACK +transaction will contain all of the records sent by the submitter that have relevance to the recipient. For +example, a society will generally not return SPU/SPT records for sub -publishers in territories it does not +control. + +MSG records will precede the detail record to which they apply and the sequence numbers in the Record +Prefix will contain information consistent to the ACK record - not the original transaction. Note that validation +will not stop at the first error encountered, but will continue to report all errors (unless a severe error makes +further processing inadvisable). + +For version 2.2 there is no requirement to include the new 2.2 fields and record types in the ACK transaction. + +Transaction Format + +Record +Type +Name Req Max +Use +Comments +ACK Acknowledgement of +Transaction +M 1 +MSG Message O M List all messages generated as a result of editing this +transaction. +AGR Agreement supporting Work +Registration +O 1 Detail records are included within the AGR transaction +NWR New Works Registration O 1 Detail records are included within the NWR transaction +REV Revised Registration O 1 Detail records are included within the REV transaction +EXC Existing Work in Conflict O 1 Detail records are included within the EXC transaction + +Record Description + +The ACK record identifies and provides a status on the transaction for which this acknowledgement has been +generated. In addition, other information is provided that can be used by the recipient to link the +acknowledgment back to the original transaction. + +Record Format + +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = ACK (Acknowledgement of Transaction) +Creation Date 20 8 D M The Creation Date of the original file that contained the +transaction to which this ACK applies. +Creation Time 28 6 T M The Creation Time of the original file that contained the +transaction to which this ACK applies. +Original Group ID 34 5 N M The Group ID within which the original transaction to which this +ACK applies. + +--- Page 31 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 31 of 81 + + +Note that if the ACK is a result of a HDR or TRL record problem, +set this field to zeroes. +Original +Transaction +Sequence # +39 8 N M The Transaction Sequence # of the original transaction to which +this ACK applies. +Note that if the ACK is a result of a HDR or TRL record problem, +set this field to zeroes. +Field Start Size Fmt Req Field Description +Original +Transaction Type +47 3 L M The Transaction Type of the original transaction to which this +ACK applies. +Note that if the ACK is a result of a HDR or TRL record problem, +set this field to HDR or TRL (whichever is applicable). +Creation Title 50 60 A C The creation title as delivered by the submitter (i.e. the title of +the musical work or audio visual production…). This field is +required if the ACK is in response to an NWR or REV transaction. +Submitter +Creation # +110 20 A C The unique identifier assigned by the original submitter to this +work. This field is required if the ACK is in response to a +transaction. +Recipient +Creation # +130 20 A C The unique identifier assigned by the recipient to this work. This +field is required if the ACK is in response to a transaction and if +the transaction status indicates that the recipient has accepted +the work. +Processing Date 150 8 D M The date this transaction or file was formally processed by the +recipient. +Transaction +Status +158 2 L M The current status of this transaction. Values for this field reside +in the Transaction Status Table. + + +Transaction Level Validation +1. Only one ACK is allowed per transaction. (TR) +Version 2.0 Edits +2. The ACK transaction must be followed by one of NWR, REV, or AGR transactions. (TR) +3. The EXC transaction must follow an NWR or REV transaction within the ACK transaction. (TR) +4. The Transaction Type of the immediately preceding GRH must be ACK for submissions from a society. +(GR) + +Field Level Validation +1. The combination of Creation Date and Creation Time must match the same fields found on the HDR +record of a file generated by the submitter. (TR) +2. The combination of Original Group Number and Transaction Sequence # must be valid within the file +referred to by Creation Date and Creation Time. (TR) +3. Original Transaction Type must match the transaction referred to by the combination of Creation Date, +Creation Time, Original Group #, and Original Transaction Sequence #. (TR) +4. Creation Title must match the corresponding title associated with the Submitter Creation #. (TR) +5. Submitter Creation # must match an entry in the submitter’s data base. (TR) +6. If entered, Recipient Creation # must match an entry in the recipient’s data base. (TR) + +--- Page 32 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 32 of 81 + + +7. Processing Date must be a valid date. (TR) +8. Transaction Status must match an entry in the Transaction Status table. (TR) +Version 2.0 Edits +9. Creation Title is required if the ACK is in response to an NWR or REV transaction. (TR) + +5 Detail Records +Detail Records contain the information required to define each transaction. The following record types are +defined in this section... + + TER: Territory in Agreement + + IPA: Interested Party of Agreement + + SPU: Publisher Controlled by Submitter + + NPN: Non-Roman Alphabet Publisher Name + + SPT: Publisher Territory of Control + + OPT: Publisher non-controlled collection + + OPU: Other Publisher + + SWR: Writer Controlled by Submitter + + NWN: Non-Roman Alphabet Writer Name + + SWT: Writer Territory of Control + + OWT: Other writer collection + + PWR: Publisher for Writer + + OWR: Other Writer + + ALT: Alternate Title + + NAT: Non-Roman Alphabet Title + + EWT: Entire Work Title for Excerpts + + NET: Non-Roman Alphabet Entire Work Title for Excerpts + + VER: Original Work Title for Versions + + NVT: Non-Roman Alphabet Original Title for Versions + + PER: Performing Artist + +--- Page 33 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 33 of 81 + + + + NPR: Performing Artist Name in Non-Roman Alphabet + + REC: Recording Detail + + ORN: Work Origin + + INS: Instrumentation Summary + + IND: Instrumentation Detail + + COM: Composite Component + + NCT: Non-Roman Alphabet Title for Components + + NOW: Non-Roman Alphabet Other Writer Name + + MSG: Message + + ARI: Additional Related Information + + XRF: Work ID cross reference + +5.1 TER: Territory in Agreement +Record Description +The TER record specifies a territory either within the territorial scope of the preceding AGR agreement or +excluded from it. An agreement may cover several territories. Include one TER record for each territory, or +groups of territories covered by the agreement. It is also possible to use a combination of include and exclude +TER records. For example, if an agreement applied to all of Europe except Switzerland, you can provide a TER +record to include Europe, and one to exclude Switzerland. +The TER record must follow the AGR record to which it applies or other TE R records for the same AGR +agreement. + +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = TER (Territory in Agreement) +Inclusion/ +Exclusion +Indicator +20 1 L M This is a marker which shows whether the territory specified in +this record is part of the territorial scope of the agreement or +not. Possible entries are I (= territory included) and E (= territory +excluded). +TIS Numeric Code 21 4 L M Numeric identifier of a territory according to the new CISAC +Territory Standard. + +Record Level Validation +1. Must follow an AGR or TER record. (TR) + + +--- Page 34 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 34 of 81 + + +Field Level Validation +1. The Inclusion/Exclusion Indicator must be “I” or “E”. (TR) +2. The TIS Numeric Code must match an entry in the TIS. (TR) + +5.2 IPA: Interested Party of Agreement +Record Description +The IPA record contains information on the interested parties that concluded the agreement and on the +shares they have agreed to assign through the agreement. Each AGR record must be followed by at least one +assignor IPA record and at least one acquirer IPA record. + +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = IPA (Interested Party of Agreement) +Agreement Role +Code +20 2 L M Code defining the role of the interested party in this agreement. +The interested party can be either an assigning party or an +acquiring party. +Interested Party +IPI Name # +22 11 L O The IPI name # assigned to this interested party. These values +reside in the IPI Database. +IPI Base Number 33 13 L O The IPI base number assigned to this interested party. +Interested +Party # +46 9 A M Submitter’s unique identifier for this interested party. +Interested Party +Last Name +55 45 A M The last name of this writer or the name of the publisher. Note +that if the submitter does not have the ability to split first and +last names of writers, the entire name should be entered in this +field in the format “Last Name, First Name” including the comma +after the last name. +Interested +Party Writer First +Name +100 30 A O The first name of this writer along with all qualifying and middle +names. An entry is only allowed if the Agreement type is OS or +OG and the Agreement Role Code is Assignor. +PR Affiliation +Society +130 3 L C Number assigned to the performing rights society with which +the IP is affiliated. These values reside on the Society Code Table. +Required if PR share is greater than zero. +PR Share 133 5 N +999v99 +C Defines the percentage of the performing rights to the work, +claimed by this interested party. Within an individual IPA record, +this value can range from 0 to 100%. The PR -shares of all IPA +records within an AGR transaction must add up to 100.00 if the +agreement cover s performing rights or must be 00000 if the +agreement does not cover performing rights. At least one of PR +share, MR share, or SR share must be greater than 0. +MR Affiliation +Society +138 3 L C Number assigned to the mechanical rights society with which +this interested party is affiliated. These values reside on the +Society Code Table. Required if MR share is greater than zero. + +--- Page 35 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 35 of 81 + + +MR Share 141 5 N +999v99 +C Defines the percentage of the mechanical rights to the work, +claimed by this interested party. Within an individual IPA record, +this value can range from 0 to 100.00. The MR -shares of all IPA +records within an AGR transaction must add up to 100.00 if the +agreement covers the mechanical rights or to 000.00 if the +agreement does not cover the mechanical rights. At least one of +PR share, MR share, or SR share must be greater than 0. +SR Affiliation +Society +146 3 L C Number assigned to the synchronization rights society with +which the IP is affiliated. These values reside on the Society Code +Table. Required if SR share is greater than zero. + +Field Start Size Fmt Req Field Description +SR Share 149 5 N +999v99 +C Defines the percentage of the synchronization rights to the +work, claimed by this interested party. Within an individual IPA +record, this value can range from 0 to 100.00. The SR -shares of +all IPA records within an AGR transaction must add up to 100.00 +if the agreement covers the synchronization rights or to 000.00 +if the agreement does not cover the synchronization rights. At +least one of PR share, MR share, or SR share must be greater +than 0. + + +Record Level Validation +1. Must follow a TER or IPA record. (TR) +2. Each AGR record must be followed by one assignor IPA record and at least one acquirer IPA record. (TR) +3. At least one of PR share, MR share, or SR share must be greater than 0 in an acquirer IPA record. (TR) + +Field Level Validation +1. Agreement Role Code must be entered and must be either “AS” for assignor or “AC” for acquirer. (TR) +2. If entered, Interested Party IPI Name # must match an entry in the IPI system. (FR) +3. Interested Party # cannot duplicate the number of a different interested party currently or previously +controlled by the submitting publisher. (TR) +4. The Interested Party Writer First Name entry is only allowed if the Agreement type is “OS” or “OG” and +the Agreement Role Code is Assignor. (FR) +5. If the PR Affiliation Society is entered, it must be held in the Society Code Table. (FR) +6. PR Share must be numeric and in the range 00000 (0%) to 10000 (100%). (TR) +7. If the MR Affiliation Society is entered, it must reside in the Society Code Table. (FR) +8. The MR Share must be numeric and in the range 00000 (0%) to 10000 (100%). (TR) +9. If the SR Affiliation Society is present, it must reside in the Society Code Table. (FR) +10. The SR Share must be numeric and in the range 00000 (0%) to 10000 (100%). (TR) +11. One of PR Affiliation Society or MR Affiliation Society must be entered. (TR) +12. If PR Share is entered, then PR Affiliation must be entered. (TR) +13. If MR Share is entered, then MR Affiliation must be entered. (TR) +14. If SR Share is entered, then SR Affiliation must be entered. (TR) + +--- Page 36 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 36 of 81 + + +15. Interested Party Last Name must be entered. (TR) +16. Interested Party # must be entered (TR) +17. If IPI Base Number is entered, it must match an entry in the IPI database. (FR) +18. Interested Party Last Name must contain only valid ASCII characters from within the “Names” section of +the allowed CIS character set. (TR) +19. If entered, Interested Party Writer First Name must contain only valid ASCII characters from within the +“Names” section of the allowed CIS character set. (TR) +5.3 NPA: Non-Roman Alphabet Agreement Party Name +Record Description +This record identifies names in a non -roman alphabet for the acquiring parties of this agreement. The +language code is used to identify the alphabet. This record can be used to identify the name of the party in +the preceding IPA record. +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = NPA +Interested +Party # +20 9 A C Submitting publisher’s unique identifier for this Writer. +Interested +Party Name +29 160 A M The last of a writer or the publisher name. +Interested +Party Writer First +Name +189 160 A M The first name of a writer. +Language Code 349 2 L O The Language code of the name – must be a valid code from the +Language Code Table. + +Record Level Validation +1. This record must immediately follow an IPA that refers to the interested party named here. (RR) + +Field Level Validation +1. Interested Party # must be entered and must match the Interested Party # of the corresponding IPA +record. (RR) +2. Interested Party Name must be entered. (RR) +3. Language code, if entered, must be a valid code from the Language Code Table. (FR) +5.4 SPU: Publisher Controlled By Submitter +5.5 OPU: Other Publisher +Record Description +The SPU record contains information about original publishers, income participants, sub-publishers, and/or +administrators who are involved in the ownership and collection of this work and are under the control of +the party submitting this transaction. The OPU record contains information about original publishers that are +not under the control of the party submitting this transaction. + +--- Page 37 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 37 of 81 + + +Submission of SPU Records +A transaction must include one or more publisher chains. The first SPU record within a chain must represent +an original publisher or income participant (Publisher Type = E or PA). If that original publisher has engaged +a local administrator, that original publisher or income participant SPU record may be followed by the SPU +record that indicates the original publisher’s local administrator (Publisher Type = AM) and the collection +shares for the administrator. If there are multiple local administrators engaged by the original publisher or +income participant, they should a ll follow the original publisher or income participant, and they should +precede SPU records representing sub-publishers (Publisher Type = SE). +If the administrator has been engaged by the original publisher or income participant’s sub -publisher, as +opposed to be the original publisher or income participant, that administrator should follow the SPU record +for the sub-publisher(s). +Also note that subsequent to each SPU record, SPT records (Publisher Territory of Control) can be inserted +to designate the territory of the collection shares for the previous publisher. +OPT (publisher non-controlled collection) records can be included to give a complete picture of collection for +a territory. These follow the relevant SPU/OPU. If there is a mix of controlled and n on-controlled territories +for an SPU the OPT(s) follow the SPT(s). +Income participants may start a publisher chain, or be included in one. +The following chart demonstrates the hierarchy that exists between these records (note that the shaded box +indicates a record that can repeat). + + + + +SPT for each +territory controlled +by the original +publisher +SPT for each +territory +controlled by the +sub publisher +SPU Record for +Original +Publisher +SPU for the +administrator +SPT for the +territory +controlled by the +administrator +SPU for each +sub publisher +SPU for the +administrator +SPT for the +territory +controlled by the +administrator + + +--- Page 38 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 38 of 81 + + +Note that the hierarchy repeats for each original publisher represented on the work. The following list is a +representation of the hierarchy based on the appearance of records within a transaction: +SPU (Original Publisher/Income Participant) +SPT (Territory of Control) for Original Publisher/Income Participant +• Repeat SPT for each territory included or excluded +• +• +SPU (Administrator Publisher for previous Original Publisher/Income +Participant) +SPT (Territory of Control) for Administrator +• Repeat SPT for each territory included or excluded +• +SPU (First Sub-Publisher for previous Original Publisher/Income Participant) +SPT (First Territory of Control) for Sub-Publisher +• Repeat SPT for each territory included or excluded applying +to this Sub-Publisher that is not locally administered +• +SPU (Administrator Publisher) for previous Sub-Publisher if required +SPT (Territory of Control) for Administrator +• Repeat SPT for each territory applying to this administrator +• +• +SPU (Last Sub-Publisher for previous Original Publisher/Income Participant) +SPT (First Territory of Control) for Sub-Publisher +• Repeat SPT for each territory included or excluded +• +• +SPU (Administrator Publisher) for previous Sub-Publisher if required +SPT (Territory of Control) for Administrator +• Repeat SPT for each territory applying to this administrator +• + +All SPU records with the same Publisher Sequence Number as the Original Publisher/Income Participant SPU +are considered to be “linked” to the Original Publisher/Income Participant in a chain. Note that this hierarchy + +--- Page 39 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 39 of 81 + + +can be repeated if there are multiple O riginal Publishers for this work represented by the submitter of the +file. +On co-publishing/administration deals, note that the co -publisher/administrator needs to submit two SPU +records for itself - one as co -publisher and one as administrator for the ori ginal publisher they are +administering. +The publisher to publisher agreement numbers are recorded in the SPU for the sub -publisher or +administrator. It is the society of the sub -publisher or the acquiring party that assigns the society -assigned +agreement n umber to the publisher to publisher agreement. If submitted, the AGR contains a Society +Agreement Number that is used to link the agreement to a work registration. + +Submission of OPU Records +When submitting OPU records, the first record in the chain must b e the original publisher. If you know the +sub-publisher(s) or administrator(s), these may be included in the chain if you choose. Publisher non - +controlled collection (OPT) records are optional in a publisher chain with an OPU. + +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = SPU (Publisher Controlled by Submitter) or +OPU (Other Publisher) +Publisher +Sequence # +20 2 N M A sequential number assigned to the original publishers on this +work. +Interested +Party # +22 9 A C Submitting publisher’s unique identifier for this publisher. This +field is required for record type SPU and optional for record type +OPU. +Publisher Name 31 45 A C The name of this publishing company. This field is required for +record type SPU and optional for record type OPU. +Publisher +Unknown +Indicator +76 1 F C Indicates if the name of this publisher is unknown. +Note that this field must be left blank for SPU records. For OPU +records, this field must be set to “Y” if the Publisher Name is +blank. +Publisher Type 77 2 L C Code defining this publisher’s role in the publishing of the work. +These values reside on the Publisher Type Table . This field is +required for record type SPU and optional for record type OPU. +Tax ID # 79 9 A O The number used to identify this publisher for domestic tax +reporting. +Publisher +IPI Name # +88 11 L C The IPI Name # assigned to this publisher. If the record is of type +SPU and followed by an SPT (and hence represents the file +submitter), then the IPI Name Number is mandatory. +Submitter +Agreement +Number +99 14 A O Indicates the agreement number unique to the submitter under +which this publisher has acquired the rights to this work. +PR Affiliation +Society # +113 3 L C Number assigned to the Performing Rights Society with which +the publisher is affiliated. These values reside on the Society +Code Table. +PR Ownership +Share +116 5 N +999v99 +C Defines the percentage of the publisher’s ownership of the +performance rights to the work. This share does not define the +percentage of the total royalty distributed for performance of +the work that will be collected by the publisher. Within an +individual SPU record, this value can range from 0 to 50.0. + +--- Page 40 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 40 of 81 + + +MR Society 121 3 L C Number assigned to the Mechanical Rights Society with which +the publisher is affiliated. These values reside on the Society +Code Table. +MR Ownership +Share +124 5 N +999v99 +C Defines the percentage of the publisher’s ownership of the +mechanical rights to the work. This share does not define the +percentage of the total royalty distributed for sales of CDs, +Cassettes, etc. containing the work that will be collected by the +publisher. Within an individual SPU record, this value can range +from 0 to 100.0. +SR Society 129 3 L C Number assigned to the Society with which the publisher is +affiliated for administration of synchronization rights. These +values reside on the Society Code Table. +SR Ownership +Share +132 5 N +999v99 +C Defines the percentage of the publisher’s ownership of the +synch rights to the work. This share does not define the +percentage of the total money distributed that will be collected +by the publisher. Within an individual SPU record, this value can +range from 0 to 100.0. + +Field Start Size Fmt Req Field Description +Special +Agreements +Indicator +137 1 L O Indicates publisher claiming reversionary rights. Note that this +flag only applies to societies that recognize reversionary rights +(for example, SOCAN). +First Recording +Refusal Ind +138 1 F O Indicates whether the submitter has refused to give authority +for the first recording. +Note that this field is mandatory for registrations with the UK +societies. +Filler 139 1 A O Fill with a blank + + Version 2.0 Fields +Publisher IPI Base +Number +140 13 L O The IPI base number assigned to this publisher +International +Standard +Agreement Code +153 14 A O The ISAC that has been assigned to the agreement under which +this publisher share is to be administered. +Society-assigned +Agreement +Number +167 14 A O The agreement number assigned by the society of the sub - +publisher. + Version 2.1 Fields +Agreement Type 181 2 L O Code defining the category of agreement. The values reside in +the Agreement Type Table. +USA License Ind 183 1 L O Indicates that rights flow through SESAC/BMI/ASCAP /AMRA in +the US + +Record Level Validation +1. Edit has been removed. +2. The first SPU record within a chain must be for an Original Publisher or Income Participant (Publisher +Type = “E” or “PA”). (TR) +3. If Publisher Type is equal to “SE” or “AM” or “PA” or “ES”, Ownership Shares must be equal to zero. +(TR) + +--- Page 41 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 41 of 81 + + +Version 1.1 Edits +4. If Publisher Type is equal "AM", the publisher must have the right to administer for the preceding +publisher. (TR) +Version 1.2 Edits +5. Administrators and sub -publishers must be assigned the publisher sequence number belonging to +the original publisher or income participant on whose behalf they administer/sub-publish. (TR) +Version 2.0 Edits +6. Edit has been removed. +7. Edit has been removed. +Version 2.1 Edits +8. If the record represents an Acquirer, at least one of PR Ownership share, MR Ownership share, or SR +Ownership share must be greater than zero. (TR) +9. For Registrations to ASCAP only – Where there is an ASCAP Original publisher there must be a +collection territory that includes the United States within that chain of title. (TR – ASCAP only) +10. Edit has been removed. +11. For registrations to SGAE only - SPU records for final Sub -Publishers with SGAE interest must include a +pre-notified Society-assigned Agreement number unless the Agreement Type field is set to “OS” or “PS”. +(TR – SGAE only) +12. For registrations to SGAE only - If the record is of SGAE interest then it must include an Agreement Type. +(TR – SGAE only) +13. For registration MusicMark only – If the original publisher belongs to ASCAP then the sub -publisher or +administrator in the chain for the US cannot belong to BMI or SESAC. (TR – MusicMark only) +14. For registration MusicMark only – If the original publisher belongs to BMI or SESAC then the sub-publisher +or administrator in the chain for the US cannot belong to ASCAP. (TR – MusicMark only) +Field Level Validation +1. Publisher Sequence # must be entered. The first publisher chain on a work must have Publisher Sequence +# set to 1. Each subsequent publisher chain must be set to the Publisher Sequence # of the prior publisher +chain incremented by 1. (TR) +2. If Record Type is equal to SPU, Interested Party # must be entered. (TR) +3. Submitters must ensure that the Interested Party # is unique wit hin their system for both current and +past controlled parties. (TR) +4. If Record Type is equal to SPU or Publisher Unknown Indicator is not equal to “Y”, Publisher Name must +be entered. (TR) +5. If Record Type is equal to SPU, Publisher Type must be entered. (TR) +6. If Publisher Type is entered in an SPU record, it must match an entry in the Publisher Type table. (TR) +7. If Record Type is equal to SPU, Publisher Unknown Indicator must be blank. (TR) +8. If Record Type is equal to OPU and Publisher Unknown Indicator is enter ed, it must be equal to “Y” or +“N” (FR - default to “N”) + +--- Page 42 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 42 of 81 + + +9. If Record Type is equal to OPU and Publisher Unknown Indicator is equal to “Y”, Publisher Name must be +blank. (FR - default Publisher Unknown Indicator to “N”) +10. If Publisher IPI Name # is entered, it must match a publisher entry in the IPI database. (FR – default to +blank) +11. If Submitter Agreement Number is entered, it must match the identifier for an agreement on file with +the society of the acquiring party or it must match an identifier in the AGR tran saction. (FR - default to +spaces) +12. If entered, PR Affiliation Society # must match an entry in the Society Code table. (FR – default to spaces) +13. PR Ownership Share must be numeric. The value must also be between 00000 (0%) and 05000 (50.00%). +Note that the decimal point on this field is implied and should not be present within the field. (TR) +14. Edit has been removed. +15. If entered, MR Affiliation Society # must match an entry in the Society Code table (FR – default to spaces) +16. MR Ownership Share must be numeric. Th e value must also be between 00000 (0%) and 10000 +(100.00%). Note that the decimal point on this field is implied and should not be present within the field. +(TR) +17. If entered, SR Affiliation Society # must match an entry in the Society Code table. (FR – default to spaces) +18. SR Ownership Share must be numeric. The value must also be between 00000 (0%) and 10000 (100.00%). +Note that the decimal point on this field is implied and should not be present within the field. (TR) +19. All ownership shares must be equal to 0 if Publisher Type is not equal to “E” or “AQ” (i.e. only Original +Publishers can have ownership shares greater than zero). (TR) +20. If entered, Special Agreement Indicator must match an entry in the Special Agreement Indicator table. +(FR - default to spaces) +21. If entered, First Recording Refusal Ind must be equal to Y or N. (FR - default to spaces) +22. Edit has been removed. +Version 1.1 Edits +23. If entered, Tax ID must be numeric. (FR - default to zeros) +Version 2.0 Edits +24. If Publisher IPI Base Number is entered, it must match an entry in the IPI database. (FR) +25. If International Standard Agreement Code is entered, it must match an entry in the international +agreements database. (FR - default to spaces). +26. If Society-Assigned Agreement Number is entered, it must match the identifier for an agreement on file +with the society of the acquiring publisher. (FR - default to spaces) +27. If Record Type is “OPU”, Special Agreements Indicator can only be “L” or blank. (FR - default to space) +28. If Record type is “OPU”, and Publisher type is invalid or missing, default to “E”. (FR - default to “E”) +29. If the Publisher Name matches the name of a society in the Society Code table, and the Publisher IPI +Name # is missing or invalid, then the registration is invalid. (TR) +Version 2.1 Edits +30. If Agreement Type is entered, it must match an entry in the Agreement Type table. (FR) + +--- Page 43 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 43 of 81 + + +31. If USA License Ind is entered, it must match a value in the USA License Indicator table. (FR) +32. If the role code is ‘AQ’, this SPU record must follow an SPU record with a role code of ‘E’. (TR) +33. For registrations to GEMA only - If Agreement Type is equal to “PS”, the Submitter Agreement +Number must be entered and must match an entry in a corresponding AGR-record. (TR - GEMA only) +34. For registrations to GEMA only – If Record Type is equal to “SPU” and Publisher Type is equal to “SE”, an +Agreement Type must be entered. (TR – GEMA only). +35. Edit has been removed. +36. Edit has been replaced +37. If entered, Publisher Name must contain only valid ASCII characters from within the “Names” section of +the allowed CIS character set (TR) +38. For registrations to SACEM only – If Record Type is equal to “SPU” and Publisher Type is equal to “SE”, +an Agreement Type must be entered. All SPU records for final Sub-Publishers in the FR must supply pre- +notified Society-assigned Agreement Number. (TR – SACEM only). +39. Edit Replaced (see 46) +Version 2.2 Edits +40. If Record Type is equal to SPU and is the collecting publisher the Publisher IPI Name Number must be +entered. (TR) +41. For registrations to Societies requiring Society Assigned Agreement Numbers only: A Society Assigned +Agreement Number must be provided missing on SPU (TR) +42. For registrations to Societies requiring Society Assigned Agreement Numbers only:– The provided Society +Assigned Agreement Number must be not represent a terminated agreement (TR) +43. For registrations to Societies requiring Society Assigned Agreement Numbers only: The provided Society +Assigned Agreement Number must exist in the Society system (TR) +44. For registrations to Societies requiring Society Assigned Agreement Numbers only:– The claimed territory +on the provided Society Assigned Agreement Number must be included in the agreement on file at the +Society (TR) +45. For registrations to ICE Societies only – The Society Assigned Agreement Number must refer to the +quoted combination of Submitter, Assignor and Agreement number on SPU on transaction (TR – ICE only) +For registrations to SACEM only: The IPI -name-number provided for the Original Publisher SPU must be +equal to the assignor IPI -name-number for the agreement represented by the first 7 characters of the +Society Provided Agreement Number. +46. For registrations to SACEM only: The IPI-name-number provided for the Sub-Publisher SPU must be equal +to the assignee IPI-name-number for the agreement represented by the last 7 characters of the Societ y +Provided Agreement Number. +5.6 NPN: Non-Roman Alphabet Publisher Name +Record Description +This record identifies publisher names in non -roman alphabets for this work. The language code is used to +identify the alphabet. This record can be used to identify the name of the publisher in the preceding SPU/OPU +record. + +--- Page 44 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 44 of 81 + + +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type =NPN +Publisher +Sequence # +20 2 N M A sequential number assigned to the original publishers on this +work. +Interested +Party # +22 9 A M Submitting publisher’s unique identifier for this publisher. +Publisher Name 31 480 A M The name of this publishing company in non-roman alphabet. +Language Code 511 2 L O The Language code of the name – must be a valid code from the +Language Code Table. +Record Level Validation +1. This record must immediately follow an SPU that refers to the publisher named here. (RR) +Field Level Validation +1. Publisher Sequence # must be entered and must match the Publisher Sequence # of the +corresponding SPU record. (RR) +2. Interested Party # must be entered and must match the Interested Party # of the corresponding SPU +record. (RR) +3. Publisher Name must be entered. (RR) +4. Language code, if entered, must be a valid code from the Language Code Table. (FR) +5.7 SPT: Publisher Territory of Control +5.8 OPT: Publisher Non-Controlled Collection +Record Description +The SPT record defines the territory and the collection shares for the preceding SPU publisher. Note that SPT +records follow an SPU, NPN (Non-Roman alphabet Publisher Name), or another SPT record. The SPT record +cannot be used with OPU records. Include one SPT record for each territory, or groups of territories for which +the preceding publisher has collection rights. It is also p ossible to use a combination of include and exclude +SPT records. For example, to specify collection shares for all of Europe except Switzerland, you can provide +an SPT record to include Europe, and one to exclude Switzerland. By its nature, the SPT used to exclude a +territory should not have any share percentages greater than zero. It is possible to have all zero shares on an +SPT that includes one or more territories. Such a record would be used to record a publisher’s place in the +chain of agreements. +The Shares change flag alerts the recipient that the ownership will not equal collection for this publisher +chain. Usually this is because the agreements permit shares to change when the work is sub -published. The +sequence number which was added in version 2.1 should run from 1 to the number of SPTs for each SPU. +The OPT record is used to record non -controlled collection. OPT records are optional and should not be +treated as providing authoritative information (whether it follows an OPU or an SPU). They can be useful in +making clear the total collection for a territory where shares change on sub -publication or where the +territories of controlled collection vary between chains. +An OPT can follow an OPU or an SPU. An SPT can never follow an OPU in a non-controlled chain. An OPT can +follow an SPT under the same SPU and an SPT can follow an OPT under the same SPU. + +--- Page 45 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 45 of 81 + + + +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = SPT (Publisher Territory of Control) or OPT +(publisher non-controlled collection) +Interested +Party # +20 9 A M Submitting publisher’s unique identifier for this Publisher. +Constant 29 6 A M Set this field equal to spaces. +PR Collection +Share +35 5 N +999v99 +C Defines the percentage of the total royalty distributed for +performance of the work which will be collected by (paid to) the +publisher within the above Territory. It can be a range from 0 to +50.00. +MR Collection +Share +40 5 N +999v99 +C Defines the percentage of the total royalty distributed for sales +of CDs, Cassette Tapes, etc. in which the work is included which +will be collected by (paid to) the publisher. It can be a range from +0 to 100.00. +SR Collection +Share +45 5 N +999v99 +C Defines the percentage of the total royalty distributed for +Synchronization rights to the work which will be collected by +(paid to) the publisher. It can be a range from 0 to 100.00. + Version 2.0 Fields +Inclusion/ +Exclusion +Indicator +50 1 L M This is a marker which shows whether the territory specified in +this record is part of the territorial scope of the agreement or +not. Possible entries are I (= territory included) and E (= territory +excluded). +TIS Numeric Code 51 4 L M A territory within which this publisher claims the right to collect +payment for performance or use of this work. These values +reside in the TIS Code Table. +Shares change 55 1 B O If the shares for the writer interest change as a result of sub - +publication in this territory or for a similar reason, set this field +to “Y”. + Version 2.1 Fields +Sequence # 56 3 N M A sequential number assigned to each territory following an +SPU. + +Record Level Validation +1. If the Inclusion/Exclusion Indicator is “I”, at least one of PR Collection Share, MR Collection Share, or SR +Collection Share must be greater than zero. (TR) +2. Edit has been removed. +3. Edit has been removed. +4. Edit has been removed. +Version 2.0 Edits +5. Each Territory (TIS code) included on an SPT/OPT record can only be linked to one SPU/OPU for a given +right. (TR) +6. For registrations to ASCAP only – The first SPT record immediately following an SPU must have the +“Inclusion/Exclusion Indicator” set to “I”. (TR – ASCAP only) + +--- Page 46 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 46 of 81 + + +Field Level Validation +1. When entered, SPT records must follow an SPU, NPN or SPT record. (TR) +2. The Interested Party # must be entered and must be equal to the Interested Party # on the previous SPU +record. (TR) +3. Edit has been removed. +4. Edit has been removed. +5. Edit has been removed. +6. PR Collection Share must be between 00000 (0%) and 5000 (50%). (TR) +7. MR Collection Share must be between 00000 (0%) and 10000 (100%). (TR) +8. SR Collection Share must be between 00000 (0%) and 10000 (100%). (TR) +Version 2.0 Edits +9. TIS Numeric Code must be entered and must match an entry in the TIS database. (TR) +10. Inclusion/Exclusion Indicator must be entered and must be either “E” for excluded or “I” for included. +(TR) +11. If Shares change is entered, it must be set to “Y” or “N”. (FR - default – “N”) +Version 2.1 Edits +12. Sequence # must be present. (RR) +13. Sequence # must be 1 for the first SPT/OPT after an SPU/OPU, and increment by 1 for each subsequent +SPT. (RR) +Version 2.2 Edits +14. When entered, OPT records must follow an SPU, NPN, SPT, OPU or OPT record. (TR) +5.9 SWR: Writer Controlled By Submitter +5.10 OWR: Other Writer +Record Description +The SWR record contains specific information on a writer controlled by the submitting publisher. Submitters +will, on a best efforts basis, provide either the writer’s tax id number (e.g. Social Security Number) or their +IPI Name # to ensure exact identification by representative societies. +The OWR record contains whatever information is available on writers that are not controlled by the +submitting publisher. +Subsequent to each SWR record, SWT records (Writer Territory of Control) must be inserted to designate +Collection Shares for the related writer within a designated territory. +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = SWR (Writer Controlled by Submitter) or OWR +(Other Writer) + +--- Page 47 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 47 of 81 + + +Interested +Party # +20 9 A C Submitting publisher’s unique identifier for this Writer. This field +is required for record type SWR and optional for record type +OWR. +Writer Last Name 29 45 A C The last name of this writer. Note that if the submitter does not +have the ability to split first and last names, the entire name +should be entered in this field in the format “Last Name, First +Name” including the comma after the last name. This field is +required for record type SWR and optional for record type OWR. +Writer First Name 74 30 A O The first name of this writer along with all qualifying and middle +names. +Writer Unknown +Indicator +104 1 F C Indicates if the name of this writer is unknown. Note that this +field must be left blank for SWR records. For OWR records, this +field must be set to “Y” if the Writer Last Name is blank. +Writer +Designation Code +105 2 L C Code defining the role the writer played in the composition of +the work. These values reside in the Writer Designation Table . +This field is required for record type SWR and optional for record +type OWR. +Tax ID # 107 9 A O The number used to identify this writer for domestic tax +reporting. +Writer IPI +Name # +116 11 L O The IPI Name # assigned to this writer. +PR Affiliation +Society # +127 3 L O Number assigned to the Performing Rights Society with which +the writer is affiliated. These values reside on the Society Code +Table. +PR +Ownership Share +130 5 N +999v99 +O Defines the percentage of the writer’s ownership of the +performance rights to the work. Within an individual SWR +record, this value can range from 0 to 100.0. Note that writers +both own and collect the performing right interest. +MR Society 135 3 L O Number assigned to the Mechanical Rights Society with which +the writer is affiliated. These values reside on the Society Code +Table. +MR +Ownership Share +138 5 N +999v99 +O Defines the percentage of the writer’s ownership of the +mechanical rights to the work. Within an individual SPU record, +this value can range from 0 to 100.0. + +Field Start Size Fmt Req Field Description +SR Society 143 3 L O Number assigned to the Mechanical Rights Society with which +the writer is affiliated. These values reside on the Society Code +Table. +SR +Ownership Share +146 5 N +999v99 +O Defines the percentage of the writer’s ownership of the +synchronization rights to the work. Within an individual SPU +record, this value can range from 0 to 100.0. + Society/Region Specific Fields +Reversionary +Indicator +151 1 F O Indicates writer involved in the claim. +Note that this flag only applies to societies that recognize +reversionary rights (for example, SOCAN). +First Recording +Refusal Ind +152 1 B O Indicates whether the submitter has refused to give authority +for the first recording. Note that this field is mandatory for +registrations with the UK societies. +Work For Hire +Indicator +153 1 B O Indicates whether or not this work was written for hire. +Filler 154 1 A O + +--- Page 48 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 48 of 81 + + + Version 2.0 Fields +Writer IPI Base +Number +155 13 L O The IPI base number assigned to this writer. These values reside +in the IPI database. +Personal Number 168 12 N O The personal number assigned to this writer in the country of +his/her residence. + Version 2.1 Fields +USA License Ind. 180 1 L O Indicates that rights flow through SESAC/BMI/ASCAP/AMRA in +the US. + +Record Level Validation +1. Edit has been removed. +2. Unless the total writers’ ownership shares is equal to 100% for each right (that is, the work is +unpublished), each SWR record must be followed by at least one PWR record. (TR) +3. Edit has been removed. +Field Level Validation +1. If Record Type is equal to SWR, Interested Party # must be entered. (TR) +2. Submitters must ensure that the Interested Party # is unique within their system for both current and +past controlled parties. (TR) +3. If Record Type is equal to SWR or Writer Unknown Indicator is not equal to “Y”, Writer Last Name must +be entered. (TR) +4. If Record Type is equal to SWR, Writer Unknown Indicator must be blank. (TR) +5. If Record Type is equal to OWR, and Writer Unknown Indicator is entered, it must be equal to Y or N (FR +- default to N) +6. If Record Type is equal to OWR, and Writer Unknown Indicator is equal to “Y”, Writer Last Name must be +blank. (FR - default Writer Unknown Indicator to “N”) +7. For SWR records, Writer Designation Code must be entered. (TR) +8. If entered, Writer Designation Code must match an entry in the Writer Designation table. (TR) +9. If entered, Writer IPI Name # must match a writer entry in the IPI database. (FR – default to spaces) +10. If entered, PR Affiliation Society # must match an entry in the Society Code table. (FR - default to spaces) +11. PR Ownership Share must be numeric. The value must also be between 00000 (0%) and 10000 (100.00%). +Note that the decimal point on this field is implied and should not be present within the field. (TR) +12. If entered, MR Affiliation Society # must match an entry in the Society Code table (FR - default to spaces) +13. MR Ownership Share must be numeric. The value must also be between 00000 (0%) and 10000 +(100.00%). Note that the decimal point on this field is implied and should not be present within the field +(TR) +14. If entered, SR Affiliation Society # must match an entry in the Society Code table. (FR - default to spaces) +15. SR Ownership Share must be numeric. The value must also be between 00000 (0%) and 10000 (100.00%). +Note that the decimal point on this field is implied and should not be present within the field. (TR) +16. If entered, Reversionary Indicator must be equal to Y, N, or U. (FR - default to spaces) + +--- Page 49 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 49 of 81 + + +17. If entered, First Recording Refusal Ind must be equal to Y or N. (FR - default to spaces) +18. If entered, Work for Hire Indicator must be equal to ‘Y’ or ‘N’ (FR - default to spaces) +19. Edit has been removed. +Version 1.1 Edits +20. When Version equals “MOD”, if Writer Designation code equal “C” or “CA” or “A” and with zero shares, +there must exist another SWR with non-zero shares and Writer Designation of “AR”, “TR”, “SA”, “SR” or +“AD”. (TR) +21. If entered, Tax ID must be numeric. (FR - default to zeros) +Version 2.0 Edits +22. If Writer IPI Base Number is entered, it must match an entry in the IPI database. (FR) +23. Edit has been removed. +Version 2.1 Edits +24. If USA License Ind is entered, it must match a value in the USA License Indicator table. (FR) +25. Edit has been removed. +26. Edit has been removed. +27. For Registrations to SGAE only – The Writer Unknown Indicator must not be set to “Y”. (TR – SGAE only) +28. For Registrations to SGAE only – The Writer Last Name must not be set to “Unknown” or any other name +indicating the Writer is not known (TR – SGAE only) +29. If entered, Writer Last Name must contain only valid ASCII characters from within the “Names” section +of the allowed CIS character set. (TR) +30. If entered, Writer First Name must contain only valid ASCII characters from within the “Names” section +of the allowed CIS character set. (TR) +31. For registrations to SACEM Societies only – If Record Type is OWR, the Writer Last Name must be entered, +or else the Writer will be ignored. (RR – SACEM only). +5.11 NWN: Non-Roman Alphabet Writer Name +Record Description +This record ident ifies writer names in non -roman alphabets for this work. The language code is used to +identify the alphabet. This record can be used to identify the name of the writer in the preceding SWR/OWR +record. +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = NWN +Interested Party # 20 9 A C Submitting publisher’s unique identifier for this Writer. +Writer Last Name 29 160 O M The last or single name of this writer. +Writer First Name 189 160 O O The first name of this writer. +Language Code 349 2 L O The Language code of the name – must be a valid code from the +Language Code Table. + +--- Page 50 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 50 of 81 + + + +Record Level Validation +1. This record must immediately follow an SWR that refers to the writer named here. (RR) +Field Level Validation +1. Interested Party # must be entered and must match the Interested Party # of the corresponding SWR +record. (RR) +2. Writer Name must be entered. (RR) +3. Language code, if entered, must be a valid code from the Language Code Table. (FR) +5.12 SWT: Writer Territory of Control +5.13 OWT: Other Writer Collection +Record Description +This record was introduced in version 2.0. The SWT record specifies collection shares for a writer and the +application territory or territories for the collection shares. Note that SWT records must follow an SWR, NWN +(Non-Roman Alphabet Writer Name) or another SWT record and cannot be used with OWR records. One +SWT record must be used for every territory that is included or excluded. The most frequent case will be that +the writer collects one share percentage for the world (2136). It often happens that a writer collects a higher +percentage for his home territory only. In this case there would be an SPT with one percentage for the world; +an exclude SPT for the home territory with zero percentage; and an include SPT for the home territory with +the percentage collected there. +The Shares change flag alerts the recipient that the ownership will not equal collection for this writer. Usually +this is because the agreements permit shares t o change when the work is sub -published. The sequence +number which was added in version 2.1 should run from 1 to the number of SWTs for each SWR. +The OWT record is used to record collection for non-controlled writers. OWT records are optional and should +not be treated as providing authoritative information. They can be useful in making clear the total collection +for a territory where shares change on sub -publication or where the territories of controlled collection vary +between chains. +An OWT can follow an OWR. It can never appear in a controlled chain (that is after a SWR). + + +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = SWT (writer Territory of Control) or OWT +(other writer collection). +Interested Party # 20 9 A C Submitting publisher’s unique identifier for this Writer. +PR Collection +Share +29 5 N +999v99 +O Defines the percentage of the total royalty distributed for +performance of the work which will be collected by (paid to) the +writer within the above Territory. Within an SWT record, can be +a range from 0 to 100.00. +MR Collection +Share +34 5 N +999v99 +O Defines the percentage of the total royalty distributed for sales +of CDs, Cassette Tapes, etc. in which the work is included which +will be collected by (paid to) the writer. Within an SWT record, +can be a range from 0 to 100.00. + +--- Page 51 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 51 of 81 + + +SR Collection +Share +39 5 N +999v99 +O Defines the percentage of the total royalty distributed for +Synchronization rights to the work which will be collected by +(paid to) the writer. Within an SWT record, can be a range from +0 to 100.00. +Inclusion/ +Exclusion +Indicator +44 1 L M This is a marker which shows whether the territory specified in +this record is part of the territorial scope of the agreement or +not. Possible entries are I (= territory included) and E (= territory +excluded). +TIS Numeric Code 45 4 L M A territory within which this writer has the right to collect +payment for performance of this work. These values reside in +the TIS Code Table. +Shares change 49 1 B O If the shares for the writer interest change as a result of sub - +publication in this territory, set this field to “Y”. + Version 2.1 Fields +Sequence # 50 3 N M A sequential number assigned to each territory following an +SWR or OWR + +Record Level Validation +1. If the Inclusion/Exclusion Indicator is “I”, at least one of PR Collection Share, MR Collection Share, or SR +Collection Share must be greater than zero. (TR) +2. Each Territory (TIS code) included on an SWT record can only be linked to one SWR for a given right. (TR) +3. If the Inclusion/Exclusion Indicator is “E”, all Collection Shares must be set to zero. (FR). +4. For Registrations to ASCAP only - The first SWT record immediately following an SWR must have the +“Inclusion/Exclusion Indicator” set to “I”. (TR - ASCAP only) +Field Level Validation +1. An SWT record must follow an SWR, NWN or SWT record. (TR) +2. For an SWT record The Interested Party # must be entered and must be equal to the Interested Party # +on the previous SWR record. (TR) +3. PR Collection Share must be between 00000 (0%) and 10000 (100%). (TR) +4. MR Collection Share must be between 00000 (0%) and 10000 (100%). (TR) +5. SR Collection Share must be between 00000 (0%) and 10000 (100%). (TR) +6. TIS Numeric Code must be entered and must match an entry in the TIS database. (TR) +7. Inclusion/Exclusion Indicator must be entered and must be either “E” for excluded or “I” for included. +(TR) +8. If Shares change is entered, it must be set to “Y” or “N”. (FR - default – “N”) +Version 2.1 Edits +9. Sequence # must be present. (RR) +10. Sequence # must be 1 for the first SWT after an SWR and increment by 1 for each subsequent SWT. (RR) +Version 2.2 Edits +11. An OWT must follow an OWR, NWN, or OWT record. (TR) +12. An OWT must not follow a SWR in a controlled chain. (TR) + +--- Page 52 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 52 of 81 + + +13. For an OWT record the Interested Party # must be equal to the Interested Party # on the previous OWR +record. Note that this can be blank (TR) +5.14 PWR: Publisher For Writer +Record Description +The PWR record is used to indicate the publisher that represents the writer designated on the previous SWR +or OWR record for writers that are published (total writer ownership shares for each right are less than +100%). PWR is optional for OWR records. Use a separate PWR record to document each publisher that +represents the writer. +The writer to publisher agreement numbers are recorded in the PWR. The reason is that if two or more +writers for a work have an agreement with the same original publisher, it is possible to record each Society- +Assigned Agreement Number / Submitter Agreement Number in the PWR record that links that writer to the +original publisher. It is the society of the original publisher that assigns the society -assigned agreement +number to the writer to publisher agreement. The AGR contains a Society Agreement Number t hat is used +to link the agreement to a work registration. +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = PWR (Publisher for Writer) +Publisher IP # 20 9 A C The publisher interested party number pointing back to the +SPU/OPU record for the original publisher/income participant +representing this writer. +Publisher Name 29 45 A C The name of the publisher indicated by the Interested Party # +field. +Version 2.0 Fields +Submitter +Agreement +Number +74 14 A O The unique number assigned to this agreement by the +submitter. +Society-Assigned +Agreement +Number +88 14 A O The unique number assigned to this agreement by the society +Version 2.1 Fields +Writer IP # 102 9 A C The writer interested party number pointing back to the +SWR/OWR record in an explicit link. +Version 2.2 Fields +Publisher +Sequence # +111 2 N M Reference to publisher chain this link relates to. This allows the +specific original publisher/income participant entry for this +relationship to be identified. + +Record Level Validation +1. Edit has been removed +Revised in Version 2.0 +2. Edit has been replaced +3. Edit has been replaced + +--- Page 53 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 53 of 81 + + +Field Level Validation +1. Edit has been replaced. +2. Edit has been replaced. +Version 2.0 Edits +3. If Submitter Agreement Number is entered, it must match the identifier for an original agreement on file +with the society of the origin al publisher or it must match an identifier in the AGR transaction with +agreement type of “OS” or “OG”. (FR - default to spaces) +4. If Society-Assigned Agreement Number is entered, it must match the identifier for an original agreement +on file with the society of the original publisher. (FR - default to spaces) +Version 2.1 Edits +5. Edit has been replaced +Version 2.2 Edits +6. For registrations to MusicMark societies only - If SWR is BMI then any related publisher must be BMI or +non-US PRO. If SWR is ASCAP then any related publisher must be ASCAP or non-US PRO +7. Publisher Sequence # must be entered and it must match the Publisher Sequence # of the relating +Original SPU/OPU record. (TR) +8. For controlled chains (where the PWR follows an SWR) writer IP # must be entered.(TR) +9. For controlled chains (where the PWR follows an SWR) the Publisher IP # must be entered. (TR) +10. For controlled chains (where the PWR follows an SWR) the Publisher Name must be entered. (TR) +11. Writer IP # must match the Interested Party # entered on the preceding SWR/OWR record. Note this can +be blank on an OWR record. (TR) +12. Publisher IP # must match the Interested Party # for the original publisher/income participant referenced +by the publisher sequence # field. Note this can be blank on an OWR record. (TR) +13. Publisher Name must match the name of the original publisher/income participant referenced by the +publisher sequence # field. (FR - default to the proper name referred to by the publisher seq uence #). +(FR) +14. For registrations to ICE Societies only – Agreement number missing on PWR (TR – ICE only) +15. For registrations to ICE Societies only – Agreement not found in ICE on quoted combination of Submitter, +Assignor and Agreement number on PWR on transaction (TR – ICE only) +16. For registrations to ICE Societies only – Agreement is terminated (TR – ICE only) +17. For registrations to ICE Societies only – Agreement number on PWR does not exist in ICE (TR – ICE only) +18. For registrations to ICE Societies only – Claimed territory on transaction is not included on publisher's +agreement in ICE (TR – ICE only) +19. For registrations to ICE Societies only – Original publisher on transaction does not own the quoted +agreement number (TR – ICE only) + + +--- Page 54 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 54 of 81 + + +5.15 ALT: Alternate Title +Record Description +This record identifies alternate titles for this work. The language code is used to identify titles that have been +translated into a language other than the original. Note that this applies to translation of the title only - not +a translation of the work. Including record type VER would indicate a work translation. +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = ALT (Alternate Title) +Alternate Title 20 60 A M AKA or pseudonym of the work title. +Title Type 80 2 L M Indicates the type of alternate title presented on this record. +These values reside in the Title Type Table. +Language Code 82 2 L C The code representing the language that this alternate title has +been translated into. These values reside in the Language Code +Table. A language Code Must be entered if the Title Type is equal +to “OL” or “AL” + +Field Level Validation +1. Alternate Title must be entered. (RR) +2. Title Type must be entered and must match an entry in the Title Type table other than “OT” (Original +Title). (FR - default to Alternative Title) +3. If Language Code is entered, it must match an entry in the Language Code Table. (RR) +4. The Alternate Title must contain only valid ASCII characters from within the “Titles” section of the allowed +CIS character set unless the Title Type is equal to “OL” or “AL”. (RR) +5. If the Title Type is equal to “OL” or “AL”, the Alternate Title must contain only valid ASCII characters from +within the “CWR National Titles” section of the allowed CIS character set. (RR). +6. If the Title Type is equal to “OL” or “AL”, Language Code must be entered. (RR) +5.16 NAT: Non-Roman Alphabet Title +Record Description +This record identifies titles in other alphabets for this work. The language code is used to identify the +alphabet. This record can be used to describe the original title of a work, and it can also be used to describe +alternate titles. +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = NAT (Non-Roman Alphabet Title) +Title 20 640 A M The work title in non-Roman alphabet +Title Type 660 2 L M Indicates the type of title presented on this record (original, +alternate etc.). These values reside in the Title Type Table. +Language Code 662 2 L O The Language code of the title – must be a valid code from the +Language Code Table. + + + +--- Page 55 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 55 of 81 + + +Record Level Validation +1. Only one instance of this record per work can contain the title type of original title. +Field Level Validation +1. Title must be entered. (RR) +2. Title Type must be entered and must match an entry in the Title Type table. (FR - default to Alternative +Title) +3. If Language Code is entered, it must match an entry in the Language Code Table. (RR) +5.17 EWT: Entire Work Title for Excerpts +Record Description +If the work being registered is an excerpt, the EWT record is used to indicate the title of the complete work +from which the excerpt has been derived. +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = EWT (Entire Work Title for Excerpts) +Entire Work Title 20 60 A M The title of the entire work from which this excerpt has been +derived. +ISWC of +Entire Work +80 11 A O The International Standard Work Code assigned to the work +from which this excerpt has been derived. +Language Code 91 2 L O The code defining the language in which the entire was originally +written. These values reside in the Language Code Table. +Writer 1 Last +Name +93 45 A O Last name of the original writer/composer of the work from +which this excerpt has been taken. Note that if the submitter +does not have the ability to split first and last names, the entire +name should be entered in this field in the format “Last Name, +First Name” including the comma after the last name. +Writer 1 First +Name +138 30 A O First name of the original writer/composer of the work from +which this excerpt has been taken. +Source 168 60 A O A description of the source from which the work was obtained. + Version 2.0 Fields +Writer 1 +IPI Name # +228 11 L O The IPI Name # assigned to the first writer of the entire work. +Writer 1 +IPI Base Number +239 13 L O The IPI base number assigned to this writer. These values reside +in the IPI database. +Writer 2 +Last Name +252 45 A O Last name of the second writer of this component. Note that if +the submitter does not have the ability to split first and last +names, the entire name should be entered in this field in the +format “Last Name, First Name” including the comma after the +last name. +Writer 2 +First Name +297 30 A O First name of the second writer of this component. +Writer 2 +IPI Name # +327 11 L O The IPI Name # assigned to the second writer of the entire work. +Writer 2 +IPI Base Number +338 13 L O The IPI base number assigned to this writer. These values reside +in the IPI database. +Submitter +Work # +351 14 A O Number assigned to the work by the party submitting the file. +This number must be unique for the submitter. + +--- Page 56 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 56 of 81 + + +Record Level Validation +1. Only one EWT record is allowed per transaction (TR). + +Field Level Validation +1. Entire Work Title must be entered. (RR) +2. If entered, the ISWC of Entire Title must be a valid ISWC. (FR - default to spaces) +3. If entered, Language Code must match an entry in the Language Code table. (FR- default to spaces) +Version 2.0 Edits +4. If entered, Writer 1 IPI Name # must match an entry for the Writer in the IPI database. (FR - default to +spaces) +5. If entered, Writer 2 IPI Name # must match an entry for the Writer in the IPI database. (FR - default to +spaces) +6. If entered, Writer 1 IPI Base Number must match an entry in the IPI database. (FR- default to spaces) +7. If entered, Writer 2 IPI Base Number must match an entry in the IPI database. (FR- default to spaces) +8. If entered, the Submitter Work Number must uniquely identify the work. (FR- default to spaces) +9. Entire Work Title must contain only valid ASCII characters from within the ‘Titles’ section of the allowed +CIS character set. (RR) +10. If entered, Writer 1 Last Name must contain only valid ASCII characters from within the ‘Names’ section +of the allowed CIS character set. (FR) +11. If entered, Writer 1 First Name must contain only valid ASCII characters from within the ‘Names’ section +of the allowed CIS character set. (FR) +12. If entered, Writer 2 Last Name must contain only valid ASCII characters from within the ‘Names’ section +of the allowed CIS character set. (FR) +13. If entered, Writer 2 First Name must contain only valid ASCII characters from within the ‘Names’ section +of the allowed CIS character set. (FR) +5.18 VER: Original Work Title for Versions +Record Description +If the work being registered is a version of another work, the VER record is used to indicate the title of the +original work from which the version has been derived. + + +--- Page 57 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 57 of 81 + + +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = VER (Original Work Title for Versions) +Original Work +Title +20 60 A M Original title of the work from which this version was derived. +ISWC of Original +Work +80 11 A O The International Standard Work Code assigned to the work +from which this version has been derived. +Language Code 91 2 L O The code defining the language in which the work was originally +written. These values reside in the Language Code Table. +Writer 1 Last +Name +93 45 A O Last name of the original writer/composer of the work from +which this version has been derived. Note that if the submitter +does not have the ability to split first and last names, the entire +name should be entered in this field in the format “Last Name, +First Name” including the comma after the last name. +Writer 1 First +Name +138 30 A O First name of the original writer/composer of the work from +which this version has been derived. +Source 168 60 A O A description of the source from which the work was obtained. +Version 2.0 Fields +Writer 1 IPI Name +# +228 11 L O The IPI Name number assigned to the first writer of the original +work. +Writer 1 IPI Base +Number +239 13 L O The IPI base number assigned to this writer. These values reside +in the IPI database. +Writer 2 Last +Name +252 45 A O Last name of the second writer of the original work. Note that if +the submitter does not have the ability to split first and last +names, the entire name should be entered in this field in the +format “Last Name, First Name” including the comma after the +last name. +Writer 2 First +Name +297 30 A O First name of the second writer of the original work. +Writer 2 IPI Name +# +327 11 L O The IPI Name number assigned to the second writer of this +original work. +Writer 2 IPI Base +Number +338 13 L O The IPI base number assigned to this writer. These values reside +in the IPI database. +Submitter Work # 351 14 A O Number assigned to the original work by the party submitting +the file. This number must be unique for the submitter. + +Record Level Validation +1. Only one VER record is allowed per transaction (TR). +Field Level Validation +1. Original Work Title must be entered. (RR) +2. If entered, the ISWC of Original Work must be a valid ISWC. (FR - default to spaces) +3. If entered, Language Code must match an entry in the Language Code table. (FR- default to spaces) +Version 2.0 Edits +4. If entered, Writer 1 IPI Name # must match an entry for the Writer in the IPI database. (FR - default to +spaces) + +--- Page 58 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 58 of 81 + + +5. If entered, Writer 2 IPI Name # must match an entry for the Writer in the IPI database. (FR - default to +spaces) +6. If entered, Writer 1 IPI base Number must match an entry in the IPI database. (FR - default to spaces) +7. If entered, Writer 2 IPI base Number must match an entry in the IPI database. (FR - default to spaces) +8. If entered, the Submitter Work Number must uniquely identify the work. (FR - default to spaces) +9. Original Work Title must contain only valid ASCII characters from within the “Titles” section of the +allowed CIS character set. (RR) +10. If entered, Writer 1 Last Name must contain only valid ASCII characters from within the “Names” section +of the allowed CIS character set. (FR) +11. If entered, Writer 1 First Name must contain only valid ASCII characters from within the “Names” section +of the allowed CIS character set. (FR) +12. If entered, Writer 2 Last Name must contain only valid ASCII characters from within the “Names” section +of the allowed CIS character set. (FR) +13. If entered, Writer 2 First Name must contain only valid ASCII characters from within the “Names” section +of the allowed CIS character set. (FR) +5.19 PER: Performing Artist +Record Description +The name of a person or group performing this work either in public or on a recording. +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = PER (Performing Artist) +Performing Artist +Last Name +20 45 A M Last name of a person or full name of a group that has performed +the work on a recording or in public. Note that if the performer +is known by a single name, it should be entered in this field. +Performing Artist +First Name +65 30 A O First name associated with the performing artist identified in the +previous field. +Performing Artist +IPI +Name # +95 11 L O The IPI Name # corresponding to this performing artist. Values +reside in the IPI database. +Version 2.0 Field +Performing Artist +IPI +Base Number +106 13 L O The IPI base number assigned to this performing artist. + +Field Level Validation +1. Performing Artist Last Name must be entered. (RR) +2. If Performing Artist IPI Name # is entered, it must match an entry on the IPI database. (FR - default to +spaces) +Version 2.0 Edit + +--- Page 59 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 59 of 81 + + +3. If Performing Artist IPI Base Number is entered, it must match an entry in the IPI database. (FR - default +to spaces) +4. Performing Artist Last Name must contain only valid ASCII characters from within the ‘Names’ section of +the allowed CIS character set (RR) +5. If entered, Performing Artist First Name must contain only valid ASCII characters from within the ‘Names’ +section of the allowed CIS character set (RR) +5.20 NPR: Performance Data in non-roman alphabet +Record Description +This record contains either the non-roman alphabet name of a person or group performing this work either +in public or on a recording, or the language/dialect of the performance. This is particularly important for +Chinese dialects such as Cantonese. Performance Dialect, if entered, must be a valid code from ISO 639-2(T). +(FR) +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = NPR +Performing Artist +Name +20 160 A C Name of a person or full name of a group that has performed +the work on a recording or in public. Note that if the performer +is known by a single name, it should be entered in this field. +Performing Artist +First Name +180 160 A O First name of a person that has performed the work on a +recording or in public. . +Performing Artist +IPI Name # +340 11 L O The IPI Name # corresponding to this performing artist. Values +reside in the IPI database. +Performing Artist +IPI Base Number +351 13 L O The IPI base number assigned to this performing artist. +Language Code 364 2 L O The Language code of the name – must be a valid code from the +Language Code Table. +Version 2.1 Fields +Performance +Language +366 2 L C The language used in the performance – must be a valid code +from the Language Code Table +Performance +Dialect +368 3 L C The dialect used in the performance – must be a valid code from +ISO 639 -2(T) e.g. if the performance is in Mandarin, YUE +Cantonese, MIN NAN or HAKKA, then use: CHN, YUH, CFR or HAK + +Field Level Validation +1. Edit has been removed. +2. If Performing Artist IPI Name # is entered, it must match an entry on the IPI database. (FR - default to +spaces) +3. If Performing Artist IPI Base Number is entered, it must match an entry in the IPI database. (FR - default +to spaces) +4. Language code, if entered, must be a valid code from the Language Code Table. (FR) +Version 2.1 Edits +5. One of Performing Artist Name, Performance Language, or Performance Dialect must be entered. (RR) + +--- Page 60 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 60 of 81 + + +6. Performance Language, if entered, must be a valid code from the Language Code Table. (FR) +7. Performance Dialect, if entered, must be a valid code from ISO 639-2(T). (FR) +5.21 REC: Recording Detail +Record Description +The REC record contains information on the first commercial release of the work. +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = REC (Recording Detail) +Release Date 20 8 D O Date the work was or will be released for public +consumption. This date can be a past, present, or future +date. +Constant 28 60 A O Fill with blanks. +Release +Duration +88 6 T O Duration of the release of the work. +Constant 94 5 A O Fill with blanks. + Version 2.0 Fields +Album Title 99 60 A O The name of the album in which the work was included if the +work was released as part of an album. +Album Label 159 60 A O Name of the organization that produced and released the album +in which the release of the work was included. +Release Catalog # 219 18 A O Number assigned by the organization releasing the album for +internal purposes such as sales and distribution tracking. +EAN 237 13 L O European Article Number of release (EAN-13) +ISRC 250 12 L O International Standard Recording Code of the recording of the +work on the release (according to ISO 3901). +Recording Format 262 1 L O Code that identifies the content of the recording: “A” (audio), +“V” (video). +Recording +Technique +263 1 L O Identifies the recording procedure: “A” (Analogue), “D” (Digital), +“U” (Unknown). + Version 2.1 Field +Media Type 264 3 L O BIEM/CISAC code for media type. + Version 2.2 Field +Recording Title 267 60 A O Title of the Sound Recording +Version Title 327 60 A O Title given to the version of the Sound Recording (for example: +“remixed by”) +Display Artist 387 60 A O Name of the artist of the Sound Recording +Record Label 447 60 A O Name of the organisation that produced the Sound Recording of +the work +ISRC Validity 507 20 L C If an ISRC is supplied, Indicates that the validity of the ISRC :“Y” +is valid, “U” the link is invalid, “N” the ISRC is invalid +Submitter +Recording +Identifier +527 14 A O The submitter’s unique identifier for this recording. + +--- Page 61 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 61 of 81 + + + +Record Level Validation +1. Edit has been removed. +Field Level Validation +1. At least one of the optional fields must be entered. (RR) +2. If entered, Release Date must be a valid date. (FR - default to zeros) +3. If entered, Release Duration must be a valid combination of hours, minutes, and seconds. (FR - default +to zeros) +4. Edit has been removed. +5. Edit has been removed. +6. Edit has been removed. +7. Edit has been removed. +8. Edit has been removed. +Version 2.0 Edits +9. If entered, EAN must be a valid European Article Number of release. (FR- default to spaces) +10. If entered, ISRC must be a valid International Standard Recording Code. (FR- default to spaces) +11. If entered, Recording Format must be “A” for Audio or “V” for video. (FR - default to 'A') +12. If entered, Recording Technique must be “A” for analogue, “D” for digital or “U” for unknown. (FR - +default to “U”) +13. For registration to SESAC only - If the work registration contains a SESAC interest, then Recording Format, +Recording Technique, EP Cassette EP CD Flag, Album CD Album Cassette Flag, Single Flag, and Twelve +Inch Single Flag must be entered. (TR – SESAC only) +Version 2.1 Edits +14. If entered, the Media type must match an entry from the BIEM/CISAC list of Media Types. (FR) +15. If entered, the First Album Title must contain only valid ASCII characters from within the ‘Titles’ section +of the allowed CIS character set. (FR) +Version 2.2 Edits +16. If entered, Recording Title must contain only valid ASCII characters from within the ‘Titles’ section of the +allowed CIS character set. (TR) +17. If entered, Version Title must contain only valid ASCII characters from within the ‘Titles’ section of the +allowed CIS character set. (TR) +18. If an ISRC is supplied, ISRC Validity must be Y, N, or U. (RR) +19. If entered, the Submitter Recording Identifier must uniquely identify the recording.(RR) + + +--- Page 62 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 62 of 81 + + +5.22 ORN: Work Origin +Record Description +The purpose of this record is to describe the origin of the work. The origin may be a library, or an audio-visual +production or both. If the work originated in an AV production, additional information regarding the usage +of the work within the production can be helpful. Note that the cue sheet is always the final authority for +usage data. Many identifiers for the audio-visual production have been added with version 2.1 including the +reference as used in the CIS tool, AV Index. +Note a Library work that is only available via the Internet will still need to have the CD Identifier field filled +in. Any wording can be used in this field, such as “INTERNET”. +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = ORN (Work Origin) +Intended Purpose 20 3 L M Indicates the type of production from which this work +originated. These values reside in the Intended Purpose Table. +Production Title 23 60 A C Name of the production from which this work originated. This +field is required when CWR Work Type on the NWR record +equals “FM”. +CD Identifier 83 15 A C If Intended Purpose is equal to LIB (Library Work), enter the +identifier associated with the CD upon which the work appears. +Cut Number 98 4 N O If Intended Purpose is equal to LIB (Library Work), enter the track +number on the CD Identifier where the work appears. +Version 2.1 Fields +Library 102 60 A C The library from which this work originated. +BLTVR 162 1 A O An indication of the primary use of the work within the AV +production. The definitive source for cue usage is the cue sheet. +Filler 163 25 N O Reserved for future use +Production # 188 12 A O The number generated by the production company to identify +the work. +Episode Title 200 60 A O Title of the episode from which this work originated. +Episode # 260 20 A O Number assigned to the episode by the producer. +Year of +Production +280 4 N O The year in which the production of the film or episode was +completed. +AVI Key... The following two fields form the unique key for the audio-visual +work within the AV Index. +AVI Society Code 284 3 N O The Society code of the society whose audio visual work detail +entry is referenced in the AV Index. These values reside on the +Society Code Table. +Audio-Visual +Number +287 15 A O Unique number used internally by the “owning” society to +identify the audio-visual work as referenced in the AV Index. +Version 2.2 Fields +V-ISAN Unique identifier for audio-visual production in which this work +is first used + ISAN 302 12 A O Root Segment + +--- Page 63 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 63 of 81 + + + Episode 314 4 A O Episode or Part number + Check Digit 1 318 1 A O Check Character for the root and episode segment. + Version 319 8 A O Version Segment + Check Digit 2 327 1 A O Check Character for the Version Segment +EIDR 328 21 A O EIDR + EIDR 328 20 A O Root Number + Check Digit 348 1 A O Check Character + + +Record Level Validation +1. Edit has been removed. +Field Level Validation +1. Intended Purpose must be entered and must match an entry in the Intended Purpose Table. (RR) +2. Edit has been removed. +3. Edit has been removed. +4. If Intended Purpose is equal to “LIB” (Library Work), CD Identifier is required. (RR) +Version 2.0 Edit +5. If entered, Cut Number must be numeric. (FR) +Version 2.1 Edit +6. If entered, BLTVR must contain one of “B” for background, “L” for logo, or “T” for theme, “V” for visual +or “R” for rolled up cues. (FR) +7. If entered, the V-ISAN must be valid. (FR) +8. If entered, Year of Production must be a valid year. (FR) +9. If entered, AVI Key must match an entry in the AV Index. (FR) +10. Production Title or Library must be entered. (RR) +11. If entered, Production Title must contain only valid ASCII characters from within the “Titles” section of +the allowed CIS character set. (RR) +12. If entered, Episode Title must contain only valid ASCII characters from within the “Titles” section of the +allowed CIS character set. (FR) +13. If Intended Purpose is equal to “FIL” or “TEL” then a Production Title must be entered (TR). + Version 2.2 Edit +14. If entered, the V-ISAN must be valid. (FR) +15. If Entered, The EIDR must be valid. (FR) + + +--- Page 64 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 64 of 81 + + +5.23 INS: Instrumentation Summary +Record Description +The INS record provides information on standard and non-standard instrumentation for serious works. If the +Musical Work Distribution Category is SER then instrumentation detail is required using one or more Standard +Instrumentation Type, one or more IND records, or one Instrumentation Description. The Instrumentation +Description is the least desirable, and should be used only if the other fields are not available. It is possible +to use both a Standard Instrumentation Type and one or more IND records to describe, for example, a wind +quintet and a piano. It is also possible to use both one or more Standard Instrumentation Type and one or +more IND records to describe, for example, a work written for two wind quintets and two pianos. +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = INS (Instrumentation Summary) +Number of Voices 20 3 N O Indicates the number of independent parts included in this work. +Standard +Instrumentation +Type +23 3 L C Describes instrumentation if standard instrumentation is used +on this work. Note that this field is required if IND records are +not entered and if Instrumentation Description is blank. These +values reside in the Standard Instrumentation Table. +Instrumentation +Description +26 50 A C Describes instrumentation if non -standard instrumentation is +used on this work. Note that this field is required if IND records +are not entered and if Standard Instrumentation Type is blank. + +Record Level Validation +1. Edit has been removed. +2. Edit has been removed. +3. Edit has been removed. +4. Edit has been removed. +5. Edit has been removed. +Version 2.1 Edit +6. Edit has been removed. +7. If Standard Instrumentation Type and/or IND records exist, the Instrumentation Description will be +ignored. (FR) +5.24 IND: Instrumentation Detail +Record Description + The IND record provides information on standard instruments or voices for serious works. If the Musical +Work Distribution Category is SER then instrumentation detail is required using one or more INS records as +well as IND records to describe the individual instruments (if any). +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = IND (Instrumentation Detail) +Instrument Code 20 3 L M Indicates the use of a specific instrument in this version of +instrumentation. These values reside in the Instrument Table. + +--- Page 65 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 65 of 81 + + +Number of +Players +23 3 N O Indicates the number of players for the above instrument +Record Level Validation +1. If provided, IND records must follow an INS or IND record. (RR) + +Field Level Validation +1. Instrument Code must be entered and must match an entry in the Instrument Table. (RR) +2. Number of Players must be numeric. (RR) +5.25 COM: Component +Record Description +If the work being registered is a composite work, the COM record will identify an individual component of +the composite. +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = COM (Composite Component) +Title 20 60 A M The title of the original work from which a portion was taken and +included in the composite work. +ISWC of +Component +80 11 A O The International Standard Work Code assigned to the original +work from which a portion was taken and included in this +composite work. +Submitter +Work # +91 14 A O The number that the submitting party uses to refer to this +composite component. +Duration 105 6 T O The duration of this composite component. +Writer 1 Last +Name +111 45 A M Last name of the first writer of this component. Note that if the +submitter does not have the ability to split first and last names, +the entire name should be entered in this field in the format +“Last Name, First Name” including the comma after the last +name. +Writer 1 First +Name +156 30 A O First name of the first writer of this component. +Writer 1 IPI Name +# +186 11 L O The IPI Name number assigned to the first writer of this +component. +Writer 2 Last +Name +197 45 A O Last name of the second writer of this component. Note that if +the submitter does not have the ability to split first and last +names, the entire name should be entered in this field in the +format “Last Name, First Name” including the comma after the +last name. +Writer 2 First +Name +242 30 A O First name of the second writer of this component. +Writer 2 IPI Name +# +272 11 L O The IPI Name number assigned to the second writer of this +component. + Version 2.0 Fields +Writer 1 IPI +Base Number +283 13 L O The IPI base number assigned to this writer. These values reside +in the IPI database. +Writer 2 IPI +Base Number +296 13 L O The IPI base number assigned to this writer. These values reside +in the IPI database. + +--- Page 66 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 66 of 81 + + +Record Level Validation +1. COM records can only be entered for works where the Composite Type is entered. (RR) +Field Level Validation +1. Title must be entered. (RR) +2. If entered, the ISWC of Component must be a valid ISWC. (FR - default to blank) +3. If entered, Duration must consist of a valid combination of hours, minutes, and seconds. (FR - default to +zeros) +4. Writer 1: Last Name must be entered. (RR) +5. If entered, Writer 1 IPI Name # must match an entry for the Writer in the IPI database. (FR - default to +spaces) +6. If entered, Writer 2 IPI Name # must match an entry f or the Writer in the IPI database. (FR - default to +spaces) +7. Writer 2 Last Name is required if Writer 2 First Name is entered. (FR - default both names to blank) +Version 2.0 Edits +8. If entered, Writer 1 IPI base Number must match an entry in the IPI database. (FR- default to spaces) +9. If entered, Writer 2 IPI base Number must match an entry in the IPI database. (FR- default to spaces) +10. If entered, the Submitter Work Number must uniquely identify the work. (FR- default to spaces) +11. Title must contain only valid ASCII characters from within the ‘Titles’ section of the allowed CIS character +set. (RR) +12. If entered, Writer 1 Last Name must contain only valid ASCII characters from within the ‘Names’ section +of the allowed CIS character set. (FR) +13. If entered, Writer 1 First Name must contain only valid ASCII characters from within the ‘Names’ section +of the allowed CIS character set. (FR) +14. If entered, Writer 2 Last Name must contain only valid ASCII characters from within the ‘Names’ section +of the allowed CIS character set. (FR) +15. If entered, Writer 2 First Name must contain only valid ASCII characters from within the ‘Names’ section +of the allowed CIS character set. (FR) +5.26 MSG: Message +Record Description +MSG records are used to communicate the results of validation on individual transactions back to the +transaction’s originator. A table of messages used for CWR can be found in the CWR website. The table +contains all of the messages in this format. The message texts in the table have been reworded to make them +more easily understood, but the content is the same as in this manual. The combination of Record Type, +Message Level and Validation Number can be used to reference the error in this document. Message Type +provides you with the severity of the error. For example, if Message Type is equal to T, then the entire work +registration has been rejected. + +--- Page 67 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 67 of 81 + + + +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = MSG (Message) +Message Type 20 1 L M Indicates whether this information is a warning, error, or for +information only. Values are F = Field Rejected, R = Record +Rejected, T = Transaction Rejected, G = Group Rejected, E = +Entire File Rejected +Original Record +Sequence # +21 8 N M The Record Sequence Number within the transaction associated +with this acknowledgment that caused the generation of this +message. +Record Type 29 3 A M The record type within the original transaction that caused +generation of this message. +Message Level 32 1 L M The level of editing that was responsible for generation of this +message. Values are E = Entire File, G = Group, T = Transaction, +R = Record, F = Field. +Validation +Number +33 3 A M Identifies the specific edit condition that generated this +message. Note that the combination of Record Type, Message +Level, and Validation Number points back to a condition within +this document. +Message Text 36 150 A M The text associated with this message. + +Field Level Validation +1. Message Type must be entered and must be equal to “F”, “R”, “T”, “G” or “E”. (TR) +2. Original Record Sequence # must correspond to a value contained within the transaction that caused the +generation of this message. (TR) +3. Message Level must be equal to “F”, “R”, “T”, “G” or “E”. (TR) +4. Message Text must be ente red and must correspond to the validation referenced by Record Type, +Message Level, and Validation Number within this document. (TR) +Version 2.0 Edits +5. Record Type must be entered, and must correspond to the record being validated. (TR) +6. Validation Number must be entered and must refer to a validation in this document. (TR) +Note that the size of the Original Sequence Number has increased in version 2.0. +5.27 NET: Non-Roman Alphabet Entire Work Title for Excerpts +5.28 NCT: Non-Roman Alphabet Title for Components +5.29 NVT: Non-Roman Alphabet Original Title for Version +Record Description +This record identifies titles in other alphabets for this work. The language code is used to identify the +alphabet. This record can be used to describe the original title of a work, and it can also be used to describe +alternate titles. + +--- Page 68 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 68 of 81 + + +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = NET/NCT/NVT (Non -Roman Alphabet +Entire Work Title for Excerpts/ Non-Roman Alphabet Title +for Components/ Non -Roman Alphabet Original Title for +Versions) +Title 20 640 A M The title in non-Roman alphabet. +Language Code 660 2 L O The Language code of the title – must be a valid code from +the Language Code Table. + +Record Level Validation +1. If Record Type is NET, this record must contain the title for the work described in the immediately +preceding EWT. (RR) +2. If Record Type is NCT, this record must contain the title for the component described in the immediately +preceding COM record. (RR) +3. If Reco rd Type is NVT, this record must contain the title for the work described in the immediately +preceding VER record. (RR) +Field Level Validation +1. Title must be entered. (RR) +2. If Language Code is entered, it must match an entry in the Language Code Table. (RR) +5.30 NOW: Non-Roman Alphabet Other Writer Name +Record Description +This record identifies writer names in non -roman alphabets for the work named in an EWT (entire work for +an excerpt), VER (original work for a version), or COM (component) record. The language code is used to +identify the alphabet. +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = NOW +Writer Name 20 160 O M The last or single name of this writer. +Writer First Name 180 160 O M The first name of this writer. +Language Code 340 2 L O The Language code of the name – must be a valid code from the +Language Code Table. +Writer Position 342 1 L O The position of the writer in the corresponding EWT, VER, or +COM record + +Record Level Validation +1. This record must follow an EWT, VER, COM, NET, NCT, NVT that refers to a work written by the writer +named here. (RR) +Field Level Validation +1. Writer Name must be entered. (RR) +2. Language code, if entered, must be a valid code from the Language Code Table. (FR) + +--- Page 69 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 69 of 81 + + +3. Writer Position, if entered, must be either “1” or “2”. (FR – default to “1”) +5.31 ARI: Additional Related Information +Record Description +This record may contain specific information or general information. The Work # is used to relate the work +being registered to an entry in an unidentified performance/use list, or to correct a work referenced in a cue +sheet, web site, etc. The free-text note contains general information addressed to one or all societies. It may +be used for important information concerning the work registration. Societies are not obliged to process ARI +records, even if the note is addressed to them. The note field should be used sparingly. + +Record Format +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = ARI (Additional Related Information) +Society # 20 3 L M Number assigned to the Society to which the Note is addressed. +These values reside Society Code Table. If the note is addressed +to all societies that use the ARI record, use “000”. +Work # 23 14 A C The Society work # that relates to this registration. It may have +been found on an unidentified list, or a website etc. +Type of Right 37 3 L M Indicates that this information relates to performing rights, +mechanical rights, sync. rights or all rights (ALL) +Subject Code 40 2 L C Subject of the ARI. +Note 42 160 A C Free text field pertaining to the type of right and subject +specified above. + +Record Level Validation +1. Either Work # or Note must be entered. (RR) +Field Level Validation +1. Society # must be entered and must match an entry in the Society Code table or “000”. (RR) +2. Type of right must be entered and must be a valid right or “ALL” for all. (RR) +3. Subject Code must be entered if Note is not blank, and must match an entry in the Subject Code +table. (RR) +4. For registrations to GEMA only – ARI records with subject code GW are mandatory in case the +GEMA authors involved in the work have agreed on freely negotiated music and lyrics portions for +the Performing Rights, i. e. where the submitter has entered Yes in Exceptional Clause and the +distribution of shares in the work deviates from the basic distribution laid down in the GEMA +distribution plan. Each ARI record must have a value of 035 in the soci ety # field, a value of PER in +the type of right field, a value of GW in the subject code field, search terms to check that the +necessary information is contained in the note fields, and structured input in the Note Fields. ARI +records with subject code GW are used to determine the ratio between music and lyrics (Role Split, +ARI-type-1) as well as to indicate the ratio within the role CA (C/A-Split, ARI-type-2 or ARI-type-3). +(TR – GEMA only) +5.32 XRF: Work ID Cross Reference +Record Description + +--- Page 70 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 70 of 81 + + +This Record contains identifiers issued by any organisation including but not limited to the intended recipient +of the file (though the principle work identifier should still be provided in NWR, ACK, REV and other headers). +Field Start Size Fmt Req Field Description +Record Prefix 1 19 A M Set Record Type = XRF (Work ID Cross Reference) +Organisation +Code +20 3 L M Number assigned to the Organisation (e.g. Society, publisher, +DSP etc...) which generated the Work Code. These values reside +in the Transmitter Code Table, or can be “ISW” for ISWC or “ISR” +for ISRC. Note: Do not use “000”or “099”. +Identifier 23 14 A M An identifier that relates to this work Transaction. +Identifier Type 37 1 L M The type of identifier ( “W” for Work, “R” for Recording, “P” for +Product, “V“ for Video) +Validity 38 1 F M Indicates whether the Identifier is valid or not: “Y” is valid, “U” +the link is invalid, “N” the identifier is invalid + +Field Level Validation +1. Organisation Code must be entered and must match an entry in the Transmitter Code Table. (RR) +2. Identifier Type must be entered and must be equal to W, R, or P. (RR) +3. Validity Indicator must be entered and must be equal to Y, N or U. (RR) + +6 CWR Data Structure +6.1 Definition of CWR using BNF +BNF is an acronym for "Backus Naur Form". John Backus and Peter Naur introduced for the first time a formal +notation to describe the syntax of a given language. Since then, almost every author of books on new +programming languages used it to specify the syntax rules of the language. It is also used to describe data +structures and interface construction. When applied rigorously, it provides an unambiguous definition of +what is valid (and by implication, what is not). +BNF is a way of defining structures algebraically. It uses a small number of symbols as defined in the following +table: +Symbol Meaning +< > Identifier: a name for something being defined or referenced. In practice, many now use +bold text to denote an identifier, normal text for text that is to be used literally +::= Is defined as +| Or +[] Optional statement +{} Repetitive Items +BNF is used below to describe the composition of a CWR file, with its headers and transactions, in a clear +unambiguous way. + +--- Page 71 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 71 of 81 + + +CWR_File ::= HDR_Transmission_Header + {Group_Info} + TRL_Transmission_Trailer +Group_Info ::= GRH_Group_Header + {Transaction_Info} + GRT_Group_Trailer +Transaction_Info ::= AGR | NWR | REV | | ISW | ACK +AGR_Transaction ::= AGR_Transaction_Record + {Territory_Information} +Territory_Information ::= {TER_Territory} + {Assignor_Information} + {Acquirer_Information} +Assignor_Information ::= IPA_Interested_Party_of_Agreement + [NPA_Non-Roman_Alphabet_Agreement_Party_Name] +Acquirer_Information ::= IPA_Interested_Party_of_Agreement + [NPA_Non-Roman_Alphabet_Agreement_Party_Name] +ACK_Transaction ::= ACK_Transaction_Record + [{MSG_Records}] (precedes record pertaining to message) + AGR | NWR [EXC]| REV [EXC] +NWR_Transaction ::= NWR_Transaction_Record +[{Controlled_Publisher_Info}] +[{Other_Publisher_Information}] +[{Controlled_Writer_Information}] +[{Other_Writer_Information}] +[{ALT_Alternate_Title}] +[NAT_Non-Roman_Alphabet_Title] +[Information_for_Excerpts] +[Information_for_Versions] [{PER_Performing_Artist}] +[{NPR_Performing Artist_in_Non-Roman_Alphabet}] +[REC_Recording_Information] +[ORN_Work_Origin] +[{Instrumentation_Information}] +[{Information_for_Components }] +[{ARI_Additional_Related_Information}] +[{XRF_Work ID Cross Reference }] + +Controlled_Publisher_Information::= Original_Publisher_Information +[{Administrator_Information}] +[{Subpublisher_Information}] +[{SPU_Income_Participant_Publisher}] +Original_Publisher_Information::= SPU_Original_Publisher | SPU_Income_Participant_Publisher + [NPN_Non-Roman_Alphabet_Publisher Name] +[{SPT_Territory_of_Control}] +[{OPT_Non_Controlled_Collection}] + +Administrator_Information ::= SPU_Administrator +[NPN_Non-Roman_Alphabet_Publisher Name] +[{SPT_Territory_of_Control}] +[{OPT_Non_Controlled_Collection}] +Subpublisher_Information ::= SPU_Subpublisher +[NPN_Non-Roman_Alphabet_Publisher Name] + +--- Page 72 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 72 of 81 + + + [{SPT_Territory_of_Control}] +[{OPT_Non_Controlled_Collection}] +Other_Publisher_Information::= OPU_Other_Publisher + [NPN_Non-Roman_Alphabet_Publisher Name] + [{OPT_Non-Controlled_Collection}] +Controlled_Writer_Information::= SWR_Controlled_Writer | SWR_Income_Participant_Writer +[NWN_Non-Roman_Alphabet_Writer Name] +[{SWT_Writer_Territory_of_Control}] +{PWR_Publisher_for_Writer} +Other_Writer_Information::= OWR_Other_Writer | OWR_Other_Participant_Writer +[NWN_Non-Roman_Alphabet_Writer Name +[{OWT_Other_Writer_Territory_of_Control}] +{PWR_Publisher_for_Writer} +Instrumentation_Information ::= INS_Instrumentation_Summary + [{IND_Instrumentation_Detail}] +Information_for_Excerpts ::= EWT_Entire_Work_Title_for_Excerpts +[NET_Non-Roman_Alphabet_Title_for_Excerpts] +[{NOW_Non-Roman_Alphabet_Other_Writer_Name]] +Information_for_Versions ::= VER_Original_Work_Title_for_Versions +[NVT_Non-Roman_Alphabet_Original_Title_for_Versions] +[{NOW_Non-Roman_Alphabet_Other_Writer_Name]] +Information_for_Components ::= COM_Component +[NET_Non-Roman_Alphabet_Title_for_Components] +[{NOW_Non-Roman_Alphabet_Other_Writer_Name]] +Note: that the BNF definitions for REV, EXC, and ISW are the same as for NWR. + +6.2 File skeleton sent from publisher to societies +This skeleton shows a combination of detail records that can be used in the various transactions. +HDR Transmission Header +GRH Group Header +AGR Agreement Transaction +TER Territory +IPA Assignor +IPA Acquirer +AGR Agreement Transaction +TER Territory +TER Territory +IPA Assignor +IPA Acquirer +IPA Acquirer +GRT Group Trailer +GRH Group Header +NWR New Work Registration Transaction +SPU Original Publisher +SPT Territory of Control +SPT Territory of Control +OPT Publisher non-controlled collection +OPT Publisher non-controlled collection +SPU Administrator +SPT Territory of Control +SPT Territory of Control +OPT Publisher non-controlled collection +OPT Publisher non-controlled collection +SPU Sub-publisher +SPT Territory of Control +SPT Territory of Control +OPT Publisher non-controlled collection +OPT Publisher non-controlled collection +OPU Other Publisher +OPT Publisher non-controlled collection +OPT Publisher non-controlled collection +SWR Writer +SWT Territory of Control +SWT Territory of Control +PWR Publisher for Writer +OWR Other Writer +OWT Other writer collection +OWT Other writer collection +PWR Publisher for Writer +ALT Alternate Title +EWT Entire Work Title for Excerpt +VER Original Work Title for Versions +PER Performing artist +PER Performing artist +REC Recording Detail +REC Recording Detail +ORN Work Origin +INS Instrumentation Summary +IND Instrumentation Detail +IND Instrumentation Detail +COM Component +COM Component +NWR New Work Registration Transaction +NWR New Work Registration Transaction +GRT Group Trailer +GRH Group Header +REV Revised work registration Transaction & detail records - as for +NWR +REV Revised work registration Transaction & detail records +GRT Group Trailer +TRL Transmission Trailer + +6.3 File skeleton sent from society to publisher +HDR Transmission Header +GRH Group Header +ACK Acknowledgement Transaction +MSG Message - precedes record of NWR/REV to which it refers + +--- Page 74 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 74 of 81 + + +AGR Agreement Information including detail records sent by publisher +- may have supplemental data +ACK Acknowledgement Transaction +AGR Agreement Information +…. +GRT Group Trailer +GRH Group Header +ACK Acknowledgement Transaction +MSG Message - precedes record of NWR/REV to which it refers +NWR Work registration including detail records sent by publisher - may +have supplemental data +EXC Notification of work in conflict (if any) +ACK Acknowledgement Transaction +MSG Message +NWR Work registration +… +GRT Group Trailer +GRH Group Header +ACK Acknowledgement Transaction +MSG Message - precedes record of NWR/REV to which it refers +REV Work registration including detail records sent by publisher - may +have supplemental data +EXC Notification of work in conflict (if any) +ACK Acknowledgement Transaction +MSG Message +REV Work registration +… +GRT Group Trailer +GRH Group Header +ISW ISWC Notification Transaction & detail records - as for NWR +ISW ISWC Notification Transaction & detail records +… +GRT Group Trailer +TRL Transmission Trailer + +Note: The groups are shown in one file in this skeleton, but it is possible to have only one group per file. +6.4 File skeleton containing Non-Roman Alphabet Records +This skeleton shows a sample of the records that can be used to register works containing non -Roman +alphabet data. +HDR Transmission Header +GRH Group Header +AGR Agreement Transaction +TER Territory +IPA Assignor +NPA Assignor Name in Non-Roman Alphabet +IPA Acquirer +AGR Agreement Transaction +TER Territory +TER Territory +IPA Assignor +IPA Acquirer + +--- Page 75 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 75 of 81 + + +NPA Acquirer Name in Non-Roman Alphabet +IPA Acquirer +NPA Acquirer Name in Non-Roman Alphabet +… +GRT Group Trailer +GRH Group Header +NWR New Work Registration Transaction +SPU Original Publisher +NPN Original Publisher Name in Non-Roman Alphabet +SPT Territory of Control +SPT Territory of Control +OPT Publisher non-controlled collection +OPT Publisher non-controlled collection +SPU Administrator +SPT Territory of Control +SPT Territory of Control +OPT Publisher non-controlled collection +OPT Publisher non-controlled collection +SPU Sub-publisher +SPT Territory of Control +SPT Territory of Control +OPT Publisher non-controlled collection +OPT Publisher non-controlled collection +OPU Other Publisher +OPT Publisher non-controlled collection +OPT Publisher non-controlled collection +SWR Writer +NWN Original Writer Name in Non-Roman Alphabet +SWT Territory of Control +SWR Territory of Control +PWR Publisher for Writer +PWR Publisher for Writer +OWR Other Writer +OWT Other writer collection +OWT Other writer collection +PWR Publisher for Writer +PWR Publisher for Writer +ALT Alternate Title +NAT Non-Roman Alphabet MainTitle +NAT Non-Roman Alphabet AlternateTitle +EWT Entire Work Title for Excerpt +NET Entire Work Title in Non-Roman Alphabet for Excerpt +NOW Other Writer Name in Non-Roman Alphabet for Excerpt +NOW Other Writer Name in Non-Roman Alphabet for Excerpt +NPR Performing artist in Non-Roman Alphabet +NPR Performing artist in Non-Roman Alphabet +INS Instrumentation Summary +IND Instrumentation Detail +IND Instrumentation Detail +NWR New Work Registration Transaction +… +GRT Group Trailer +TRL Transmission Trailer + +7 Society-Specific Edits + +--- Page 76 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 76 of 81 + + +The following section lists all of the society-specific edits that appear throughout this specification. +7.1 ABRAMUS and UBC +NWR Transaction Level Validation Rules 40 +40. For registrations to ABRAMUS and UBC only – all SPU records for final Sub -Publisher’s collecting +shares in the territory of Brazil must include the start date of the sub -publishing agreement in the +Society-assigned Agr eement Number field. The date should be left -justified in the format +YYYYMMDD, and the rest of the field should be left blank. Invalid dates will be rejected. (TR – +ABRAMUS and UBC only) + +7.2 ASCAP +NWR Transaction Level Validation Rules 28 & 29 +28. Edit Removed +29. Edit Removed +SPT Record Level Validation Rule 6 +6. For registrations to ASCAP only – The first SPT record immediately following an SPU must have the +‘Inclusion/Exclusion Indicator’ set to ‘I’. (TR – ASCAP only) +SWT Record Level Validation Rule 4 +4. For Registrations to ASCAP only - The first SWT record immediately following an SWR must have the +'Inclusion/Exclusion Indicator' set to 'I'. (TR - ASCAP only) +SPU Record Level Validation Rule 9, 13 &14 +9. For Registrations to ASCAP only – Where there is an ASCAP Original publisher there must be a +collection territory that includes the United States within that chain of title. (TR – ASCAP only) +13. For registration ASCAP only – If the original publisher belongs to ASCAP then the sub -publisher or +administrator in the chain for the US cannot belong to BMI or SESAC. (TR – ASCAP only) +14. For registration ASCAP only – If the original publisher belongs to BMI or SESAC then the sub-publisher +or administrator in the chain for the US cannot belong to ASCAP. (TR – ASCAP only) +7.3 BMI +NWR Field Level Validations Rule 21 +21. If Musical Work Distribution Category is equal to “JAZ” and BMI is represented on the work, duration +must be greater than zero (TR – BMI only) +7.4 GEMA +NWR Field Level Validation Rules 26, 27 & 28 +26. Edit Removed +27. Edit Removed +28. For registrations to GEMA only - If an ISWC number is entered and is part of the GEMA number block +then that number must already be registered by GEMA. (FR –GEMA only – Replace with spaces). + +--- Page 77 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 77 of 81 + + +SPU Field Level Validation Rules 33 & 34 +33. For registrations to GEMA o nly - If Agreement Type is equal to “PS”, the Submitter Agreement +Number must be entered and must match an entry in a corresponding AGR-record. (TR - GEMA only) +34. For registrations to GEMA only – If Record Type is equal to “SPU” and Publisher Type is equal to “SE”, +an Agreement Type must be entered. (TR – GEMA only). +NWR Transaction Level Validation Rules 30 & 31 +30. For registrations to GEMA only - A work transaction must contain at least one SPU with either “PR +Affiliation society” or “MR Affiliation society” set to 035 (GEMA), otherwise the work will be rejected +with the transaction status set to “NP” (TR – GEMA only). +31. For registrations to GEMA only – If all the Writer’s Last Names are entered as “DP” (i.e. Public +Domain), then the work will be rejected with Transaction Status “NP”. (TR – GEMA only). +NWR Field Level Validation Rules 26 & 27 +26. Edit Removed +27. Edit Removed +7.5 Harry Fox +NWR Transaction Level Validation Rule 32 +32. For registrations to Harry Fox only – A transaction must contain at least one SWR record (TR – Harry +Fox only). +7.6 ICE Societies +NWR Transaction Level Validation Rule XX and XX +1. For registrations to ICE Societies only – If writer designation code AR on work, a different writer's +designation code must be C or CA (TR – ICE only) +2. For registrations to ICE Societies only – If writer designation code SA on work, a different writer's +designation code must be A or CA (TR – ICE only) +SPU Transaction Level Validation Rule XX, XX, XX, XX and XX +1. For registrations to ICE Societies only – Agreement number missing on SPU (TR – ICE only) +2. For registrations to ICE Societies only – Agreement not found in ICE on quoted combination of +Submitter, Assignor and Agreement number on SPU on transaction (TR – ICE only) +3. For registrations to ICE Societies only – Agreement is terminated (TR – ICE only) +4. For registrations to ICE Societies only – Agreement number on SPU does not exist in ICE (TR – ICE +only) +5. For registrations to ICE Societies only – Claimed territory on transaction is not included on +publisher's agreement in ICE (TR – ICE only) +PWR Transaction Level Validation Rule XX, XX, XX, XX, XX and XX +1. For registrations to ICE Societies only – Agreement number missing on PWR (TR – ICE only) +2. For registrations to ICE Societies only – Agreement not found in ICE on quoted combination of +Submitter, Assignor and Agreement number on PWR on transaction (TR – ICE only) + +--- Page 78 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 78 of 81 + + +3. For registrations to ICE Societies only – Agreement is terminated (TR – ICE only) +4. For registrations to ICE Societies only – Agreement number on PWR does not exist in ICE (TR – ICE +only) +5. For registrations to ICE Societies only – Claimed territory on transaction is not included on +publisher's agreement in ICE (TR – ICE only) +6. For registrations to ICE Societies only – Original publisher on transaction does not own the quoted +agreement number (TR – ICE only) + +7.7 MusicMark +NWR Field Level Validations Rule nn +22. If SWR is BMI then any related publisher must be BMI or non-US PRO. If SWR is ASCAP then any related +publisher must be ASCAP or non-US PRO (TR- MusicMark only) +7.8 SACEM +NWR Transaction Level Validation Rule 41 +41. For registrations to SACEM only - A work transaction must contain at least one SPU with either “PR +Affiliation society” or “MR Affiliation society” set to 058 (SACEM), otherwise the work will be rejected +with the transaction status set to “NP”. (TR – SACEM only). +NWR Field Level Validation Rule 29 +29. For registrations to SACEM only - If an ISWC number is entered and is part of the SACEM number +block then that number must already be registered by SACEM. (FR – SACEM only – Replace with +spaces). +SPU Field Level Validation Rules 38 & 39 +38. For registrations to SACEM only – If Record Type is equal to “SPU” and Publisher Type is equal to +“SE”, an Agreement Type must be entered. All SPU records for final Sub -Publishers in the FR must +supply pre-notified Society-assigned Agreement Number. (TR – SACEM only). +39. For registrations to SACEM Societies only – If the publisher is a SACEM member and the Society - +Assigned Agreement Number is entered, it must match an agreement number on file with the SACEM +Society. (TR – SACEM only). +Note for rule 39 : The first 7 characters m ust be used for the Society Agreement Number linking the +Original Publisher to the Administrator. The last 7 characters must be used for the Society Agreement +Number linking the administrator to the Sub Publisher. (PG) +46. For registrations to SACEM only: The IPI-name-number provided for the Original Publisher SPU must +be equal to the assignor IPI -name-number for the agreement represented by the first 7 characters of +the Society Provided Agreement Number. +47. For registrations to SACEM only: The IPI-name-number provided for the Sub-Publisher SPU must be +equal to the assignee IPI -name-number for the agreement represented by the last 7 characters of the +Society Provided Agreement Number. + +SWR/OWR Field Level Validation Rule 31 + +--- Page 79 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 79 of 81 + + +31. For registrations to SACEM Societies only – If Record Type is OWR, the Writer Last Name must be +entered, or else the Writer will be ignored (RR – SACEM only). +7.9 SESAC +REC Transaction Level Validation Rule 13 +13. If the work registration contains a SESAC interest then Recording Format, Rec ording Technique, EP +Cassette EP CD Flag, Album CD Album Cassette Flag, Single Flag, and Twelve Inch Single Flag must be +entered. (TR – SESAC only) + +7.10 SGAE +NWR Transaction Level Validation Rule 35, 36, 37 & 38 +35. For registrations to SGAE only - All SPU records for Spanish sub -publishers must include a Society - +assigned Agreement Number, or a Specific agreement must already have been notified to SGAE (TR +– SGAE only) +36. For Registrations to SGAE only - For SGAE territories, the total Ownership shares of non -controlled +right-owners (OPUs and OWRs) and the Collection shares of controlled right-owners (SPTs and SWTs) +must equal 100% for each right. Note that a tolerance of plus or minus 00006 (0.06%) is allowed (TR +– SGAE only) +37. For Registrations to SGAE only - For SGAE territories, the total of PR Ownership shares of Non - +Controlled publishers (OPUs) and the PR Collection shares of controlled publishers (SPTs) must be +less or equal to 50%. Note that a tolerance of plus or minus 00006 (0.06%) is allowed (TR – SGAE +only) +38. NWR Transaction Level Validation Rule: For registrations to SGAE only – If all the Writers are Public +Domain, then the work will be rejected (TR – SGAE only) +39. Part of the agreements hierarchy missed. There is no agreements link registered (notified) between +original publisher and the submitter of the work (TR – SGAE only). +40. The sub-publisher of the work is not the registered (notified) for the original publisher (TR – SGAE +only). +41. The shares for the sub-publisher are different from the shares registered (notified) in the agreement +(TR – SGAE only). +SPU Record Level Validation Rules 11 & 12 +11. For registrations to SGAE only - SPU records for final Sub-Publishers with SGAE interest must include +a pre-notified Society-assigned Agreement number unless the Agreement Type field is set to “OS” or +“PS”. (TR – SGAE only) +12. For registrations to SGAE only - If the record is of SGAE interest then it must include an Agreement +Type. (TR – SGAE only) +SWR Field Level Validation Rules 27 & 28 +27. For Registrations to SGAE only – The Writer Unknown Indicator must not be set to “Y”. (TR – SGAE +only) +28. For Registrations to SGAE only – The Writer Last Name must not be set to “Unknown” or any other +name indicating the Writer is not known. (TR – SGAE only) + +--- Page 80 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 80 of 81 + + +7.11 SIAE +NWR Transaction Level Validation Rule 42 +3. For registration SIAE only – There must be at least one writer designation code of C or CA on a +transaction. (TR – SIAE only) + + +--- Page 81 --- + +Functional specifications: Common Works Registration Version 2.2 Revision 2 +CWR19-1070 Page 81 of 81 + + +8 Previous Revisions + +Number of +revision +Date Main modifications +2.2R2 09/2019 ➢ Update to transmission header record to account for IPI Name Numbers +(IPNN) greater than 9 digits. +➢ OPU validation updates. +➢ GRH record version number update. +➢ MSG record example removal. +➢ Addition of missing XREF record in Transaction Format table and file +skeletons. +➢ Update to XRF field description for Organisation Code. +2.2R1 04/2017 ➢ Correction of missing edit PWRF006 and renumbering the edits below. +2.2 05/2015 + + + + + + + + + + + + + + +04/2016 +➢ HDR: new fields for, version, revision, software package and package +release number +➢ SPU: IPI Name Numbers made mandatory for a submitter’s own IPI +Name Numbers +➢ PWR removed edit to allow PWR to follow OWR +➢ PWR to SPU Sequence Number link +➢ OPT New ‘non-controlled publisher collection’ record (optional) +➢ OWT new ‘other writer collection’ record (optional) +➢ REC New optional fields for Sound Recording Title, Sound Recording +version title, Record Label, Display Artist +➢ ORN removed previously invalid ISAN field and note relating to its use +➢ ORN New optional Field for ISAN and EIDR +➢ XRF new Optional Record +➢ Society specific edits agreed at the New York meeting added +➢ Information Services Committee (Lisbon, 14/04/2016) approves Version +2.2 + + \ No newline at end of file diff --git a/docs/source/_downloads/IS-CRFCRF-0020R7__CWR_validation_and_lookup_tables_2005_07_28_EN.doc b/docs/source/_downloads/IS-CRFCRF-0020R7__CWR_validation_and_lookup_tables_2005_07_28_EN.doc new file mode 100644 index 0000000..962c58d Binary files /dev/null and b/docs/source/_downloads/IS-CRFCRF-0020R7__CWR_validation_and_lookup_tables_2005_07_28_EN.doc differ diff --git a/docs/source/_downloads/ISTIS-0184a_TIS_database_full_data_-_Appendix_a_list_of_territories_EN.xlsx b/docs/source/_downloads/ISTIS-0184a_TIS_database_full_data_-_Appendix_a_list_of_territories_EN.xlsx new file mode 100644 index 0000000..1c37e64 Binary files /dev/null and b/docs/source/_downloads/ISTIS-0184a_TIS_database_full_data_-_Appendix_a_list_of_territories_EN.xlsx differ diff --git a/docs/source/_downloads/MLC CWR User Guide.pdf b/docs/source/_downloads/MLC CWR User Guide.pdf new file mode 100644 index 0000000..cb698eb Binary files /dev/null and b/docs/source/_downloads/MLC CWR User Guide.pdf differ diff --git a/docs/source/_downloads/MusicMark-CWR getting-started.pdf b/docs/source/_downloads/MusicMark-CWR getting-started.pdf new file mode 100644 index 0000000..676db45 Binary files /dev/null and b/docs/source/_downloads/MusicMark-CWR getting-started.pdf differ diff --git a/docs/source/_downloads/SG25-0580_CISAC_societies_codes_listing_2025-12-08_EN.xlsx b/docs/source/_downloads/SG25-0580_CISAC_societies_codes_listing_2025-12-08_EN.xlsx new file mode 100644 index 0000000..86f854c Binary files /dev/null and b/docs/source/_downloads/SG25-0580_CISAC_societies_codes_listing_2025-12-08_EN.xlsx differ diff --git a/docs/source/_downloads/SR06-1311_Standards-And_Rules_Working_Group_CIS_Character_Set_EN.doc b/docs/source/_downloads/SR06-1311_Standards-And_Rules_Working_Group_CIS_Character_Set_EN.doc new file mode 100644 index 0000000..149e402 Binary files /dev/null and b/docs/source/_downloads/SR06-1311_Standards-And_Rules_Working_Group_CIS_Character_Set_EN.doc differ diff --git a/docs/source/_downloads/TIS09-1540a_Territories_2009-08-27_EN.xls b/docs/source/_downloads/TIS09-1540a_Territories_2009-08-27_EN.xls new file mode 100644 index 0000000..e8c5b46 Binary files /dev/null and b/docs/source/_downloads/TIS09-1540a_Territories_2009-08-27_EN.xls differ diff --git a/docs/source/_downloads/TIS09-1540c_Hierarchies_2009-08-27_EN.xls b/docs/source/_downloads/TIS09-1540c_Hierarchies_2009-08-27_EN.xls new file mode 100644 index 0000000..bae49f4 Binary files /dev/null and b/docs/source/_downloads/TIS09-1540c_Hierarchies_2009-08-27_EN.xls differ diff --git a/docs/source/_downloads/TIS09-1546R1_Territory_Information_System_2012-01-20_EN.pdf b/docs/source/_downloads/TIS09-1546R1_Territory_Information_System_2012-01-20_EN.pdf new file mode 100644 index 0000000..69e6ee2 Binary files /dev/null and b/docs/source/_downloads/TIS09-1546R1_Territory_Information_System_2012-01-20_EN.pdf differ diff --git a/docs/source/_downloads/archive/.DS_Store b/docs/source/_downloads/archive/.DS_Store new file mode 100644 index 0000000..18d5303 Binary files /dev/null and b/docs/source/_downloads/archive/.DS_Store differ diff --git a/docs/source/_downloads/archive/CWR06-1950_CWR_Implementation_spreadsheet_2014-06-23_EN.pdf b/docs/source/_downloads/archive/CWR06-1950_CWR_Implementation_spreadsheet_2014-06-23_EN.pdf new file mode 100644 index 0000000..dfb32f7 Binary files /dev/null and b/docs/source/_downloads/archive/CWR06-1950_CWR_Implementation_spreadsheet_2014-06-23_EN.pdf differ diff --git a/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(August_2025)_2025-08-08_EN.xlsx b/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(August_2025)_2025-08-08_EN.xlsx new file mode 100644 index 0000000..35a48e1 Binary files /dev/null and b/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(August_2025)_2025-08-08_EN.xlsx differ diff --git a/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(December_2025)_2025-12-08_EN.xlsx b/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(December_2025)_2025-12-08_EN.xlsx new file mode 100644 index 0000000..983aa4b Binary files /dev/null and b/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(December_2025)_2025-12-08_EN.xlsx differ diff --git a/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(December_2025)_2025-12-22_EN.xlsx b/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(December_2025)_2025-12-22_EN.xlsx new file mode 100644 index 0000000..33d1f60 Binary files /dev/null and b/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(December_2025)_2025-12-22_EN.xlsx differ diff --git a/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(February_2026)_2026-02-20_EN.xlsx b/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(February_2026)_2026-02-20_EN.xlsx new file mode 100644 index 0000000..0ec68a4 Binary files /dev/null and b/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(February_2026)_2026-02-20_EN.xlsx differ diff --git a/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(January_2026)_2026-01-09_EN.xlsx b/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(January_2026)_2026-01-09_EN.xlsx new file mode 100644 index 0000000..be3b202 Binary files /dev/null and b/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(January_2026)_2026-01-09_EN.xlsx differ diff --git a/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(March_2026)_2026-03-20_EN.xlsx b/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(March_2026)_2026-03-20_EN.xlsx new file mode 100644 index 0000000..18e05e2 Binary files /dev/null and b/docs/source/_downloads/archive/CWR06-1972_CWR_sender_ID_and_codes_(March_2026)_2026-03-20_EN.xlsx differ diff --git a/docs/source/_downloads/archive/CWR06-1972_Specifications_Overview_CWR_sender_ID_and_Codes_2025-09-04_EN.xlsx b/docs/source/_downloads/archive/CWR06-1972_Specifications_Overview_CWR_sender_ID_and_Codes_2025-09-04_EN.xlsx new file mode 100644 index 0000000..065afb6 Binary files /dev/null and b/docs/source/_downloads/archive/CWR06-1972_Specifications_Overview_CWR_sender_ID_and_Codes_2025-09-04_EN.xlsx differ diff --git a/docs/source/_downloads/archive/CWR06-1972_Specifications_Overview_CWR_sender_ID_and_codes_2014-12-04_EN.xlsx b/docs/source/_downloads/archive/CWR06-1972_Specifications_Overview_CWR_sender_ID_and_codes_2014-12-04_EN.xlsx new file mode 100644 index 0000000..3ba94c7 Binary files /dev/null and b/docs/source/_downloads/archive/CWR06-1972_Specifications_Overview_CWR_sender_ID_and_codes_2014-12-04_EN.xlsx differ diff --git a/docs/source/_downloads/archive/CWR11-1494_CWR_User_Manual_2011-09-23_E_2011-09-23_EN.pdf b/docs/source/_downloads/archive/CWR11-1494_CWR_User_Manual_2011-09-23_E_2011-09-23_EN.pdf new file mode 100644 index 0000000..ba37adc Binary files /dev/null and b/docs/source/_downloads/archive/CWR11-1494_CWR_User_Manual_2011-09-23_E_2011-09-23_EN.pdf differ diff --git a/docs/source/_downloads/archive/CWR11-1991R1_Functional_specifications_CWR_version_2-1_Rev7_2013-11-02_EN.pdf b/docs/source/_downloads/archive/CWR11-1991R1_Functional_specifications_CWR_version_2-1_Rev7_2013-11-02_EN.pdf new file mode 100644 index 0000000..73c5181 Binary files /dev/null and b/docs/source/_downloads/archive/CWR11-1991R1_Functional_specifications_CWR_version_2-1_Rev7_2013-11-02_EN.pdf differ diff --git a/docs/source/_downloads/archive/society_code.tsv b/docs/source/_downloads/archive/society_code.tsv new file mode 100644 index 0000000..bac40a1 --- /dev/null +++ b/docs/source/_downloads/archive/society_code.tsv @@ -0,0 +1,247 @@ +Society Code Code Country +DP 0 Public Domain +ACUM 1 Israel +ADDAF 2 Brazil +AEPI 3 Greece +AGADU 4 Uruguay +AKM 5 Austria +BUCUDA 6 Central Afr Rep +APDAYC 7 Peru +APRA 8 Australia +ARTISJUS 9 Hungary +ASCAP 10 USA +AUSTRO-MECHANA 11 Austria +AMCOS 12 Australia +AWA 13 German Dem Rep +ARGENTORES 14 Argentina +APA 15 Paraguay +BUMDA 16 Mali +AMRA 17 USA +BGDA 18 Guinea +BMDA 19 Morocco +SODRAC 20 Canada +BMI 21 USA +MCSN 22 Nigeria +BUMA 23 Netherlands +BURIDA 24 Ivory Coast +BSDA 25 Senegal +CASH 26 Hong Kong +CAPAC 27 Canada +LITA 28 Slovakia +SCD 29 Chile +AMAR 30 Brazil +DILIA 31 Czech Republic +FILSCAP 32 Philippines +OMDA 33 Madagascar +HARRY FOX AGENCY 34 USA +GEMA 35 German Fed Rep +IPRS 36 India +BUBEDRA 37 Benin +JASRAC 38 Japan +MUSICAUTOR 39 Bulgaria +KODA 40 Denmark +LITERAR-MECHANA 41 Austria +LVG 42 Austria +MCSK 43 Kenya +MCPS 44 United Kingdom +BBDA 45 Burkina Faso +MRS 46 United Kingdom +BCDA 47 Congo +NCB 48 Scandinavia +ONDA 49 Algeria +OSA 50 Czech Republic +PROLITTERIS 51 Switzerland +PRS 52 United Kingdom +PROCAN 53 Canada +ALCS 54 United Kingdom +SABAM 55 Belgium +SACD 56 France +SACERAU 57 Egypt +SACEM 58 France +SACM 59 Mexico +SACVEN 60 Venezuela +SADAIC 61 Argentina +SADEMBRA 62 Brazil +SAMRO 63 South Africa +SOKOJ 64 Yugoslavia +SAYCE 65 Ecuador +SBACEM 66 Brazil +SBAT 67 Brazil +SDRM 68 France +SPA 69 Portugal +SOGEM 70 Mexico +SESAC 71 USA +SGAE 72 Spain +SCAM 73 France +SIAE 74 Italy +SUISSIMAGE 75 Switzerland +ACEMLA 76 Puerto Rico +STEF 77 Iceland +STEMRA 78 Netherlands +STIM 79 Sweden +SUISA 80 Switzerland +SARRAL 81 South Africa +OTPDA 82 Tunisia +SONECA 83 Zaire +SAYCO 84 Columbia +SOZA 85 Slovakia +SICAM 86 Brazil +SPACEMF 87 French Polynesia +CMRRA 88 Canada +TEOSTO 89 Finland +TONO 90 Norway +SSA 91 Switzerland +SOCINADA 92 Cameroon Rep +UBC 93 Brazil +RAO 94 Russia +VG WORT 95 German +COTT 96 Trinidad & Tobago +ZAIKS 97 Poland +ZIMRA 98 Zimbabwe +NS 99 +SOCAN 101 Canada +NASCAM 102 Namibia +ACDAM 103 Cuba +MACP 104 Malaysia +MASA 105 Mauritius +COMPASS 106 Singapore +ACAM 107 Costa Rica +CHA 108 Taiwan +KCI 109 Indonesia +LATGA-A 110 Lithuania +HDS-ZAMP 111 Croatia +SAZAS 112 Slovenia +LAA 113 Latvia +AGAYC 114 Guatemala +UCMR-ADA 115 Romania +EAU 116 Estonia +MESAM 117 Turkey +KOMCA 118 South Korea +MCSC 119 China +LIRA 120 Netherlands +VDFS 121 Austria +AKKA/LAA 122 Latvia +COSGA 123 Ghana +COSOMA 124 Malawi +BNDA 125 Niger +MCT 126 Thailand +ALBAUTOR 127 Albania +IMRO 128 Ireland +SOBODAYCOM 129 Bolivia +BUTODRA 130 Togo +SADA 131 Greece +BILD-KUNST 132 German Federal Republic +ZAMCOPS 133 Zambia +SLPRS 134 Sri Lanka +SADH 135 Greece +ZAMP 136 Macedonia +SOFAM 137 Belgium +KOPIOSTO 138 Finland +COPY-DAN BILLEDKUNST 139 Denmark +UACRR 140 Ukraine +ATN 141 Chile +DALRO 142 South Africa +TEATERAUTOR 143 Bulgaria +HAA 144 Croatia +DPRS 145 United Kingdom +SPAC 146 Panama +FILMAUTOR 147 Bulgaria +ADAGP 148 France +ARS 149 USA +BEELDRECHT 150 Netherlands +BONO 151 Norway +BUS 152 Sweden +DACS 153 United Kingdom +HUNGART 154 Hungary +SOMAAP 155 Mexico +VAGA 156 USA +VBK 157 Austria +VEGAP 158 Spain +VISCOPY 159 Australia +RUPIS 160 Belarus +MUST 161 Taiwan (Province Of China) +AMPAL 162 Australia +APG-JAPAN 163 Japan +APSAV 164 Peru +ATN 165 Chile +AUTORARTE 166 Venezuela +BURAFO 167 Netherlands +CAL 168 Australia +COSCAP 169 Barbados +CPSN 170 Nepal +CREAIMAGEN 171 Chile +DGA 172 United States +DIRECTORES 173 Mexico +FLIM JUS 174 Hungary +COPYRO 175 Romania +JACAP 176 Jamaica +KAZAK 177 Kazakhstan +KOSA 178 Korea Republic Of +KUVASTO 179 Finland +MUSIKEDITION 180 Austria +NMPA 181 United States +PAPPRI 182 Indonesia +SACK 183 Korea Republic Of +SARTEC 184 Canada +SESAM 185 France +SGDL 186 France +SNAC 187 France +SOCIETE DE L’IMAGE 188 France +SOCINPRO 189 Brazil +SOPE 190 Greece +SPACQ 191 Canada +SFF 192 Sweden +THE SOCIETY OF AUTHORS 193 United Kingdom +UFFICIO LEGALE 194 Holy See (Vatican City State) +VEVAM 195 Netherlands +WGA 196 United States +WGJ 197 Japan +ZAMP 198 Slovenia +ZAPA 199 Poland +MSG 200 Turkey +ABRAMUS 201 Brazil +ASDAC 202 Moldova - Republic Of +AWGACS 203 Australia +SAS 204 Georgia +SODART 205 Canada +SUOMEN KIRJAILIJALIITTO 206 Finland +THE AUTHOR'S REGISTRY INC. 207 United States +SGA 208 Guinea-Bissau +ARMAUTHOR 209 Armenia +ACCESS 210 Canada (Formerly CANCOPY) + 211 No Longer In Use +CSCS 212 Canada +DRCC 213 Canada +HMS 214 Saint Lucia +KYRGYZPATENT 215 Kyrgyzstan +SQN 216 Bosnia And Herzegovina +ABRAC 217 Brazil +ANACIM 218 Brazil +ASSIM 219 Brazil +ATIDA 220 Brazil +SABEM 221 Brazil +FONOPERU 222 Peru +COSOTA 223 Tanzania, United Republic Of +SOMAS 224 Mozambique +SAIF 225 France +AACIMH 226 Honduras +SGACEDOM 227 Dominican Republic +ROMS 228 Russian Federation +ICG 229 United States +ADAVIS 230 Cuba +AUTVIS 231 Brazil +GESTOR 232 Czech Republic +SACEMLUXEMBOURG 233 Luxembourg +UCOSO 234 Uganda +SACENC 235 France +WID CENTRE 300 United States +GESAC 301 Belgium +LATINAUTOR 302 Uruguay +NORD-DOC 303 Sweden +SONGCODE 304 United States +IMJV 305 Netherlands +CCL 306 Trinidad And Tobago +MISASIA 307 Singapore +ECAD 308 Brazil +LATINNET 309 Spain +DIVA 310 Hong Kong diff --git a/docs/source/_downloads/archive/writer_role.tsv b/docs/source/_downloads/archive/writer_role.tsv new file mode 100644 index 0000000..eec6197 --- /dev/null +++ b/docs/source/_downloads/archive/writer_role.tsv @@ -0,0 +1,11 @@ +Role Writer Designation Code + +Adaptor AD +Arranger AR +Author A +Composer C +Composer/ Author CA +Sub Arranger SR +Sub Author SA +Translator TR +Income Participant PA \ No newline at end of file diff --git a/docs/source/_downloads/cwr_files/charset_rules.rar b/docs/source/_downloads/cwr_files/charset_rules.rar deleted file mode 100644 index e789bf4..0000000 Binary files a/docs/source/_downloads/cwr_files/charset_rules.rar and /dev/null differ diff --git a/docs/source/_downloads/cwr_files/cwr_light.rar b/docs/source/_downloads/cwr_files/cwr_light.rar deleted file mode 100644 index 1c04fe8..0000000 Binary files a/docs/source/_downloads/cwr_files/cwr_light.rar and /dev/null differ diff --git a/docs/source/_downloads/cwr_files/errors.rar b/docs/source/_downloads/cwr_files/errors.rar deleted file mode 100644 index 1a1bdf5..0000000 Binary files a/docs/source/_downloads/cwr_files/errors.rar and /dev/null differ diff --git a/docs/source/_downloads/cwr_files/impl_sheet.rar b/docs/source/_downloads/cwr_files/impl_sheet.rar deleted file mode 100644 index 6fe8a05..0000000 Binary files a/docs/source/_downloads/cwr_files/impl_sheet.rar and /dev/null differ diff --git a/docs/source/_downloads/cwr_files/questionnary_publisher.rar b/docs/source/_downloads/cwr_files/questionnary_publisher.rar deleted file mode 100644 index 6753e40..0000000 Binary files a/docs/source/_downloads/cwr_files/questionnary_publisher.rar and /dev/null differ diff --git a/docs/source/_downloads/cwr_files/questionnary_society.rar b/docs/source/_downloads/cwr_files/questionnary_society.rar deleted file mode 100644 index d574f28..0000000 Binary files a/docs/source/_downloads/cwr_files/questionnary_society.rar and /dev/null differ diff --git a/docs/source/_downloads/cwr_files/sender_id_code.rar b/docs/source/_downloads/cwr_files/sender_id_code.rar deleted file mode 100644 index 01ce6b9..0000000 Binary files a/docs/source/_downloads/cwr_files/sender_id_code.rar and /dev/null differ diff --git a/docs/source/_downloads/cwr_files/specification.rar b/docs/source/_downloads/cwr_files/specification.rar deleted file mode 100644 index 4478400..0000000 Binary files a/docs/source/_downloads/cwr_files/specification.rar and /dev/null differ diff --git a/docs/source/_downloads/cwr_files/tables.rar b/docs/source/_downloads/cwr_files/tables.rar deleted file mode 100644 index b78a605..0000000 Binary files a/docs/source/_downloads/cwr_files/tables.rar and /dev/null differ diff --git a/docs/source/_downloads/cwr_files/tis_amend.rar b/docs/source/_downloads/cwr_files/tis_amend.rar deleted file mode 100644 index 9bc808b..0000000 Binary files a/docs/source/_downloads/cwr_files/tis_amend.rar and /dev/null differ diff --git a/docs/source/_downloads/cwr_files/tis_hierarchies.rar b/docs/source/_downloads/cwr_files/tis_hierarchies.rar deleted file mode 100644 index 388f6c4..0000000 Binary files a/docs/source/_downloads/cwr_files/tis_hierarchies.rar and /dev/null differ diff --git a/docs/source/_downloads/cwr_files/tis_territories.rar b/docs/source/_downloads/cwr_files/tis_territories.rar deleted file mode 100644 index f377540..0000000 Binary files a/docs/source/_downloads/cwr_files/tis_territories.rar and /dev/null differ diff --git a/docs/source/_downloads/cwr_files/user_manual.rar b/docs/source/_downloads/cwr_files/user_manual.rar deleted file mode 100644 index cd6690e..0000000 Binary files a/docs/source/_downloads/cwr_files/user_manual.rar and /dev/null differ diff --git a/docs/source/_static/.DS_Store b/docs/source/_static/.DS_Store new file mode 100644 index 0000000..e909696 Binary files /dev/null and b/docs/source/_static/.DS_Store differ diff --git a/explain.txt b/explain.txt new file mode 100644 index 0000000..1b85a5e --- /dev/null +++ b/explain.txt @@ -0,0 +1,38 @@ +CWR Format: A Standard with Variations +The Common Works Registration (CWR) format is a globally recognized standard for the electronic registration of musical works. It was developed by the International Confederation of Societies of Authors and Composers (CISAC) to facilitate the automated exchange of musical work information between collective management organizations (CMOs), publishers, and other rights holders. The purpose of this standard is to ensure all parties are providing and receiving data in a consistent and machine-readable format. + +CWR Format Standardization +While CWR is a standard, it is not universally implemented identically. The CISAC standard defines a set of record types and data fields (e.g., HDR for Header, NWR for New Work Registration, TRL for Trailer) and their required lengths and content types. + +Variations exist in the specific version of the standard adopted by different societies (e.g., CWR v2.1 vs. v2.2) and the custom validation rules each society applies to incoming files. Therefore, a CWR file that is valid for one society may be rejected by another due to these society-specific requirements. + +Territorial Information in CWR +The CWR format explicitly includes fields for specifying territorial rights. This data is not an external add-on; it is an integrated part of the file structure. + +Publisher Territory of Control (SPT): This record type is used to specify the territories where a publisher controls the rights for a work. + +Writer Territory of Control (SWT): This record type serves the same purpose as SPT but for writers and their share of the rights. + +Group of Territories: The standard also allows for the specification of a group of territories (e.g., "North America") through a single line item, provided the specific group is defined in the CISAC standards. + +These records allow rights holders to define granular ownership splits on a territory-by-territory basis within a single registration file. + +Implementation Variations +The following examples illustrate how different societies implement and validate the CWR standard, which is critical for understanding its real-world application. + +Accepted Versions: A society may only accept a specific version of the CWR standard, for example, v2.1 or v2.2, while a newer version (e.g., v3.1) is being developed or is pending adoption. + +File Naming Conventions: Some societies enforce specific file naming conventions that are not part of the core CWR standard itself. An example is the required format CWYYXXXXTST_000.V21, which includes a specific submitter code and a sequence number. + +Share Totals: Societies may have unique validation rules for royalty splits. For instance, one society might require the total ownership splits to be 100% plus or minus 0.06% to account for rounding errors. + +Common Validation Rules +Beyond the core format, societies validate CWR files for common data errors. An AI program should be trained to recognize and avoid the following common issues: + +Missing IPI Numbers: Incorrect or missing IPI (Interested Party Information) numbers for writers or publishers. + +Incorrect Splits: Ownership splits for a work that do not add up to 100%. + +Duplicate Filenames: Submitting a new version of a file without changing its unique identifier. + +Using Stage Names: Registering a work under a stage name without also providing the associated legal name. \ No newline at end of file diff --git a/record_types.tsv b/record_types.tsv new file mode 100644 index 0000000..70bdecb --- /dev/null +++ b/record_types.tsv @@ -0,0 +1,13 @@ +Record Type Record Name Function / Description +HDR Transmission Header File-level header, identifies the sender and CWR version. +TRL Transmission Trailer File-level trailer, provides a total count of groups, works, and lines for validation. +GRH Group Header Indicates the start of a group of transactions of a single type. +NWR New Work Registration Initiates a new work registration transaction. +REV Revised Registration Initiates a revised work registration transaction. +SPU Publisher Controlled by Submitter Identifies a publisher controlled by the submitting party with ownership shares. +SPT Publisher Territory of Control Specifies collected shares for a publisher in a given territory. +SWR Writer Controlled by Submitter Identifies a writer controlled by the submitting party with ownership shares. +SWT Writer Territory of Control Specifies collected shares for a writer in a given territory. +OPU Other Publisher Identifies an uncontrolled publisher. +OWR Other Writer Identifies an uncontrolled writer. +PWR Publisher for Writer Links a controlled writer to their controlling publisher. \ No newline at end of file diff --git a/tests/.DS_Store b/tests/.DS_Store new file mode 100644 index 0000000..a94be62 Binary files /dev/null and b/tests/.DS_Store differ diff --git a/tests/examples/demo_cwr_cleaned.v22 b/tests/examples/demo_cwr_cleaned.v22 new file mode 100644 index 0000000..f0dc6ba --- /dev/null +++ b/tests/examples/demo_cwr_cleaned.v22 @@ -0,0 +1,93 @@ +HDRPB000000DP1TOTALLY MADE UP PUBLISHING 01.102025051319184420250513 2.2001CURVE ROYALTY SYSTEMS +GRHREV0000102.200000000002 +NWR0000000000000000MIDNIGHT SERENADE KEY001T012345678900000000 POP000000N ORI ORINON N +SPU000000000000000101P00000001CROWN PUBLISHING E 00000000000854632549 052050000441000004410000 N +SPT0000000000000002P00000001 050001000010000I2136N001 +SWR0000000000000003C00000001SMITH JOHN CA 00856545879052050000520000005200000 N +SWT0000000000000004C00000001050000000000000I2136N001 +PWR0000000000000005P00000001CROWN PUBLISHING C0000000101 +NWR0000000100000000ECHOES OF TOMORROW KEY002T012345678900000000 POP000000N ORI ORINON N +SPU000000010000000101P00000001CROWN PUBLISHING E 00000000000854632549 052050000441000004410000 N +SPT0000000100000002P00000001 050001000010000I2136N001 +SWR0000000100000003C00000001SMITH JOHN CA 00856545879052025000520000005200000 N +SWT0000000100000004C00000001025000000000000I2136N001 +PWR0000000100000005P00000001CROWN PUBLISHING C0000000101 +SWR0000000100000006C00000004JOHNSON SARAH CA 00856545876128025001280000012800000 N +SWT0000000100000007C00000004025000000000000I2136N001 +PWR0000000100000008P00000001CROWN PUBLISHING C0000000401 +XRF0000000100000009052123456BR WY +XRF0000000100000010055A35G45A1 WY +XRF000000010000001008912345678 WN +REV0000000200000000MIDNIGHT SERENADE KEY003 00000000 POP000000N ORI ORINON N +SPU000000020000000101P00000001CROWN PUBLISHING E 00000000000854632549 052025000440500004405000 N +SPT0000000200000002P00000001 025000500005000I2136N001 +OPU000000020000000302P00000002HOPS PUBLISHING E 00000000000854632548 055012500550250005502500 N +OPU000000020000000403P00000004LIBERTY PUBLISHING E 00000000000854632546 021012507080250002102500 N +SWR0000000200000005C00000001SMITH JOHN CA 00856545879052025000520000005200000 N +SWT0000000200000006C00000001025000000000000I2136N001 +PWR0000000200000007P00000001CROWN PUBLISHING C0000000101 +OWR0000000200000008C00000004JOHNSON SARAH CA 00856545876128012501280000012800000 N +OWR0000000200000009C00000005WHITE EMILY CA 00856545875008012500080250000802500 N +REV0000000300000000WHISPERING WINDS KEY004 00000000 POP000000N ORI ORINON N +SPU000000030000000101P00000001CROWN PUBLISHING E 00000000000854632549 052050000441000004410000 N +SPU000000030000000201P00000003TULIP PUBLISHING SE00000000000854632547 023000000780000007800000 N +SPT0000000300000003P00000003 050001000010000I2136N001 +SWR0000000300000004C00000001SMITH JOHN CA 00856545879052050000520000005200000 N +SWT0000000300000005C00000001050000000000000I2136N001 +PWR0000000300000006P00000001CROWN PUBLISHING C0000000101 +ACK0000000000000000202506201239380000100000000REVCRIMSON TIDE KEY005B 795145CV 20250620AS +MSG0000000000000001F00000000MSGI006Submitter work number for revision work does not exist in BMI.: Possible submitter ids = '[BMI:2000000001]' +REV0000000400000000GOLDEN HORIZON KEY005B 00000000 POP000000N ORI ORINON N +SPU000000040000000101P00000001CROWN PUBLISHING E 00000000000854632549 052050000441000004410000 N +SPT0000000400000002P00000001 050001000010000I2136N001 +SPT0000000400000003P00000001 000000000000000E0056N002 +SPU000000040000000401P00000002HOPS PUBLISHING SE00000000000854632548 055000000550000005500000 N +SPT0000000400000005P00000002 050001000010000I0056N001 +SWR0000000400000006C00000001SMITH JOHN CA 00856545879052050000520000005200000 N +SWT0000000400000007C00000001050000000000000I2136N001 +PWR0000000400000008P00000001CROWN PUBLISHING C0000000101 +REV0000000500000000FORGOTTEN MELODY KEY006 00000000 POP000000N ORI ORINON N +SPU000000050000000101P00000001CROWN PUBLISHING E 00000000000854632549 052050000441000004410000 N +SPU000000050000000201P00000002HOPS PUBLISHING SE00000000000854632548 055000000550000005500000 N +SPT0000000500000003P00000002 050001000010000I2136N001 +SPU000000050000000401P00000003TULIP PUBLISHING SE00000000000854632547 023000000780000007800000 N +SPT0000000500000005P00000003 050001000010000I0528N001 +SWR0000000500000006C00000001SMITH JOHN CA 00856545879052050000520000005200000 N +SWT0000000500000007C00000001050000000000000I0056N001 +SWT0000000500000008C00000001050000000000000I0528N002 +PWR0000000500000009P00000001CROWN PUBLISHING C0000000101 +REV0000000600000000STARLIGHT SYMPHONY KEY007 00000000 POP000000N ORI ORINON N +SPU000000060000000101P00000001CROWN PUBLISHING E 00000000000854632549 052025000440500004405000 N +SPU000000060000000201P00000002HOPS PUBLISHING SE00000000000854632548 055000000550000005500000 N +SPT0000000600000003P00000002 025000500005000I2136N001 +SPU000000060000000402P00000001CROWN PUBLISHING E 00000000000854632549 052025000440500004405000 N +SPU000000060000000502P00000006ROCHEFORT PUBLISHING SE00000000000000000000 00000 00000 00000 N +SPT0000000600000006P00000006 025000500005000I2136N001 +SWR0000000600000007C00000001SMITH JOHN CA 00856545879052050000520000005200000 N +SWT0000000600000008C00000001050000000000000I2136N001 +PWR0000000600000009P00000001CROWN PUBLISHING C0000000101 +NWR0000000700000000URBAN PULSE KEY008 00000000 POP000000N ORI ORINON N +SPU000000070000000101P00000001CROWN PUBLISHING E 00000000000854632549 052025000440500004405000 N +SPU000000070000000201P00000002HOPS PUBLISHING SE00000000000854632548 055000000550000005500000 N +SPT0000000700000003P00000002 025000500005000I2136N001 +SPU000000070000000402P00000005MAISON PUBLISHING E 00000000000854632545 058025000580500005805000 N +SPU000000070000000502P00000002HOPS PUBLISHING SE00000000000854632548 055000000550000005500000 N +SPT0000000700000006P00000002 025000500005000I2136N001 +SWR0000000700000007C00000001SMITH JOHN CA 00856545879052025000520000005200000 N +SWT0000000700000008C00000001025000000000000I2136N001 +PWR0000000700000009P00000001CROWN PUBLISHING C0000000101 +SWR0000000700000010C00000005WHITE EMILY CA 00856545875008025000080000000800000 N +SWT0000000700000011C00000005025000000000000I2136N001 +PWR0000000700000012P00000005MAISON PUBLISHING C0000000502 +REV0000000800000000SILENT GUARDIAN KEY009 00000000 POP000000N ORI ORINON N +SPU000000080000000101P00000001CROWN PUBLISHING E 00000000000854632549 052025000440500004405000 N +SPT0000000800000002P00000001 025000500005000I2136N001 +SPU000000080000000302P00000004LIBERTY PUBLISHING E 00000000000854632546 021025007080500002105000 N +SPU000000080000000402P00000001CROWN PUBLISHING SE00000000000854632549 052000000440000004400000 N +SPT0000000800000005P00000001 025000500005000I2136N001 +SWR0000000800000006C00000001SMITH JOHN CA 00856545879052050000520000005200000 N +SWT0000000800000007C00000001050000000000000I2136N001 +PWR0000000800000008P00000001CROWN PUBLISHING C0000000101 +PWR0000000800000009P00000004LIBERTY PUBLISHING C0000000102 +GRT000010000003900000720 +TRL000010000003900000722 diff --git a/tests/examples/nwrexample2.V21 b/tests/examples/nwrexample2.V21 new file mode 100644 index 0000000..c771f1a --- /dev/null +++ b/tests/examples/nwrexample2.V21 @@ -0,0 +1,12 @@ +HDRPB000000199THE SENDER 01.102018032210203720180322 +GRHNWR0000102.100000000000 +NWR0000000000000000THE WORK CLAIMDIGITAL01 00000000 POP000000Y ORI MRS. SMITH N00000000000 +SPU000000000000000101HCJ3EBJT6THE PUBLISHER E 00000000000000000297 0100250003405000 05000 N +SPU000000000000000201ILE7GIQMJTHE SENDER AM00000000000000000199 0100000003400000 00000 N +SPT0000000000000003ILE7GIQMJ 025000500005000I2136N001 +SWR00000000000000042RDRB3FHXDOE JOHN CA0000000000000000039501002500 00000 00000 N +SWT00000000000000052RDRB3FHX025000000000000I2136N001 +PWR0000000000000006HCJ3EBJT6THE PUBLISHER 2RDRB3FHX +OWR0000000000000007JZL2GMGV3DOE JANE CA00000000000000000000 05000 05000 05000 N +GRT000010000000100000010 0000000000 +TRL000010000000100000012 \ No newline at end of file diff --git a/tests/examples/revexample.V21 b/tests/examples/revexample.V21 new file mode 100644 index 0000000..780c66d --- /dev/null +++ b/tests/examples/revexample.V21 @@ -0,0 +1,25 @@ +HDRPB000000199DMP DEMO PUBLISHING 01.102019021516052620190215 +GRHREV0000102.100000000000 +REV0000000000000000THE ONE DMP000001 00000000 UNC000000Y ORI N00000000000 N +SPU000000000000000101DMP DMP DEMO PUBLISHING E 00000000000000000199 052050000441000004410000 N +SPT0000000000000002DMP 050001000010000I2136N001 +SWR0000000000000003W000001 SMITH JOHN JAMES CA0000000000000000039521 05000 00000 00000 N +SWT0000000000000004W000001 050000000000000I2136N001 +PWR0000000000000005DMP DMP DEMO PUBLISHING SAAN12345 W000001 +ALT0000000000000006THE ONE BED AT +ALT0000000000000007THE ONE DRUMS ONLY AT +ALT0000000000000008THE ONE NO DRUMS AT +ALT0000000000000009THE ONE STING AT +PER0000000000000010THE BAND +REC000000000000001100000000 000000 DML +ORN0000000000000012LIB INTERNET 0000DMP DEMO LIBRARY 0000 +REV0000000100000000SECOND BEST DMP000002 00000000 UNC000000U ORI N00000000000 N +SPU000000010000000101DMP DMP DEMO PUBLISHING E 00000000000000000199 052025000440500004405000 N +SPT0000000100000002DMP 025000500005000I2136N001 +SWR0000000100000003W000001 SMITH JOHN JAMES CA0000000000000000039521 02500 00000 00000 N +SWT0000000100000004W000001 025000000000000I2136N001 +PWR0000000100000005DMP DMP DEMO PUBLISHING SAAN12345 W000001 +OWR0000000100000006W000003 ADAMS AARON CA00000000000000000000 05000 05000 05000 +ALT0000000100000007SECOND PLACE AT +GRT000010000000200000023 0000000000 +TRL000010000000200000025 \ No newline at end of file