search

uwlib-cams / MARC2RDA

mapping between MARC21 and RDA-RDF
Creative Commons Zero v1.0 Universal
36 stars 3 forks source link

246 varying form of title #116

Open CECSpecialistI opened 3 years ago

CECSpecialistI commented 3 years ago

https://github.com/uwlib-cams/MARC2RDA/blob/main/Working%20Documents/2XX.csv

lake44me commented 1 week ago

@sita @cspayne I've reviewed 246 and have suggestions for revising some of the fields that I'd like you to took at and revise or ok before I make the changes.

  1. It seems to me the transformation note for $g (Miscellaneous) (e.g. $g (varies slightly)) is lacking something. Transformation note is "2nd indicator label: {a}: {b}, {f}, {n}, {p}. if present" which is what's in the row above it. No indication of what to do with $g. if this is going to be mapped to "Note on manifestation" I would suggest the literal, "Note on variant title "[2nd indicator label: {a}: {b}, {f}, {n}, {p}. if present]": + contents of $g."
    I don't know how to format this instruction, but does it make sense?

    I think this is better than including $g in the variant title since it's added by the catlaoger, but we would have to quote the variant title to indicate which one the $g applies to.

  2. For $h, Medium (also known as GMD) there was a mapping to http://rdaregistry.info/Elements/m/P30002 "has media type", with no transformation notes.

There is no requirement that RDA media types be used with P30002; another scheme, or an unstructured uncontrolled term can be used. But I have a feeling this was discussed with $h in 245 in a meeting (but I can't find it in notes from 2022). Looks like there was a decision to deline use of P30002 and go with 30335. The mapping and transformation notes read:

h Medium (NR) | http://www.rdaregistry.info/Elements/m/P30335 | has category of manifestation| structured
Transformation notes: If square brackets surrounding whole field (aside from ending punctation), remove. If subfield is last subfield, remove ending , or . unless in abbreviations list - CP 2024-10-11

Other notes: See also TAG 007 , 336, 337 and 338
See what? --TG 2022-10-14 possible to look up URI's for most GMD's? SMD also exist...more specific ones. coded. No lookup provided in phase 1. TG 2022-10-14."

For consistency, I would suggest using the same mapping for 246 $h if that's ok with you @Sita @lake44me Ok with me.

  1. For $5 (institution to which field applies) I don't think we have a coded example yet that is similar, do we? I checked 730 and it is "first pass", incomplete and $5 is not addressed. 630 doesn't have a $5 !? 740 (Uncontrolled title added entry) has $5 but it hasn't been coded.

Looking at what we did in 500. We had a conditional mapping when $5 was present, ,mapping contents of $a to http://rdaregistry.info/Elements/i/P40028 (Note on item). This was simple for 500 but will add a tad of complexity to 246 since we have so many variations that would all get the condition. For $5 mapping, we referenced the decision at https://github.com/uwlib-cams/MARC2RDA/wiki/Decisions-Index#iij-5 which involved minting a URI for the item, one for the collection to which it belongs, and associating collection with an agent based on the abbreviation in the $5.

I have a similar question for 246. If the variant title is local to an institution, can we assume it is item-specific? If so, the 246 subfields should be mapped to http://rdaregistry.info/Elements/i/P40082 Title of item. (unstructured) If you agree I can add notes and mappings using that property and apply the same transformation notes to $5 as we used for 500.

cspayne commented 4 days ago

Hi @lake44me

  1. I agree that note on manifestation should be used for $g, and the transformation note you have suggested makes sense.
  2. We should follow the same mapping for $h that we do in 245
  3. I am not sure about $5 and whether the title would be item specific, we may need to ask for opinions from the whole group.