MNDeployment #2564: ORNL DAAC
Set dateUploaded date in SystemMetadata to reflect true ORNLDAAC upload dates
Many Member Nodes such as the ORNLDAAC have been curating data for years (or even decades) prior to DataONE. Therefore, for these datasets, the SystemMetadata.dateUploaded field should reflect the date when the repository first registered the dataset. Particularly, Tier I nodes such as ORNLDAAC do not implement the MNStorage.create() method, and so need to rely on the creation date of the original science metadata documents.
The following list shows ORNLDAAC identifiers and their dateUploaded values, all of which range from 2012 to 2013, which does not represent the actual upload dates to the DAAC.
Update each system metadata document on the member node with dateUploaded dates that reflect the true upload dates. Once done, contact Chris/Robert/Ben/Skye, etc. (or just firstname.lastname@example.org) to have the content re-harvested so the CNs reflect the correct dates.
#3 Updated by Chris Jones over 9 years ago
From our 04/17/2014 conference call with Bob, Giri, Ranjeet, Jim, and Laura:
We discussed the dateUploaded date, and Ranjeet and Jim said that the packages that they harvest are generated every day, and so the dataUploaded gets set to a very recent date. However, Bob said that they internally keep track of the 'ingest date' for reporting purposes. This ingest date is the date that should be set in the dateUploaded field. Ranjeet, Jim, and Giri will look into enabling this.