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.

Sign up for GitHub

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

Jump to bottom

Using 010/016 for URI generation #42

Open
danmichaelo opened this issue Nov 8, 2017 · 1 comment
Open

Using 010/016 for URI generation #42

danmichaelo opened this issue Nov 8, 2017 · 1 comment

Comments

@danmichaelo
Copy link
Member

danmichaelo commented Nov 8, 2017 •
edited
Loading

The example record (source xml, target rdf) gets the URI http://lod.nal.usda.gov/nalt/142 rather than the correct http://lod.nal.usda.gov/nalt/1396

Seems like vocabularies.yml must be updated to use the value of the 016 field rather than the 001 field.. My guess is that 010 or 016, if present, could always take precedence over 001 when it comes to URI generation, but I could be wrong here..
danmichaelo added a commit that referenced this issue Nov 8, 2017
@danmichaelo
[#42] Let 010 and 016 take precedence over 001
546a68c 
This fixes the NALT URIs.
@danmichaelo
Copy link
Member Author

Not sure if this solution is general enough, but until we have a counterexample…

@danmichaelo danmichaelo changed the title URIs for NALT are wrong - using 010/016 for URI generation Using 010/016 for URI generation Nov 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@danmichaelo