-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
046 special coded dates #79
Comments
From Melissa: "RDA Registry mapping has several subfields going to P20004, "has date of capture". The description says it's a date associated with "recording, filming, etc.", so am I correct in interpreting this as only applying to things with audio or video recordings (videos, movies, music, audiobooks)? If so, I'm thinking about how to write in these conditions -- I'm thinking of basing it off either 336, 337, or 338 so I can narrow in on only resources that would have recording elements. Does this seem like I'm on the right track?" @CatalogerCate and @AdamSchiff , what do you think? Is there an easy way to know when an 046 value is a date of capture vs. another coded date? Or is this really only a functional mapping going from RDA to MARC? |
This information will always be in the 033 and 518. Don’t think 046 has anything to do with this date, but let me check and make sure.
Cate
Cate Gerhart, Librarian
Head, Monographic Cataloging Unit
University of Washington Libraries
***@***.***
206 685-2827 (cell: 206 372-5046)
“The difficult is what takes a little time; the impossible is what takes a little longer.”—Nansen.
From: Crystal Clements ***@***.***>
Sent: Tuesday, December 14, 2021 5:29 PM
To: uwlib-cams/MARC2RDA ***@***.***>
Cc: Cate Gerhart ***@***.***>; Mention ***@***.***>
Subject: Re: [uwlib-cams/MARC2RDA] 046 special coded dates (Issue #79)
From Melissa: "RDA Registry mapping has several subfields going to P20004, "has date of capture". The description says it's a date associated with "recording, filming, etc.", so am I correct in interpreting this as only applying to things with audio or video recordings (videos, movies, music, audiobooks)?
If so, I'm thinking about how to write in these conditions -- I'm thinking of basing it off either 336, 337, or 338 so I can narrow in on only resources that would have recording elements. Does this seem like I'm on the right track?"
@CatalogerCate<https://github.com/CatalogerCate> and @AdamSchiff<https://github.com/AdamSchiff> , what do you think? Is there an easy way to know when an 046 value is a date of capture vs. another coded date? Or is this really only a functional mapping going from RDA to MARC?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#79 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVX7HCTLXHUQ6L52JMKJPRTUQ7VO5ANCNFSM5IXJNZPA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
046 would not normally be used for date of capture. It is used for date of creation of work and date of expression. I suppose as an expression date there could be a mapping to 046 as well as 033 or 518 since for music a performance is a particular expression of a work or works. 046 is more likely to be used to limit searches than 033. There’s definitely the possibility of duplication of information when coding expression dates of music. For film/video 046 is more likely to be used for creation date of work than an expression date. 033/518 would be used
filming/recording dates, which are likely to be specific dates (year-month-day) while 046 is likely to just be a year or years.
Adam
Adam L. Schiff
Principal Cataloger
University of Washington Libraries
Box 352900
Seattle, WA 98195-2900
aschiff @ uw.edu
…________________________________
From: Cate Gerhart ***@***.***>
Sent: Tuesday, December 14, 2021 8:46 PM
To: uwlib-cams/MARC2RDA
Cc: Adam L Schiff; Mention
Subject: Re: [uwlib-cams/MARC2RDA] 046 special coded dates (Issue #79)
This information will always be in the 033 and 518. Don’t think 046 has anything to do with this date, but let me check and make sure.
Cate
Cate Gerhart, Librarian
Head, Monographic Cataloging Unit
University of Washington Libraries
***@***.***
206 685-2827 (cell: 206 372-5046)
“The difficult is what takes a little time; the impossible is what takes a little longer.”—Nansen.
From: Crystal Clements ***@***.***>
Sent: Tuesday, December 14, 2021 5:29 PM
To: uwlib-cams/MARC2RDA ***@***.***>
Cc: Cate Gerhart ***@***.***>; Mention ***@***.***>
Subject: Re: [uwlib-cams/MARC2RDA] 046 special coded dates (Issue #79)
From Melissa: "RDA Registry mapping has several subfields going to P20004, "has date of capture". The description says it's a date associated with "recording, filming, etc.", so am I correct in interpreting this as only applying to things with audio or video recordings (videos, movies, music, audiobooks)?
If so, I'm thinking about how to write in these conditions -- I'm thinking of basing it off either 336, 337, or 338 so I can narrow in on only resources that would have recording elements. Does this seem like I'm on the right track?"
@CatalogerCate<https://github.com/CatalogerCate> and @AdamSchiff<https://github.com/AdamSchiff> , what do you think? Is there an easy way to know when an 046 value is a date of capture vs. another coded date? Or is this really only a functional mapping going from RDA to MARC?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#79 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVX7HCTLXHUQ6L52JMKJPRTUQ7VO5ANCNFSM5IXJNZPA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://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 mentioned.
Reply to this email directly, view it on GitHub<#79 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADFBVB3HUJBA75WD5M3U7X3UQ7XM7ANCNFSM5IXJNZPA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Meeting discussion: 046: generally can't go from MARC2RDA and determine date of capture. Maybe unless someone somewhere used 046**$a p $e [date of capture] |
Next steps: Crystal email Theo. If we still have questions, email GD to ask for consult. |
Yes, as we said, date of capture is 033 not 046.
Cate
Cate Gerhart, Librarian
Head, Monographic Cataloging Unit
University of Washington Libraries
***@***.***
206 685-2827 (cell: 206 372-5046)
“The difficult is what takes a little time; the impossible is what takes a little longer.”—Nansen.
From: Crystal Clements ***@***.***>
Sent: Thursday, December 16, 2021 2:22 PM
To: uwlib-cams/MARC2RDA ***@***.***>
Cc: Cate Gerhart ***@***.***>; Mention ***@***.***>
Subject: Re: [uwlib-cams/MARC2RDA] 046 special coded dates (Issue #79)
Meeting discussion: 046: can't go from MARC2RDA and determine date of capture.
—
Reply to this email directly, view it on GitHub<#79 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVX7HCSHRLOMWLXUEMXSJ5LURJQ7DANCNFSM5IXJNZPA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://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 mentioned.Message ID: ***@***.******@***.***>>
|
From Junghae: I’d like to let you know that there are no records with 046 $a p and $e in Alma. I ran an indication rule but didn’t get any results. |
@gerontakos Do you understand how timespans work? Or should we email GD about this? #79 (comment) |
To keep it short, no, I don't, although I've read the pertinent passages in RDA and LRM. But I think that our properties should make it clear: if there's a range=Timespan, we create a Timespan; if there is no range, we have a choice on the value: it's either a datatype property for which we enter a literal, or it's an object property for which we create a Timespan. I think if there is no range, we're free to decide in our AP what we want to do. I'm only at step one of this problem however. You may have already considered all that. |
@CECSpecialistI Hi Crystal, for 046, the following subfield is mapped to 3 elements because the first indicator Type of entity is # No information provided. Can it be mapped to 3 elements or should we use a broader element? It seems there is no broader element to cover this three. <style type="text/css"></style>
|
Gosh, that's a good question. There is no broader term so I think we have to map to what is "safe". I think the safest mapping for when there is "no information provided" is "has date of manifestation". What do you think, @GordonDunsire @AdamSchiff ? |
If you look at the history of the field at the bottom of the MARC format, you gain more information:
CONTENT DESIGNATOR HISTORY
Field 046 - Special Coded Dates [REDESCRIBED, 2016]
Redescribed to clarify that dates recorded in 008/06-14 may additionally be recorded in field 046.
Indicator 1 - Type of entity [NEW, 2021]
# - No information provided [NEW, 2021]
1 - Work [NEW, 2021]
2 - Expression [NEW, 2021]
3 - Manifestation [NEW, 2021]
Prior to 2021, Indicator 1 was undefined.
$b - Date 1, B.C. date [RENAMED, 2016]
$d - Date 2, B.C. date [RENAMED, 2016]
$j - Date resource modified [NEW, 2002]
$k - Beginning or single date created [NEW, 2002]
$k - Beginning or single date created [REDESCRIBED, 2016]
Redescribed to clarify that dates contained in subfield $k may also be coded elsewhere in the formats.
$l - Ending date created [NEW, 2002]
$m - Beginning of date valid [NEW, 2002]
$n - End of date valid [NEW, 2002]
$o - Single or starting date for aggregated content [NEW, 2013]
$p - Ending date for aggregated content [NEW, 2013]
$x - Nonpublic note [NEW, 2021]
$z - Public note [NEW, 2021]
$2 - Source of date [NEW, 2002]
$3 - Materials specified [NEW, 2021]
As you can see, the first indicator value was undefined until 2021, when it was defined with the four values shown above. Subfields $k and $l were added for work dates in 2002, while $0 and $p were added for work dates in compilations in 2013.
Subfield $a is not used with any of the date of creation subfields. I think its use would be limited to manifestation dates.
Adam
Adam L. Schiff
Principal Cataloger
University of Washington Libraries
(206) 543-8409
***@***.***
…________________________________
From: Crystal Yragui ***@***.***>
Sent: Wednesday, April 24, 2024 11:43 AM
To: uwlib-cams/MARC2RDA ***@***.***>
Cc: Adam L Schiff ***@***.***>; Mention ***@***.***>
Subject: Re: [uwlib-cams/MARC2RDA] 046 special coded dates (Issue #79)
Gosh, that's a good question. There is no broader term so I think we have to map to what is "safe". I think the safest mapping for when there is "no information provided" is "has date of manifestation". What do you think, @GordonDunsire<https://urldefense.com/v3/__https://github.com/GordonDunsire__;!!K-Hz7m0Vt54!n3ocaIGz0bxOn_lmJEg7vzGYM8tYTUiQJ7ELlDqnCw-QdXfUTu3OYJYH0KrUFk7Xvqxy4ibH46_kL-97LdZUGZ0$> @AdamSchiff<https://urldefense.com/v3/__https://github.com/AdamSchiff__;!!K-Hz7m0Vt54!n3ocaIGz0bxOn_lmJEg7vzGYM8tYTUiQJ7ELlDqnCw-QdXfUTu3OYJYH0KrUFk7Xvqxy4ibH46_kL-97umIAqvU$> ?
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/uwlib-cams/MARC2RDA/issues/79*issuecomment-2075600682__;Iw!!K-Hz7m0Vt54!n3ocaIGz0bxOn_lmJEg7vzGYM8tYTUiQJ7ELlDqnCw-QdXfUTu3OYJYH0KrUFk7Xvqxy4ibH46_kL-9720LyqDs$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ADFBVB7P4DMXGEWCC4PVFE3Y674OVAVCNFSM5IXJNZPKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBXGU3DAMBWHAZA__;!!K-Hz7m0Vt54!n3ocaIGz0bxOn_lmJEg7vzGYM8tYTUiQJ7ELlDqnCw-QdXfUTu3OYJYH0KrUFk7Xvqxy4ibH46_kL-97Y6lWsq8$>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
When I reviewed the mapping, I changed most of the mapping. It is better for someone else to review the mapping again. |
Thank you, Penny! Will leave this as "awaiting review" |
Hi @SitaKB , would you review this mapping? |
Hi @AdamSchiff I am reviewing TAG 046. Could you give your input about $x. |
https://github.com/uwlib-cams/MARC2RDA/blob/main/Working%20Documents/0XX.csv
The text was updated successfully, but these errors were encountered: