uwlib-cams / MARC2RDA

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

Control Subfields #20

Closed CECSpecialistI closed 2 years ago

CECSpecialistI commented 3 years ago

The control subfields in Appendix A of the MARC Bibliographic Standard have made their first appearance at the end of the 490 field here. They're going to reappear all over this mapping, and they aren't included in the existing mapping the RSC published on the Registry. Should we add this appendix to another mapping spreadsheet in our Working Documents, deal with them there, and refer to that document as these fields appear in all the other spreadsheets? Does anyone have ideas about how these should be mapped?

AdamSchiff commented 3 years ago

I think these would be provenance information.

Adam L. Schiff Principal Cataloger University of Washington Libraries (206) 543-8409 @.***


From: Crystal Clements @.> Sent: Thursday, October 28, 2021 9:10 AM To: uwlib-cams/MARC2RDA @.> Cc: Adam L Schiff @.>; Assign @.> Subject: [uwlib-cams/MARC2RDA] Control Subfields (Issue #20)

The control subfields in Appendix Ahttps://www.loc.gov/marc/bibliographic/ecbdcntf.html of the MARC Bibliographic Standard have made their first appearance at the end of the 490 field herehttps://github.com/uwlib-cams/MARC2RDA/blob/main/Working%20Documents/4XX.csv#L419. They're going to reappear all over this mapping, and they aren't included in the existing mapping the RSC published on the Registry. Should we add this appendix to another mapping spreadsheet in our Working Documents, deal with them there, and refer to that document as these fields appear in all the other spreadsheets? Does anyone have ideas about how these should be mapped?

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHubhttps://github.com/uwlib-cams/MARC2RDA/issues/20, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADFBVB2TMT2OAFIJIEBUXADUJFYWDANCNFSM5G5IX2AQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

CECSpecialistI commented 3 years ago

Should we map provenance information?

AdamSchiff commented 3 years ago

Much provenance info has no place to go in MARC. But some does.

Adam L. Schiff Principal Cataloger University of Washington Libraries Box 352900 Seattle, WA 98195-2900 aschiff @ uw.edu


From: Crystal Clements @.> Sent: Tuesday, November 2, 2021 3:07:31 PM To: uwlib-cams/MARC2RDA @.> Cc: Adam L Schiff @.>; Assign @.> Subject: Re: [uwlib-cams/MARC2RDA] Control Subfields (Issue #20)

Should we map provenance information?

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHubhttps://github.com/uwlib-cams/MARC2RDA/issues/20#issuecomment-958086432, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADFBVBY5FWADMJUWVZODIV3UKBAIHANCNFSM5G5IX2AQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

pan-zhuo commented 2 years ago

For $6, it seems easier if the field is a transcription field. It would mean a parallel metadata statement in a non-Latin script is needed. Then maybe just take the field tag in 880 $6 and treat it the same way we treat the associated regular field.

245 10$6880-01$a[Title in Latin script]
880 10$6245-01/(2/r$a[Title in Hebrew script linked to associated field]

Treat the 880 as a 245. For script identification code, rdf language tags seem more specific. For orientation code, may have to do with the base direction? Doesn't seem to have been implemented at this time.

For identifiers, if the cataloging language is English, are there ever identifiers not expressed in Latin script?

Not sure about headings yet.

AdamSchiff commented 2 years ago

Most identifiers would be expressed in Latin script and Arabic numerals. But it would be possible for some not to be. I can't think of a real example within RDA yet, but to illustrate that an identifier doesn't have to be in Latin, here's a Wikidata property:

INPA park ID (https://www.wikidata.org/wiki/Property:P10392):

[cid:96bdb780-3241-42dd-864d-d7c520a36b24]

And here's one where some identifiers are in Chinese or a mix of Chinese and Latin script:

[cid:3bcf7de2-72a5-4d01-8f45-f6932abb5af7]

Adam L. Schiff Principal Cataloger University of Washington Libraries (206) 543-8409 @.***


From: Zhuo Pan @.> Sent: Wednesday, March 16, 2022 4:51 PM To: uwlib-cams/MARC2RDA @.> Cc: Adam L Schiff @.>; Assign @.> Subject: Re: [uwlib-cams/MARC2RDA] Control Subfields (Issue #20)

For $6, it seems easier if the field is a transcription field. It would mean a parallel metadata statement in a non-Latin script is needed. Then maybe just take the field tag in 880 $6 and treat it the same way we treat the associated regular field.

245 10$6880-01$a[Title in Latin script] 880 10$6245-01/(2/r$a[Title in Hebrew script linked to associated field]

Treat the 880 as a 245. For script identification code, rdf language tags seem more specific. For orientation code, may have to do with the base directionhttps://w3c.github.io/rdf-dir-literal/? Doesn't seem to have been implemented at this time.

For identifiers, if the cataloging language is English, are there ever identifiers not expressed in Latin script?

Not sure about headings yet.

— Reply to this email directly, view it on GitHubhttps://github.com/uwlib-cams/MARC2RDA/issues/20#issuecomment-1069754369, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADFBVB7PFG7UTIHXT6NS7VLVAJXX7ANCNFSM5G5IX2AQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were assigned.Message ID: @.***>