You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a full rebuild of the oe24-test environment, I re-loaded our sample data set which should contain:
59 works
450 FileSets and 450 Files
After the ingest completed, Bulkrax reported 1 CSV row entry as failing: Standard Error, missing title. (Though each row in the CSV file contains a title and other required fields)
The FileSets appear to have all been created, based on the Hyrax Dashboard counts.
The Bulkrax "identifier" for the erroring row includes a randomly generated deduplication_key which does not exist in the CSV (they all contain ARK identifiers as deduplication_keys). From what I can determine from the Bulkrax UI, it is the last row on the spreadsheet. However, if that's the case, that work did get created.
I then used the Bulkrax UI to remove and rebuild the erroring row.
Bulkrax shows an Enqueued state of "-1", but the re-run does not appear to have occurred.
The text was updated successfully, but these errors were encountered:
After a full rebuild of the oe24-test environment, I re-loaded our sample data set which should contain:
59 works
450 FileSets and 450 Files
After the ingest completed, Bulkrax reported 1 CSV row entry as failing: Standard Error, missing title. (Though each row in the CSV file contains a title and other required fields)
The FileSets appear to have all been created, based on the Hyrax Dashboard counts.
The Bulkrax "identifier" for the erroring row includes a randomly generated deduplication_key which does not exist in the CSV (they all contain ARK identifiers as deduplication_keys). From what I can determine from the Bulkrax UI, it is the last row on the spreadsheet. However, if that's the case, that work did get created.
I then used the Bulkrax UI to remove and rebuild the erroring row.
Bulkrax shows an Enqueued state of "-1", but the re-run does not appear to have occurred.
The text was updated successfully, but these errors were encountered: