Zenodo and DOI

[aidanheerdegen]

I have created a draft Zenodo record for ACCESS-ESM1.6:

https://zenodo.org/records/17490073

IT IS NOT COMPLETE!

The decision has been made to use organisations for the creator and contributor fields for the model deployment, and have more granular individual credit for records covering the model components and configurations.

I need some input for funding sources (I guess CSIRO needs to namecheck NESP?) and anything else that might be missing.

Once we're happy I'll also create a PR to add a citation.cff file which captures all the relevant information, and hook the repo up to Zenodo to automate the creation of DOIs for each release.

Note at this stage the plan is to have the DOI creation after release, so we'll be using the top level concept DOI until we can put in place a workflow that automates reserving a DOI and embedding it in the citation.cff prior to tag and release steps.

[ccarouge]

My main comment on the Zenodo record is why do we copy information that I would think would rather live within the ESM1.6 config docs? Obviously, I imagine the same template would be used for all the released models and it seems a lot of duplication. I would assume we would rather want to push people to open our docs, and increase the traffic on the docs website.

[aidanheerdegen]

My main comment on the Zenodo record is why do we copy information that I would think would rather live within the ESM1.6 config docs? Obviously, I imagine the same template would be used for all the released models and it seems a lot of duplication. I would assume we would rather want to push people to open our docs, and increase the traffic on the docs website.

Oh right. I just copied some stuff in there. We can remove all that and point to the ACCESS Hive Docs.

Any suggestion on what we should have there?

[ccarouge]

I'll work on the configs docs and let you know when we know what's in the configs docs :D

[aidanheerdegen]

From @pearseb

WOMBAT was supported by the AAPP. The official statement for this is:

“This research has been supported by the Australian Government as part of the Antarctic Science Collaboration Initiative (ASCI) program.“

[aidanheerdegen]

Edit: I should read more carefully, @pearseb pointed out it was funded by AAPP

Seems ASCI funded the AAPP

https://www.grants.gov.au/Go/Show?GoUuid=10e0ee4a-c9c3-cca0-6f46-d3a8845385ef

https://aappartnership.org.au/about_us/

The Australian Antarctic Program Partnership (AAPP) is a ten-year Australian Government funded initiative through the Antarctic Science Collaboration Initiative program to better understand the role of the Antarctic region in the global climate system and the implications for marine ecosystems.

[har917]

@rml599gh or Tilo will be the best placed to provide the official wording for the NESP support.

NESP are also looking to facilitate tracking of output - this involves embedding a number of identifiers in as many outputs as possible (to allow cross-tracking). Examples are

• Research Organisation Records (RORs)
• ORCIDs for individuals
• partner dois
• Research Activity Identifiers (RAID)*

The RAID for the NESP project will be set up shortly - but since RAIDs are a fairly new concept we've been informed that Zenodo doesn't easily facilitate these (yet) - basically a work in progress and maybe we won't be able to include that anywhere.

[access-hive-bot]

This issue has been mentioned on ACCESS Hive Community Forum. There might be relevant details there:

https://forum.access-hive.org.au/t/csiro-access-nri-standup-minutes/3789/62

[rml599gh]

@aidanheerdegen - suggest we chat about this next week.

[rml599gh]

Can the title of the Zenodo record be 'ACCESS-ESM1.6 release' rather than just 'ACCESS-ESM1.6'? This would seem to be consistent with ACCESS-NRI being listed as the project leader.

[aidanheerdegen]

Can the title of the Zenodo record be 'ACCESS-ESM1.6 release' rather than just 'ACCESS-ESM1.6'? This would seem to be consistent with ACCESS-NRI being listed as the project leader.

Good point. Done.

Any other CSIRO funders etc we need to include?

Still need to chat about this @rml599gh?