-
Notifications
You must be signed in to change notification settings - Fork 25
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 import: subject creator
is unexpected
#3468
Labels
bug
Breaks something but is not blocking
Comments
PascalRepond
changed the title
Subject import:
Document import: subject Sep 25, 2023
creator
is unexpected creator
is unexpected
rerowep
added a commit
to rerowep/rero-ils
that referenced
this issue
Oct 3, 2023
* Make SLSP import more robust against wrong MARC21 for example 019 has no subfields. * Adds $ref creation for different entity types. * Closes rero#3468. Co-Authored-by: Peter Weber <[email protected]>
rerowep
added a commit
to rerowep/rero-ils
that referenced
this issue
Oct 3, 2023
* Make SLSP import more robust against wrong MARC21 for example 019 has no subfields. * Adds $ref creation for different entity types. * Closes rero#3468. Co-Authored-by: Peter Weber <[email protected]>
rerowep
added a commit
to rerowep/rero-ils
that referenced
this issue
Oct 3, 2023
* Make SLSP import more robust against wrong MARC21 for example 019 has no subfields. * Adds $ref creation for different entity types. * Closes rero#3468. Co-Authored-by: Peter Weber <[email protected]>
rerowep
added a commit
to rerowep/rero-ils
that referenced
this issue
Oct 3, 2023
* Make SLSP import more robust against wrong MARC21 for example 019 has no subfields. * Adds $ref creation for different entity types. * Closes rero#3468. Co-Authored-by: Peter Weber <[email protected]>
rerowep
added a commit
to rerowep/rero-ils
that referenced
this issue
Oct 3, 2023
* Make SLSP import more robust against wrong MARC21 for example 019 has no subfields. * Adds $ref creation for different entity types. * Closes rero#3468. Co-Authored-by: Peter Weber <[email protected]>
rerowep
added a commit
to rerowep/rero-ils
that referenced
this issue
Oct 3, 2023
* Make SLSP import more robust against wrong MARC21 for example 019 has no subfields. * Adds $ref creation for different entity types. * Closes rero#3468. Co-Authored-by: Peter Weber <[email protected]>
rerowep
added a commit
to rerowep/rero-ils
that referenced
this issue
Oct 3, 2023
* Make SLSP import more robust against wrong MARC21 for example 019 has no subfields. * Adds $ref creation for different entity types. * Closes rero#3468. Co-Authored-by: Peter Weber <[email protected]>
rerowep
added a commit
to rerowep/rero-ils
that referenced
this issue
Oct 3, 2023
* Make SLSP import more robust against wrong MARC21 for example 019 has no subfields. * Adds $ref creation for different entity types. * Closes rero#3468. Co-Authored-by: Peter Weber <[email protected]>
Garfield-fr
pushed a commit
that referenced
this issue
Oct 4, 2023
* Make SLSP import more robust against wrong MARC21 for example 019 has no subfields. * Adds $ref creation for different entity types. * Closes #3468. Co-Authored-by: Peter Weber <[email protected]>
rerowep
added a commit
that referenced
this issue
Oct 9, 2023
* Make SLSP import more robust against wrong MARC21 for example 019 has no subfields. * Adds $ref creation for different entity types. * Closes #3468. Co-Authored-by: Peter Weber <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description:
When importing a document with a subject of type Work that has a creator (MARC subfield ?), the importer tries to create a subfield subjects_imported.entity.creator that is not accepted by the jsonschema. This creates an error when trying to save the document.
Relates to
Expected behavior:
In this case, the document importer should create a unique authorized_access_point from the MARC fields without creating an invalid "creator" subfield in the json.
Format of the authorized access point : TO BE DEFINED
Steps to Reproduce:
Version:
v1.18.0
Anything else?
The text was updated successfully, but these errors were encountered: