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

empty MARC fields with geographic subdivision URIs #22

Open
jodiw01 opened this issue May 22, 2024 · 2 comments
Open

empty MARC fields with geographic subdivision URIs #22

jodiw01 opened this issue May 22, 2024 · 2 comments

Comments

@jodiw01
Copy link

jodiw01 commented May 22, 2024

When a MARC record contains a geographic heading that has a subdivision heading -- and has two URIs in id.loc.gov -- bibframe2marc is selecting the subdivision URI and creating an empty MARC field. An added complication is that the geographic heading is used as a bf:PrimaryContribution in the following examples.

Examples:
001 10277584
https://id.loc.gov/resources/works/10277584.html
2$aAlaska$1http://id.loc.gov/rwo/agents/n79018447-781$4http://id.loc.gov/vocabulary/relators/ctb

Correct heading:
110 2$aAlaska$1http://id.loc.gov/rwo/agents/n79018447$4http://id.loc.gov/vocabulary/relators/ctb

001 10053631
https://id.loc.gov/resources/works/10053631.html
2$aSweden$1http://id.loc.gov/rwo/agents/n79021184-781$4http://id.loc.gov/vocabulary/relators/ctb

Correct heading:
110 2$aSweden$1http://id.loc.gov/rwo/agents/n79021184$4http://id.loc.gov/vocabulary/relators/ctb

001 21289967
https://id.loc.gov/resources/works/21289967.html
2$aPanama$1http://id.loc.gov/rwo/agents/n79068688-781$4http://id.loc.gov/vocabulary/relators/ctb

Original MARC:
1101 $aPanama.

001 7250281
https://id.loc.gov/resources/works/7250281.html
2$aAustria$1http://id.loc.gov/rwo/agents/n79040121-781$4http://id.loc.gov/vocabulary/relators/ctb

Original MARC:
1101 $aAustria.$kLaws, statutes, etc.

@kefo
Copy link
Member

kefo commented May 22, 2024

This is has two source issues.

  1. An LC system issue.
  2. A MARC-to-BF conversion issue.

With respect to '2,' I've not looked at the specs, but assuming I grabbed the correct passage of code (I was working quickly with an eye to capturing this information versus descending the rabbit hole to its ultimate depth), the $k is not being converted:

https://github.com/lcnetdev/marc2bibframe2/blob/master/xsl/ConvSpec-1XX%2C7XX%2C8XX-names.xsl#L772-L778

@jodiw01
Copy link
Author

jodiw01 commented May 22, 2024

The lack of a $k is not a factor for the Alaska example, but it is for the Sweden example. (but $k doesn't seem appropriate for a treaty name?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants