-
Notifications
You must be signed in to change notification settings - Fork 5
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
[Remediation] [building-or] #1575
Comments
in the first asset the term is in lcsubject, but the second one I checked uses it in workType |
I think I see what Ed's intent was. Let's use http://id.loc.gov/authorities/subjects/sh2001006360 for subjects and http://vocab.getty.edu/aat/300054638 for worktypes. |
ok hoping these are done now. |
ok I'm hoping these are the last of the verdammt rights probs After you fix, I will remove the wacko dcRightsHolder, and then hopefully by then, we'll have the crosswalk updated to handle the old predicate |
@lsat12357 Corrected. |
collection_id: building-or
sorry, more things...
these loc subjects are used as workType in building-or
"http://id.loc.gov/authorities/subjects/sh85031252",1,
"http://id.loc.gov/authorities/subjects/sh85038731",7,
"http://id.loc.gov/authorities/subjects/sh85062603",15,
"http://id.loc.gov/authorities/subjects/sh85075320",27,
"http://id.loc.gov/authorities/subjects/sh85078076",39,
"http://id.loc.gov/authorities/subjects/sh96004672",6,
If you give me replacement uris I will fix
Also coming, more wonky uris that are failing bc they are non-ascii. After talking to wickr, I am going to try to scrape all the nts.
Known Issues
Related Tickets
The text was updated successfully, but these errors were encountered: