-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add identifiers table to traits.build output #195
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
* Code to add a table of identifiers is working - tested so far with a single column of identifiers, but workflow should work for any number of identifiers * Next steps: - test with multiple identifier columns - rework `metadata_create_template` to add identifiers - create function `metadata_add_identifiers` to propagate identifier section of metadata.yml - write tests - edits to lots of austraits functions since now list is 1 longer; need to create function to join in identifiers
Add identifiers to remaining part of schema
Add new function for adding identifiers to metadata files
To avoid people having to retrofit existing metadata files to include identifiers, if identifiers is missing from the metadata file, a blank metadata tibble is added during processing.
3 old tests not passing, but some might be because running new austraits, but accompanying traits.build changes not on this branch.
All old tests now passing with new `identifiers` table. Next need to add tests and identifiers permutations to test datasets.
further edits to schema to capture most likely identifier types used. At least for a while, these will be a suggested list, rather than a controlled vocabulary - as in an identifier types can be used, but only these will be suggested by the function `metadata_add_identifiers`.
Added another test, confirming datasets build with "non-controlled identifiers" - good to include, since we don't yet fully know what people want to have Few other formatting changes, update documentation
- identifiers table contained rows for which there wasn't a trait value (blanks filtered from traits table after identifiers table detached as its own table)
Specify austraits branch that goes with this traits.build branch
Removing automatically added zeros
ehwenk
commented
Jan 28, 2025
ehwenk
commented
Jan 28, 2025
ehwenk
commented
Jan 28, 2025
ehwenk
commented
Jan 28, 2025
ehwenk
commented
Jan 28, 2025
- add mistakenly reverted some file renamings - add `austraits::` in report dataset
dfalster
approved these changes
Jan 29, 2025
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.
Add a dataframe to a traits.build output that documents "identifiers" that link specimens/individuals/etc. across datasets and to museum/herbarium collections.
Six types of identifiers have been added to the traits.build schema, reflecting key identifiers types specified by DarwinCore. This is not a comprehensive list of all DarwinCore identifiers - but instead of adding others, this seems like a good starting point, and traits.build has been coded to NOT throw an error is a different
identifier_type
is used.Note,
catalog_number
is for non-universal identifiers that represent an individual researchers plant tag system whilecollectionID
andmaterialSampleID
are meant to be universally unique identifiers.Notes:
identifiers
section, so people already using traits.build do not need to retrofit their metadata filesI don't understand why changes that were previously pushed to master are appearing here. For instance, the renaming of functions. Confirming this pull request is from
add_specimen_ID
branch todevelop