Table and Column Metadata #278
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
…iption` for `get_NASIS_metadata()` and `get_NASIS_column_metadata()`
|
Merging, will replicate this approach with other functions that use the NASIS metadata |
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.
Implements new function
get_NASIS_table_metadata()which allows for retrieval of descriptions, datatypes etc. for selected NASIS tables and columns.include_descriptionforget_NASIS_metadata()andget_NASIS_column_metadata()I see being able to generate these tables as a first step towards more comprehensive metadata generation for soilDB functions that hit NASIS and SSURGO data sources--essentially known tables/columns will have their metadata filled in based on the contents of MetadataTable and MetadataTableColumn, and then calculated/derived columns will need to be filled in manually. The latter will be stored in some sort of raw data file (i.e. CSV or .rds), programmatically combined with the NASIS metadata, and then selected columns rendered in a markdown table as a component of the documentation webpage.