-
Notifications
You must be signed in to change notification settings - Fork 0
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
Bulkrax doesn't complete/update metadata #685
Comments
I see that you've created an importer to update a metadata field, but it's unclear which specific metadata fields were updated and which ones I should focus on in relation to this CSV. For future tickets, it would be greatly helpful to include the specific fields you’ve updated and the expected changes. This additional context will help us quickly understand and address the reported issue more efficiently. Thank you! |
Hi @aprilrieger - thanks for this. A number of fields were updated, but the biggest changes occurred in the keyword, subject, and spatial fields. As an example, I'll illustrate the changes that were made to a single record - https://digitalcollections.lib.utk.edu/concern/images/1f82f04d-2d2f-41ac-9473-8d8d40a2656a?locale=en Because these records were often derived from MARC records, a lot of the keywords have unnecessary trailing periods (that make it not possible for them to be grouped with like terms in a facet). Additionally, when possible, we've substituted out uncontrolled keywords for subjects with URIs. Complex headings that include both topical and geographic values were also separated out into the appropriate fields. So the current record on Hyku has the following for keywords: Paris (Tenn.)--Social life and customs With the updated import sheet we wanted the following result: Subjects: http://id.loc.gov/authorities/subjects/sh85001932 (African Americans) | http://id.loc.gov/authorities/subjects/sh85080593 (Manners and customs) | http://id.loc.gov/authorities/subjects/sh85061212 (History) I've included the strings in parentheses for clarity, though obviously they can't be used for fields that require URIs. My concern here is that the importer itself never went through in the dashboard and no records were processed. I'm going to try reimporting next week with just a few changes to one field and see that things go through and then try to make changes on a larger scale. For us typically remediating a collection involves lots of changes rather than just a few. |
Summary
Acceptance Criteria
Testing Instructions
The text was updated successfully, but these errors were encountered: