Created an analysis script for Custom/Local metadata #21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…states more explicityly that it can be used for custom metadata or metadata written in local schemas
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So I've been looking over the analysis scripts to see what would be needed to create an analysis script for custom/local schema metadata (such as an export from ContentDM). I modified dlxsexport_analysis.py by replacing the XPath used to create the record_id with a different XPath and it worked ok. So I put a note in on where to change the XPath for record_id and changed other notes so that it's more general and doesn't refer to DLXS.
Let me know if this works or if there's anything else I need to do!
PS: The changed code is in Line 25 and Line 17.