Closed kiegel closed 7 years ago
It's marked as no attempt to code - if you send me an example record, I'll look into what we need to do to support this field.
Here is a sample record in MARCXML. (not supported as an attachment)
<?xml version="1.0" encoding="UTF-8"?>
-
-
We've decided we're going to close this issue after evaluating the proposed solution and deciding it will not work. Also, apparently this field is not approved by NACO, which is one reason it is marked as no attempt to code in the specifications, and is probably why we have no LC examples. Thanks for the marcxml, we'll definitely revisit this field when we look at updating the ontology/specifications.
Just noting that NACO is not relevant because the proposal is for the 388 in bib records. While LC may not have examples, it is being used by PCC libraries: OCLC #321177, #50028686, #3354935, #38539852, #969996605. Also, the proposed property is an addition to bflc, which is under LC's control, so it does not need to wait for an update to the bf ontology.
I'll pass that on, thanks for the OCLC numbers. The field is marked as "no attempt to code" in the specs, I don't doubt it's used or useful but we can't convert it until we have a spec. If it looks like they'll actually attempt to model this in the ontology and write a spec we'll reopen this issue.
Thanks!
-Kirk
On Wed, Nov 8, 2017 at 12:57 PM, Joe Kiegel notifications@github.com wrote:
Just noting that NACO is not relevant because the proposal is for the 388 in bib records. While LC may not have examples, it is being used by PCC libraries: OCLC #321177, #50028686, #3354935, #38539852, #969996605. Also, the proposed property is an addition to bflc, which is under LC's control, so it does not need to wait for an update to the bf ontology.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/lcnetdev/marc2bibframe2/issues/60#issuecomment-342901079, or mute the thread https://github.com/notifications/unsubscribe-auth/ABWqki2xbqkul4mTu3CqnEhj6PCn9Opnks5s0et6gaJpZM4QIJo4 .
We would like to see field 388 (Time period of creation) converted. It could be done easily based on the template you have established for field 386.
bflc:timePeriodOfCreation [ a bflc:TimePeriodOfCreation ; rdfs:label "388 Time Period of Creation subfield a" ; bflc:appliesTo [ a bflc:AppliesTo ; rdfs:label "388 subfield 3" ] ;
bf:source [ a bf:Source ; rdfs:label "388 subfield 2" ] ] .