Add a Data Package serializer #10632
Open
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.
Purpose
Data Package is a European Commission-funded project (via NLnet) that is a standard containing a set of lightweight specifications for describing datasets and individual data files. The standard is widely used for data interoperability in other data portal systems like CKAN, Dryad, Our World in Data, and others. The main benefit of adoption the Data Package Standard is a rich set of software for reading and validating datasets - https://datapackage.org/standard/software/ (the most advanced implementations are in Python and R, as well as a Desktop application).
By creating this pull request, we would like to bootstrap a discussion if OSF would consider accepting the
datapackage.jsonformat to be one of the export targets for datasets' metadata. Also, tagging our friends from the University of California @sdiggs and @sapetti9 from Open Knowledge Foundation.Thanks a lot in advance!
Changes / QA Notes
It only adds a new serializer without touching the existent code. Also, it exposes the new serializer in the
osf.metadata.serializers.METADATA_SERIALIZER_REGISTRYDocumentation
Can you please help with identifying whether some docs need to be updated?
Side Effects
No
Ticket
No