Clarification for the meaning of the Date_Type column #68
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 will add some more clarification in the verbose interpretation of the schema on the website. |
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.
After some confusion about the age information columns (see e.g. poseidon-framework/community-archive#146 (comment) and poseidon-framework/poseidon-hs#283 (comment)) I would like to suggest a clarification for the description in schema version 2.7.1.
Note the emphasis I put on usability for derived, computational analysis. My idea is as follows: If the
Date_Typefield is set toC14, then the date(s) inDate_C14_Uncal_BPandDate_C14_Uncal_BP_Errshould be directly useful for derived modelling. If, on the other hand, the age of a sample is only vaguely informed by a radiocarbon date from a stratigraphically related layer, then this is contextual (!) information that does not have to be listed in the .janno file, but only indirectly feeds into the contextual age columnsDate_BC_AD_Start,Date_BC_AD_MedianandDate_BC_AD_Stop.