Skip to content
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

Add bf:AccessionNumber class as a subclass if bf:Identifier #11

Closed
sfolsom opened this issue Jun 25, 2018 · 4 comments
Closed

Add bf:AccessionNumber class as a subclass if bf:Identifier #11

sfolsom opened this issue Jun 25, 2018 · 4 comments
Assignees
Labels
semantic changes to rdfs:domain, rdfs:range, owl changes, etc. under review Work begins on issue; incl. questions, consultations, or BFC review.

Comments

@sfolsom
Copy link

sfolsom commented Jun 25, 2018

Justification: Accession numbers are an important identifier for cultural heritage institutions to record and track an object in their collections. These numbers are also useful in the provenance of an object. BF2 does not explicit way to record accession numbers that are currently being recorded in MARC 541 $e. This issue was discussed during the Rare Material and ArtFrame Ontology Spring on March 2-3, 2017, and it was determined that accession numbers are an essential identifier and must have some way recording this information in a linked data ontology for cultural heritage and rare materials. See: https://github.com/LD4P/arm/blob/master/modeling_recommendations/accession_numbers.md.

[This recommendation was made on behalf of the LD4P Art & Rare Materials BIBFRAME Ontology Extension (https://github.com/LD4P/arm).]

@raydAtLC raydAtLC added semantic changes to rdfs:domain, rdfs:range, owl changes, etc. under review Work begins on issue; incl. questions, consultations, or BFC review. labels Jul 5, 2018
@raydAtLC raydAtLC self-assigned this Jul 6, 2018
@jak473
Copy link

jak473 commented Sep 21, 2020

Has LC considered this proposal? ARM is soon to finalize it's next release and will need to include AccessionNumber if LC does not incorporate into BF.

@ntra00
Copy link
Contributor

ntra00 commented Sep 21, 2020

We have it on a list of things we (LC) want to approve, so assuming planets align, it will become a subclass of Identifier.

@jak473
Copy link

jak473 commented Sep 21, 2020

Great, thanks @ntra00 ; do you have a sense of when this may happen?

@kefo
Copy link
Member

kefo commented Jun 24, 2021

@kefo kefo closed this as completed Jun 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semantic changes to rdfs:domain, rdfs:range, owl changes, etc. under review Work begins on issue; incl. questions, consultations, or BFC review.
Projects
None yet
Development

No branches or pull requests

5 participants