-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metadata changes (v0.4) #241
Merged
Merged
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
- List them as table on metadata page - Update profile to list properties in same order - Update example and include all properties - title - description - version - keywords - image (empty) - homepage (empty) - rightsHolder - bibliographicCitation - references (empty) - Fix incorrect link to 0.2
Fix #230, update example to make use of this + add coordinateUncertainty
Fix #230, update example to make use of this + add coordinateUncertainty
…into metadata_changes
- Requires every property to be added to camtrap-dp-profile.json, with a description
- Done for data and metadata - Includes: - constraints.required - constraints.minimum - constraints.maximum - constraints.unique - constraints.enum - const - enum - items.enum Fix #226
peterdesmet
force-pushed
the
metadata_changes
branch
from
October 5, 2022 06:38
ace6ab7
to
b797b11
Compare
- Reference terms in `backticks` - Use "package", not Data Package - Move examples below type (in profile) - Refer to other fields via table.fields t
Closes #27 - Add custom property `version`, but see suggestion to include in main specs: frictionlessdata/datapackage#808 - Update example
peterdesmet
force-pushed
the
metadata_changes
branch
from
October 5, 2022 10:00
704bc21
to
600bb4b
Compare
peterdesmet
added
documentation
Improvements or additions to documentation
level:package
labels
Oct 5, 2022
Impressive work @peterdesmet! |
kbubnicki
approved these changes
Oct 10, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
documentation
Improvements or additions to documentation
level:package
term:deprecate
term:new
term:update
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.
This PR includes a lot of work:
Changes to Camtrap DP
rightsHolder
Deprecate rightsHolder #202platform
in favour ofsources
Should platform metadata go in sources? #27organizations
in favour ofcontributors
Should organizations be bundled incontributors
#235relatedIdentifiers
using DataCite properties Add related identifiers in metadata, cf. DataCite #236coordinatePrecision
AddcoordinatePrecision
property to metadata #230project.animalTypes
to a booleanproject.individualAnimals
ChangeanimalTypes
to boolean field #232package.project.references
topackage.references
Purpose of references? #116Textual changes to the metadata page
metadata.md
. This does require all properties to be listed incamtrap-dp-profile.json
, including the ones we are not extending in Camtrap DP. I think that is a good thing, since you can now see everything in context. For those properties, I added only added adescription
, which links to the generic specs + allows to clarify some things (Documentpackage$title
#233)Extend the example data package to include all relevant properties and serve as a better example
Have a distinct logical order for the metadata properties. This is mainly based on how properties are listed in a Zenodo metadata page:
Show deep controlled vocabs Mention vocabs for captureMethod, animalTypes on website #226
Show
const
valuesShow all constraints together (including on "Data") page: