Kirk Hess
Kirk Hess
The MARC 242 field has two mandatory subfields: $a and $y See [https://www.oclc.org/bibformats/en/2xx/242.html](https://www.oclc.org/bibformats/en/2xx/242.html) The marc2bibframe2 specifications have 'ignore" on subfield $y so titles with the variant type 'translated' do not...
I propose that we add bf:Microform as a Class, specifically a bf:Instance subclass. However, since all the Work types are aligned with the LDR types, bf:Microform might end up as...
Most BF classes have subclasses and there seems to be many examples where you use both the parent and the subclass. In some cases, the parent class is never used...
Because of the duplication of cartographic information in MARC, in BIBFRAME examples you can clearly see the duplication and it causes problems converting back to MARC since the parts are...
We all know the note modeling approach has taken a lot of turns yet the current approach still matches the original whitepaper for the most part: https://www.loc.gov/bibframe/docs/pdf/bf2-notes-march2017.pdf It looks like...
The current implementation of Provision Activities causes problems with MARC conversion to/from the 008 and the 26x. The current strategy is to create multiple provision activities - one with a...
008 bytes, 385 and 521 map into bf:intendedAudience, although the way this is implemented the only 385 $a, $b values that are supported are the ones listed in the BKS...
If subfield $t and subfield $g are included in the title (which is unlikely but possible), the subfields will no longer be in the order they originally were and $g...
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) ``` H. 658 Helm...