First rough mapping of a DataLad dataset export onto data-distribution
#128
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
I think this worked pretty good for a first attempt!
A number of examples have been added that roughly reflect the
compartmentalization of metadata record for storage in a datalad dataset
- annex key metadata -> Distribution
- git blob metadata -> Distribution
- git tree metadata -> Distribution
- git commit -> Resource
- this is also the anchor for provenance records
- here demo'd for a derivation from a parent commit via an unspecific
"change"
- datalad dataset (version-less) -> Resource
Structurally, `EntityInfluence` has been enhanced to accept multiple
entities. This makes specifying a homgeneous set of roles for a number
of entities more space-efficient. It also enables the annotation of
merge commits (that have multiple parent commits).
This should make the `datalad-dataset-component` schema obsolete.
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.
I think this worked pretty good for a first attempt!
A number of examples have been added that roughly reflect the compartmentalization of metadata record for storage in a datalad dataset
Structurally,
EntityInfluencehas been enhanced to accept multiple entities. This makes specifying a homgeneous set of roles for a number of entities more space-efficient. It also enables the annotation of merge commits (that have multiple parent commits).This should make the
datalad-dataset-componentschema obsolete.