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

MARC-to-RDF transform: fields that likely will require updating the code (because only 1 or two subfield values were processed in the MARC where many subfields exist) #3

Open
gerontakos opened this issue Jun 30, 2023 · 1 comment
Assignees
Labels

Comments

@gerontakos
Copy link
Collaborator

  • MARC 075
    • Potential problem: only $0 and $1 values were output to RDF/XML. It's possible, someday, we'll want to output additional subfield values.
  • MARC 155
    • Potential problem: only $a value was output to RDF/XML. That's because, at this time, the only subfield that appears in the NGL MARC is $a. If other subfields are used eventually, new conditions will be required in the transform.
  • MARC 455
    • Potential problem: only $a value was output to RDF/XML. That's because, at this time, the only subfield that appears in the NGL MARC is $a. If other subfields are used eventually, new conditions will be required in the transform.
  • MARC 680
    • Potential problem: only $i value was output to RDF/XML. That's because, at this time, the only subfield that appears in the NGL MARC is $i. If other subfields are used eventually, new conditions will be required in the transform.
  • MARC 750
    • Potential problem: only $0 values were output to RDF/XML. It's possible, someday, we'll want to output additional subfield values.
  • MARC 755
    • Potential problem: only $1 values were output to RDF/XML. It's possible, someday, we'll want to output additional subfield values.
@gerontakos gerontakos changed the title MARC-to-RDF transform: fields that likely will require updating the code MARC-to-RDF transform: fields that likely will require updating the code (because only 1 or two subfield values were processed in the MARC where many subfields exist) Sep 13, 2023
@gerontakos
Copy link
Collaborator Author

Potential problems noted when preparing version 1-1-1. Nothing done about this at present; maybe later, when it becomes an actual problem.

@briesenberg07 briesenberg07 self-assigned this Feb 23, 2024
@briesenberg07 briesenberg07 pinned this issue Feb 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants