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

Document model : add the type bf:Lccn to identifiers #1756

Closed
JoelleDosimont opened this issue Mar 9, 2021 · 0 comments · Fixed by #1767
Closed

Document model : add the type bf:Lccn to identifiers #1756

JoelleDosimont opened this issue Mar 9, 2021 · 0 comments · Fixed by #1767
Assignees
Labels
f: data About data model, importation, transformation, exportation of data, specific for bibliographic data f: editor Concerns editor based on JSON schema AND custom editor

Comments

@JoelleDosimont
Copy link
Contributor

JoelleDosimont commented Mar 9, 2021

Describe the issue
Currently the LCCN (MARC 010) is not present in the document model.

What should be done
In "identifiedBy", add the type bf:Lccn
The "Conversion file" has already been updated accordingly (L09).

@JoelleDosimont JoelleDosimont added f: editor Concerns editor based on JSON schema AND custom editor triage f: data About data model, importation, transformation, exportation of data, specific for bibliographic data labels Mar 9, 2021
zannkukai added a commit to zannkukai/rero-ils that referenced this issue Mar 12, 2021
Closes rero#1756

Co-Authored-by: Renaud Michotte <renaud.michotte@gmail.com>
@zannkukai zannkukai self-assigned this Mar 12, 2021
zannkukai added a commit that referenced this issue Mar 15, 2021
Closes #1756

Co-Authored-by: Renaud Michotte <renaud.michotte@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
f: data About data model, importation, transformation, exportation of data, specific for bibliographic data f: editor Concerns editor based on JSON schema AND custom editor
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants