-
Notifications
You must be signed in to change notification settings - Fork 11
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
Initial work on #482. #487
Conversation
Failing on whitespace in one of the test files.... which is strange since I didn't touch that file. I'll investigate. |
Anything beyond the work I've already been doing that you think should be tested? Any places where you see potential problems/conflicts, etc? |
Only to confirm whether it works in other Cdm toolchain metadata manipulators like: |
NormalizeDate: Can't confirm, because it doesn't work for me regardless of which field I choose...
For the others: well, nothing crashed... SimpleReplace doesn't seem to do anything, and I don't really have the appropriate data for SplitRepeatedValues. I'm not sure that the data I have available is useful for testing those manipulators. |
Let's not worry about those plugins now, we can address later as needed. |
@MarcusBarnes Any objection to me merging this then? |
@bondjimbond I'm assuming that if |
@MarcusBarnes If I remove the use_nicknames option, I still get the NormalizeDate problems. I haven't tried with tagging it "false" |
Do you get those NormalizeDates problems if you use the default branch (not the changes in the PR)? |
@MarcusBarnes Yeah, NormalizeDates is still a problem for me. But that's kind of normal; these INI files are rather finicky. If I hear no objections from you, I'll merge this soon; I'd like to get it into the main branch ASAP. |
@bondjimbond Please go ahead and merged this. Also please create a separate issue regarding the details of how NormalizeDate is failing for your use cases so that the issue is documented. Thanks so much! |
Github issue: (#482)
What does this Pull Request do?
Allows use of CONTENTdm metadata field "nicknames" in MIK mappings files and Twig-based metadata manipulators.
What's new?
The nicknames are used internally in MIK, but we go out of our way to allow the use of the corresponding human-readable field labels in mappings files. This change effectively bypasses that conversion.
How should this be tested?
@bondjimbond has already tested this thoroughly, but checking out this branch, then following the documentation in how to configure this option in https://github.com/MarcusBarnes/mik/wiki/Cookbook:-Using-CONTENTdm-field-nicknames-instead-of-labels should be sufficient.
Additional Notes
https://github.com/MarcusBarnes/mik/wiki/Cookbook:-Using-CONTENTdm-field-nicknames-instead-of-labels created, and can be linked from the Cdm toolchain wiki pages and https://github.com/MarcusBarnes/mik/wiki/Metadata-manipulator:-InsertXmlFromTemplate.
No.
Yes.