Skip to content
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

Read optional date ambiguity node attrs #1943

Merged
merged 1 commit into from
Mar 10, 2025

Conversation

jameshadfield
Copy link
Member

This reflects an upcoming change in Augur to export two (optional) properties within the num_date node attr. inferred: boolean and raw_value:string. There is no change to how dates are displayed for datasets without these optional values. If they are present, then showing the raw_value (ambiguous date string) is often very helpful for understanding outbreaks which may have incomplete metadata.

Visual summary of changes:

image

Related to nextstrain/augur#386

This reflects an upcoming change in Augur to export two (optional)
properties within the `num_date` node attr. `inferred: boolean` and
`raw_value:string`. There is no change to how dates are displayed for
datasets without these optional values. If they are present, then
showing the raw_value (ambiguous date string) is often very helpful
for understanding outbreaks which may have incomplete metadata.
@nextstrain-bot nextstrain-bot temporarily deployed to auspice-james-unambiguo-zo8m3p February 18, 2025 21:59 Inactive
@jameshadfield
Copy link
Member Author

nextstrain/augur#1760 allowed Augur to add these properties to the JSON, released in 29.0.0

@jameshadfield jameshadfield merged commit 46e023e into master Mar 10, 2025
18 checks passed
@jameshadfield jameshadfield deleted the james/unambiguous-dates branch March 10, 2025 20:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants