Updates to ch xslt review #19
Closed
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
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.
@cmharlow - i'd love feedback specifically about historicpitt.xsl running against HPtest.xml. I'm trying to include the collection name in the metadata based on the setSpec element higher up in the node hierarchy. I've tried lookups and just a template match, and nothing will work. And now my eyes are crossing.
What I'm looking for is basically -
if //setSpec = 'pitt_collection.72' then add 'dcterms:isPartOfPittsburgh City Photographer Collection</dcterms:isPartOf>' to the metadata. I have a list of setSpec values with their corresponding collection names in a spreadsheet.