You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently only have a single _timestamp = 2023-05-12T14:48:11.983Z attribute in the ESGF index. This needs to be unique for every dataset, such that when a new replica (the same dataset, bit for bit) is republished, the original timestamp is preserved. A new e.g. _timestampReplica1 = 2023-12-12T19:48:11.983Z is generated allowing for this original version/timestamp to be used persistently, e.g. in the data citation/license info etc.
Just catching up on this. the issue title might be better rewritten to express the concern. _timestamp is always unique because it reflects the index-assigned timstamp at a sub-second granularity. What we want in the publisher is to write the original creation time of the record to the replica record? IIRC from our chat at AGU?
eg. original_timestamp
We currently only have a single
_timestamp = 2023-05-12T14:48:11.983Z
attribute in the ESGF index. This needs to be unique for every dataset, such that when a new replica (the same dataset, bit for bit) is republished, the original timestamp is preserved. A new e.g._timestampReplica1 = 2023-12-12T19:48:11.983Z
is generated allowing for this original version/timestamp to be used persistently, e.g. in the data citation/license info etc.Example from https://esgf-node.llnl.gov/search/input4mips/?institution_id=PCMDI&source_id=PCMDI-AMIP-1-1-9
@MartinaSt @wolfiex @SebastienDenvil @sashakames ping
The text was updated successfully, but these errors were encountered: