copyright date not in MARC record: (264 _4 $c )

[jimfhahn]

Type of change
change to existing mapping

Example RDF records
Please provide URIs or RDF of the bf:Instance. If providing RDF, Turtle is preferred.

https://api.stage.sinopia.io/resource/2a182f02-abd1-4c04-bbcd-b70457a1416c

Resource template
Which resource template does this apply to? In which Sinopia environment (development, stage, production)?

PCC Instance Template in stage.

Expected MARC
What MARC did you expect to receive?

264 | #4$c©1996

Actual MARC
What MARC did you actually receive (if mapped incorrectly)?

264 1 $a New York (N.Y.) $b Schirmer Books $c 1996
264 1 $a London (England) $b Prentice-Hall International $c 1996

Expected mapping logic
Please describe the logic of the mapping.

Could entering in copyright information like this:
"http://id.loc.gov/ontologies/bibframe/copyrightDate": [ { "@value": "©1996", "@language": "en" }
generate a (264 $4 $c ) in the MARC?

[NancyL]

@jimfhahn just to be sure. You primarily want the copyright date in the 264, correct? So the mapping would be:
bf:copyright ©1996
converts to:
264 #4 $c ©1996 in MARC

Are you okay if the 008 t [pubdate] [copyright date] is not implemented in the first round?

[jimfhahn]

Yes, that sounds good! 🙏

…

On Mon, Sep 12, 2022 at 12:44 PM NancyL ***@***.***> wrote: @jimfhahn <https://github.com/jimfhahn> just to be sure. You primarily want the copyright date in the 264, correct? So the mapping would be: bf:copyright ©1996 converts to: 264 #4 <#4> $c ©1996 in MARC Are you okay if the 008 t [pubdate] [copyright date] is not implemented in the first round? — Reply to this email directly, view it on GitHub <#188 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJ76LN6VKQPPOC6H3RS5YDV55TY3ANCNFSM5PE2M7MQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>