-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Corresponding nextstrain PR <nextstrain/nextstrain.org#719>
- Loading branch information
1 parent
87a0c76
commit eaac099
Showing
5 changed files
with
148 additions
and
1 deletion.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,144 @@ | ||
================================= | ||
Viewing previous versions of data | ||
================================= | ||
|
||
|
||
.. contents:: Sections in this document | ||
:local: | ||
:depth: 2 | ||
|
||
|
||
Overview | ||
======== | ||
|
||
Analyses are a snapshot in time, and for most of our `core Nextstrain datasets | ||
<https://nextstrain.org/pathogens>`__ we update this snapshot frequently, | ||
sometimes daily. When you view a dataset such as the seasonal influenza build | ||
`flu/seasonal/h3n2/ha/6y <https://nextstrain.org/flu/seasonal/h3n2/ha/6y>`__ you | ||
can see in the header of the page that it's been updated sometime in the last | ||
week or so. Because we update this every week, we have a large archive of past | ||
updates which we can go view; if we want to view the snapshot from mid way | ||
through 2023, we can load `flu/seasonal/h3n2/ha/6y@2023-07-01 | ||
<https://nextstrain.org/flu/seasonal/h3n2/ha/6y@2023-07-01>`__, which will load | ||
the latest available snapshot on July 1st, which was a dataset updated on June | ||
30. | ||
|
||
In general, appending a ``@YYYY-MM-DD`` string to a Nextstrain core dataset URL | ||
will load the dataset that was the latest available at that particular date. | ||
|
||
.. note:: | ||
|
||
This functionality is newly introduced in early 2024 and is currently only | ||
available for core Nextstrain datasets. There is not yet a way to see a list / | ||
visualise all the available datasets, but this is in the works. | ||
|
||
|
||
Tanglegrams to compare changes | ||
------------------------------ | ||
|
||
Using tanglegrams allows us to easily view two different versions of the same | ||
dataset side-by-side. Using the above examples we can view the latest dataset | ||
against the one from the middle of 2023 via the URL | ||
`flu/seasonal/h3n2/ha/6y:flu/seasonal/h3n2/ha/6y@2023-07-01 | ||
<https://nextstrain.org/flu/seasonal/h3n2/ha/6y:flu/seasonal/h3n2/ha/6y@2023-07-01>`__. | ||
Here's a screenshot of this taken in early January 2024, allowing us to see the | ||
expansion of clade 2a.3a.1 over the past 6 months: | ||
|
||
.. image:: ../images/versions-tanglegram-h3n2.jpg | ||
:alt: Tanglegram of flu/seasonal/h3n2/ha/6y:flu/seasonal/h3n2/ha/6y@2023-07-01 | ||
|
||
Over time, the data shown by this URL link will start to change as we update the | ||
latest version, but by versioning both datasets we can preserve this exact view | ||
into the data: | ||
`flu/seasonal/h3n2/ha/6y@2024-01-03:flu/seasonal/h3n2/ha/6y@2023-07-01 | ||
<https://nextstrain.org/flu/seasonal/h3n2/ha/6y@2024-01-03:flu/seasonal/h3n2/ha/6y@2023-07-01>`__. | ||
|
||
|
||
SARS-CoV-2 datestamped datasets | ||
------------------------------- | ||
|
||
Prior to the functionality described here we exposed dated versions of some of | ||
our datasets by including the YYYY-MM-DD in the URL without the ``@`` character, | ||
i.e. the date string was part of the dataset name. This functionality is now | ||
superseded by the new URL syntax described here, and we may stop producing these | ||
kinds of dated dataset names in the future. | ||
|
||
As an example, and to highlight an improvement with the new approach, you can | ||
access the ``ncov/gisaid/21L/global/6m`` SARS-CoV-2 build from Jan 9th 2024 | ||
using either the new (and preferred) syntax | ||
`ncov/gisaid/21L/global/6m@2024-01-09 | ||
<https://nextstrain.org/ncov/gisaid/21L/global/6m@2024-01-09>`__ or | ||
`ncov/gisaid/21L/global/6m/2024-01-09 | ||
<https://nextstrain.org/ncov/gisaid/21L/global/6m/2024-01-09>`__. If we now look | ||
at Jan 10th, when we didn't update the data, we see that | ||
`ncov/gisaid/21L/global/6m@2024-01-10 | ||
<https://nextstrain.org/ncov/gisaid/21L/global/6m@2024-01-10>`__ still works | ||
(returning the latest dataset availbale at that time) while | ||
`ncov/gisaid/21L/global/6m/2024-01-10 | ||
<https://nextstrain.org/ncov/gisaid/21L/global/6m/2024-01-10>`__ doesn't exist | ||
(404). | ||
|
||
|
||
Details for dataset maintainers | ||
=============================== | ||
|
||
.. note:: | ||
|
||
This section is more technical and aimed primarily at those managing datasets. | ||
|
||
Time zones | ||
---------- | ||
|
||
All times are UTC. A datestamp refers to datasets uploaded between 00h00 | ||
and 23h59 UTC on that day. | ||
|
||
|
||
S3 Delete Markers | ||
----------------- | ||
Our core datasets are all stored in a versioned S3 bucket, which is how we are | ||
able to provide this functionality. When files are "deleted" from a versioned | ||
bucket, the normal behaviour is to preserve the file but add a `delete marker | ||
<https://docs.aws.amazon.com/AmazonS3/latest/userguide/DeleteMarker.html>`__. | ||
When looking back at versions over time, we interpret the intended behaviour of | ||
a delete marker as removing the then-latest file from history, so it wont be | ||
available via any ``@YYYY-MM-DD`` value. | ||
|
||
.. image:: ../images/delete-markers.png | ||
|
||
|
||
What about if the URL changed over time? | ||
---------------------------------------- | ||
|
||
We've often changed the URL which (core) datasets appear at, for instance we | ||
recently changed the URL for `/dengue/denv1 | ||
<https://nextstrain.org/dengue/denv1>`__ to `dengue/denv1/genome | ||
<https://nextstrain.org/dengue/denv1/genome>`__, with the former now redirecting | ||
to the latter. The result of this is that the earliest available | ||
``dengue/denv1/genome`` dataset is from 2024-01-03, despite DENV1 datasets being | ||
available since January 2019. | ||
|
||
We have plans to expose these versions - see `this issue | ||
<https://github.com/nextstrain/nextstrain.org/issues/777>`__ for progress here. | ||
|
||
|
||
Multiple datasets uploaded on the same day | ||
------------------------------------------ | ||
|
||
If multiple datasets are uploaded on the same day we take the most recent. If | ||
there are v1 and v2 Auspice dataset JSONs then we will always take the v2 | ||
dataset over the v1 dataset. | ||
|
||
|
||
Sidecar files | ||
------------- | ||
|
||
Sidecar files must have been uploaded on the same day as the dataset JSON (or | ||
meta+tree JSONs in the case of v1 datasets). | ||
|
||
|
||
How far back does this go? | ||
-------------------------- | ||
|
||
The oldest versioned dataset `is a H3N2 dataset from August 2018 | ||
<https://nextstrain.org/flu/seasonal/h3n2/ha/3y@2018-08-01>`__. While Nextstrain | ||
datasets existed before then, we didn't have versioning enabled. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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
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