383 issues

[kirkhess]

The 383 field is pretty specific to music cataloging; the shape used by BIBFRAME is significantly different from the MLA specifications.

For exampe: https://lccn.loc.gov/2020564285/marcxml (ocn 923157573)

<datafield ind1=" " ind2=" " tag="383">
<subfield code="c">H. 658</subfield>
<subfield code="d">Helm</subfield>
<subfield code="2">mlati</subfield>
</datafield>
<datafield ind1=" " ind2=" " tag="383">
<subfield code="c">H. 659</subfield>
<subfield code="d">Helm</subfield>
<subfield code="2">mlati</subfield>
</datafield>
<datafield ind1=" " ind2=" " tag="383">
<subfield code="c">H. 660</subfield>
<subfield code="d">Helm</subfield>
<subfield code="2">mlati</subfield>
</datafield>
<datafield ind1=" " ind2=" " tag="383">
<subfield code="c">H. 661</subfield>
<subfield code="d">Helm</subfield>
<subfield code="2">mlati</subfield>
</datafield>
<datafield ind1=" " ind2=" " tag="383">
<subfield code="c">H. 662</subfield>
<subfield code="d">Helm</subfield>
<subfield code="2">mlati</subfield>
</datafield>

CPE Bach ("Helm" in mlati), is converted into repeated Music Thematic Numbers with the 383$cd concatenated and no $2.
https://id.loc.gov/resources/works/23417108

Music Thematic Number
H. 658 Helm
Music Thematic Number
H. 659 Helm
Music Thematic Number
H. 660 Helm
Music Thematic Number
H. 661 Helm
Music Thematic Number
H. 662 Helm

Converting that back to MARC, you get this:

    <marc:datafield tag="383" ind1=" " ind2=" ">
        <marc:subfield code="c">H. 658 Helm</marc:subfield>
        <marc:subfield code="c">H. 659 Helm</marc:subfield>
        <marc:subfield code="c">H. 660 Helm</marc:subfield>
        <marc:subfield code="c">H. 661 Helm</marc:subfield>
        <marc:subfield code="c">H. 662 Helm</marc:subfield>
    </marc:datafield>

But it could be something like this (or like the original):

<marc:datafield tag="383" ind1=" " ind2=" ">
    <marc:subfield code="c">H. 658</marc:subfield>
    <marc:subfield code="c">H. 659</marc:subfield>
    <marc:subfield code="c">H. 660</marc:subfield>
    <marc:subfield code="c">H. 661</marc:subfield>
    <marc:subfield code="c">H. 662</marc:subfield>
    <marc:subfield code="d">Helm</marc:subfield>
    <marc:subfield code="2">mlati</marc:subfield>
</marc:datafield>

Without some kind of new property/Class to hold the thematic numbering prob. this form is the only option.

[kirkhess]

Subfield e is not supported in m2bf2, and is very infrequently used in 383s in WC but it is in use.

e.g. https://lccn.loc.gov/2019564428/marcxml

<datafield ind1=" " ind2=" " tag="383">
<subfield code="b">op. 39</subfield>
<subfield code="e">Pleyel</subfield>
</datafield>
<datafield ind1=" " ind2=" " tag="500">
<subfield code="a">"Pleyel took the liberty of extracting these twelve quartets from the collection of Boccherini's works in which he had acquired proprietary rights and publishing them, without any intimation to the reader of the true facts, with a single Opus number, although in relaity they were composed at various dates between 1780 and 1795 and are borrowed from various opera of Boccherini without any respect for chronological order."--Gérard.</subfield>
</datafield>

[kefo]

What are the $2s you have in your data? 'mlati,' obviously, but what are the others? I ask in part because I can see a way to linked-data-ify the mlati codes but I don't know how many others of these are out there and the frequency of their use.

In any event, we can see a potential pathway here via PMO or treating this field as an Identifier.