Ms. Regan Smith and Ms. Anna Chauvet
December 6, 2019
Page 2
the relevant writers and publishers. For this reason and because of the various concerns about the
sound recording data discussed at the meeting, we highlighted the need for a strong disclaimer.
3. Data Quality. We discussed a number of marketplace realities that affect the quality of the sound
recording data that is available to the MLC.
a. Data is most accurate when it is obtained as close to the source as possible. We discussed
the new RIN (i.e., Recording Information Notification) message from DDEX, which captures
data in the studio and is the ultimate tool for capturing data at the source. We discussed the
fact that the quality of data can vary among different genres of music, and that artists or
performers sometimes do not want their names to appear in credits or to be listed in a
publicly available database (e.g., when an established artist sits in to help a newer artist).
b. We reiterated the suggestion in our Initial Comments that the MLC be required to obtain its
sound recording data from a single authoritative source, such as SoundExchange.
c. We explained that SoundExchange gets the same data feeds as the DMPs (for purposes of
distributing statutory licensing royalties) but then it dedupes and deconflicts the data.
SoundExchange receives data from approximately 3400 labels, including certain
independent distributors (e.g., CdBaby). If the MLC does not get its data from a single
authoritative source, such as SoundExchange, it will be faced with the burden of reconciling
data conflicts that have been ignored for years because of the way the DMPs silo their label
data. SoundExchange has already reconciled most of those conflicts.
d. We gave examples of how and why the DMPs alter and augment the metadata they receive
from the labels and noted that any data provided by the DMPs to the MLC must be
submitted in unaltered form.
e. We stressed that the database should not be populated from usage reports because those
are subject to typographical and other human errors; instead, it should be populated from a
single authoritative source. Once the database is populated, DMPs should ping the database
to derive the information needed to populate their reports of use. Where a track is not
already in the MLC database, the DMP should include it in its report of use but when that
data appears in the database it should be flagged as unverified or from a non-authoritative
source.
4. Sound Recording Copyright Owner Data. We explained the difference between the data in the digital
supply chain, where actual copyright ownership is irrelevant, and the record companies’ copyright
registration and royalty databases, which the record companies use for litigation purposes and to
know who to pay for various recordings. DMPs only need to know who to pay and, maybe, who to
call if issues arise. We discussed how data labelling the supply chain data as “sound recording
copyright owner” could mislead the public and could be upsetting to the actual copyright owners,
who are sometimes artists or their heirs, who may mistakenly think the distributing label is trying to
claim ownership of their recordings. Conversely, artists who are the actual copyright owners likely
do not want their names listed in a publicly accessible database. We noted that the
SoundExchange’s ISRC look up database does not include owner information and it is not currently
available for bulk download by the public. We also highlighted that making ISRCs publicly available in
bulk could also raise piracy concerns.