Add fallback for dct:issued and dct:modified in resources #233
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
|
This makes sense @seitenbau-govdata , can you merge the latest master branch? that should fix the lint testing issues |
seitenbau-govdata
force-pushed
the
add-fallback-for-resource-dates
branch
from
b56ac69 to
2f22fc3
Compare
seitenbau-govdata
force-pushed
the
add-fallback-for-resource-dates
branch
from
2f22fc3 to
01d40c5
Compare
|
@amercader Done. The pull request is now based on the current master. Thanks for fixing the testing issues. |
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.
We'd like to add a fallback for the serialization of the resource dates dct:issued and dct:modified, in the same way it is implemented for the dataset. To do so we use the CKAN internal dates created and metadata_modified of the resource.