-
Notifications
You must be signed in to change notification settings - Fork 10
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
CSV Compound Child metadata ignored #494
Comments
@bondjimbond I can take a look at this tonight. Can you share your metadata spreadsheet and mappings file with me via email? |
Sorry @mjordan, I just figured out what the problem is. So my CSV's child_key colum includes "1" for the first child, "2" for the second. Due, most likely, to annoying spreadsheet editor tendencies to auto-format numerical cells as numbers instead of text. The filenames, meanwhile, end in _01.tif and _02.tif. MIK throws the error:
Because based on the filenames, MIK created directories named "01" and "02", but based on the metadata it's trying to find the directory "1" and "2" to write the correct metadata. So, a couple of takeaways:
|
Agreed that we should do something here. These two things are a good start, but I wonder if we should have a |
Indeed! |
Or possibly building a check into https://github.com/mjordan/iipqa. |
I'd rather see it just built into the checks done by --checkconfig... Check that the values in the child_key column match the values in the file extensions. |
It should be allowed for the directory to contain file numbers not mentioned in the CSV, but it should be illegal for the CSV to contain child_key values that are not found in the directory. |
I'm trying to run a Compound CSV job, and running into problems getting the metadata in child rows to end up in the child MODS.xml files. MIK is treating the objects as if they do not appear in the spreadsheet.
Here are my relevant config settings:
Am I missing some setting to allow MIK to read the child objects' metadata rows, or is MIK broken?
The text was updated successfully, but these errors were encountered: