One step before a user submit a data set to NCEI

[lqjiang]

Hi Linus,

Would you please consider adding the below steps before a user click the data submission button?

Please choose how your data set should be published at NCEI: 1: Publish the data package as a new data package (A new NCEI accession will be created)

2: Publish the data package as a revision to an existing data package at NCEI (Both the metadata and data files of the existing NCEI data package will be replaced with the new ones)

3: Append the new data package to an existing data package at NCEI. (The metadata file of the new data package will be merged with the existing one, the new data files will be added to the current pool of data files)

If a user chooses option 2 or 3, the below question will appear: Please input the Accession number or DOI of the existing NCEI data package (or Accession) [ (please fill in here) ]. There will be an option of "unknown". (If you choose "unknown", NCEI will find the existing NCEI Accession related to this data set for you).

Many thanks for your consideration,

Liqing

[eugeneburger]

Liqing,

Firstly - happy new year! Or is it happy spring festival - my apologies if I got this wrong.

This is a very timely comment, and one we have considered ourselves. Thank you for the broader context. I'm sure we'll have more questions on this as we consider the implementation.

I assume the answer is no, but is there a mechanism for SDIS to acquire through a machine to machine call the list of accession numbers of data hosted in OCADS?

Best Eugene

[lqjiang]

Hi Eugene,

Many thanks for the kind words about the Chinese New Year. We say Happy New Year to each other, but the holiday is called a spring festival :-)

Glad to hear we're aligned well in terms of this suggestion. As to your question in terms of the list of Accessions at NCEI, it will be a super long list from 0 - about 2500000. It will be too long to be useful. If you are thinking of OA related Accession numbers, we'll have a list of about

2000. I think it will be more helpful to include a link to the OCADS Portal https://www.ncei.noaa.gov/access/oads/, so that a user can search for the relevant data sets themselves.

Liqing

On Thu, Feb 11, 2021 at 11:37 PM Eugene Burger notifications@github.com wrote:

Liqing,

Firstly - happy new year! Or is it happy spring festival - my apologies if I got this wrong.

This is a very timely comment, and one we have considered ourselves. Thank you for the broader context. I'm sure we'll have more questions on this as we consider the implementation.

I assume the answer is no, but is there a mechanism for SDIS to acquire through a machine to machine call the list of accession numbers of data hosted in OCADS?

Best Eugene

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NOAA-PMEL/OAPDashboard/issues/29#issuecomment-777964336, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABY2ZWYRSFBKHPOQZD3YV33S6SV6VANCNFSM4XNUXP5A .

[lkamb]

Hi Liqing,

This was something we had considered, and in fact was just asked about in one of our demos.

Another suggestion was to accept the URL for the NCEI landing page for the submitted dataset as an option as the identifier.

This should not be too hard to do from my end. We'll have to agree how this is communicated, but I'm assuming another entry in the SubmissionInstructions.txt file. (I'm really thinking that we need to replace or restructure that file to be more structured and machine-readable, as it is getting more and more overloaded from its original role of communicating the optional user comment.)

[lqjiang]

Thanks, Linus!

Has John subscribed to the SDIS GitHub list? If not, would you please make sure he does.

As to how the info is communicated to NCEI, I'll leave it to you and John to decide. My recommendation is to add a set of tags like the below to the metadata XML file. After all, this is some critical information to have.

Note, r2a is short for Request to Archive.

New, or Revision, or Accumulation

Liqing

On Fri, Feb 12, 2021 at 11:59 AM Linus Kamb @ NOAA notifications@github.com wrote:

Hi Liqing,

This was something we had considered, and in fact was just asked about in one of our demos.

Another suggestion was to accept the URL for the NCEI landing page for the submitted dataset as an option as the identifier.

This should not be too hard to do from my end. We'll have to agree how this is communicated, but I'm assuming another entry in the SubmissionInstructions.txt file. (I'm really thinking that we need to replace or restructure that file to be more structured and machine-readable, as it is getting more and more overloaded from its original role of communicating the optional user comment.)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NOAA-PMEL/OAPDashboard/issues/29#issuecomment-778315199, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABY2ZW4P74TNW6VVI7X5GY3S6VM7JANCNFSM4XNUXP5A .

[lkamb]

I would argue that this information is not metadata about the Dataset, but rather about the Submission, and as such does not belong in the Metadata XML.

[lqjiang]

Hi Linus,

That will be fine.

Please feel free to work with John to find the best way to convey the info to his automation program.

Liqing

On Tue, Feb 16, 2021 at 11:13 AM Linus Kamb @ NOAA notifications@github.com wrote:

I would argue that this information is not metadata about the Dataset, but rather about the Submission, and as such does not belong in the Metadata XML.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NOAA-PMEL/OAPDashboard/issues/29#issuecomment-779942182, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABY2ZW5U2SUEWEVQVAKSMNTS7KKTDANCNFSM4XNUXP5A .