dspace fix #1910
Closed
dspace fix #1910
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
cstarcher
requested changes
Mar 11, 2024
There was a problem hiding this comment.
The dc.date.issued date in the DSpaceMETS export is still formatted as Month YYYY.
This PR is changing the following:
DSpaceMETS (mets.xml)
dc.date.created from YYYY-MM to YYYY-MM-DD
dc.date.submitted from Month YYYY to YYYY-MM-DD
DSpaceSimple (dublin_core.xml)
dc.date.created from Month YYYY to YYYY-MM-DD
dc.date.issued from YYYY-MM to YYYY-MM-DD.
The solution for #1911 should only change the dc.date.issued date format in the DSpaceMETS mets.xml file to YYYY-MM.
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.
DSpaceMETS dc.date.issued date rendered as iso8601 format