Import scripts for Feb 2025 E&O Open Data Release

[zlmarshall]

These are the scripts and metadata needed for the 2025 Feb ATLAS Education and Outreach Open Data Release. These are based on the recent proton-proton Research Open Data release, but with several simplified formats for various educational projects and skims that satisfy a variety of use-cases. We'll need 25 new DOIs and record IDs for this release, and we should plan for a news item as usual.

Please let me know if anything seems amiss, or if I've missed anything in here! Assigning @tiborsimko as he's helped us with the last imports, but please feel free to re-assign if appropriate.

Cheers,
Zach

[tiborsimko]

We'll need 25 new DOIs and record IDs for this release,

The record IDs could start from 93910, with the following DOIs:

# recid doi
93910 10.7483/OPENDATA.ATLAS.B5M9.44TN
93911 10.7483/OPENDATA.ATLAS.ZPCQ.9VO2
93912 10.7483/OPENDATA.ATLAS.CMHX.9D8M
93913 10.7483/OPENDATA.ATLAS.NNF8.76IX
93914 10.7483/OPENDATA.ATLAS.SCWS.LYYX
93915 10.7483/OPENDATA.ATLAS.GYRR.GRP3
93916 10.7483/OPENDATA.ATLAS.IBFR.R9L3
93917 10.7483/OPENDATA.ATLAS.L5QV.U2XC
93918 10.7483/OPENDATA.ATLAS.7UW9.C9LL
93919 10.7483/OPENDATA.ATLAS.ZXYW.FXJO
93920 10.7483/OPENDATA.ATLAS.71IP.L3OC
93921 10.7483/OPENDATA.ATLAS.6VGH.HN41
93922 10.7483/OPENDATA.ATLAS.IMZO.7U52
93923 10.7483/OPENDATA.ATLAS.OMF2.CICK
93924 10.7483/OPENDATA.ATLAS.3ATL.Q9Z2
93925 10.7483/OPENDATA.ATLAS.211Z.76E7
93926 10.7483/OPENDATA.ATLAS.CIU5.U5YX
93927 10.7483/OPENDATA.ATLAS.1P1H.J3QK
93928 10.7483/OPENDATA.ATLAS.XNPI.CX93
93929 10.7483/OPENDATA.ATLAS.KPYL.P0EE
93930 10.7483/OPENDATA.ATLAS.AR66.6RTA
93931 10.7483/OPENDATA.ATLAS.9VTD.OT28
93932 10.7483/OPENDATA.ATLAS.IPG4.6M6X
93933 10.7483/OPENDATA.ATLAS.VV3I.0WJE
93934 10.7483/OPENDATA.ATLAS.0CJR.N7ZT

[zlmarshall]

Thanks @tiborsimko ! I've pushed an update that includes those record IDs and DOIs, and seems to run locally. I think this is ready for you to try out to see if a test deployment works. Let me know if I've screwed anything up, or missed anything!

Best,
Zach

[tiborsimko]

Note that this URL does not resolve: https://opendata.atlas.cern/docs/documentation/data_format/FEB2025_ntuple/

[zlmarshall]

Yep, we are just waiting on an MR to create the page (one issue there left to resolve). If this could go ahead in the test deployment, that'd be great — we'd then want to make sure all the links are 100% working before the final deployment.

[tiborsimko]

I've pushed an update that includes those record IDs and DOIs, and seems to run locally.

Thanks, I have left some minor observations about about a broken link and a placeholder record ID,.

Looking at the ODEO records, they have at most 373 files attached. This means that we do not have to attach them via file indexes (as for record 80000), but we could attach them directly (as for record 15010).

If we do this, then we can simply amend the produced JSON snippets for files from the current format:

      {
        "checksum": "adler3204d90a6c",
        "events": 1471843,
        "filename": "opendata:ODEO_FEB2025_v0_1LMET30_data15_periodD.1LMET30.root",
        "size": 364145700,
        "type": "root",
        "uri_root": "root://eospublic.cern.ch:1094//eos/opendata/atlas/rucio/opendata/ODEO_FEB2025_v0_1LMET30_data15_periodD.1LMET30.root"
      },

to the following format:

      {
        "checksum": "adler32:04d90a6c",
        "size": 364145700,
        "uri": "root://eospublic.cern.ch//eos/opendata/atlas/rucio/opendata/ODEO_FEB2025_v0_1LMET30_data15_periodD.1LMET30.root"
      },

After that the record JSON files are directly uploadable. Here is an example of how it looks:

Would this be OK?

[zlmarshall]

Thanks @tiborsimko ! That proposed change is fine with me, and I've gone ahead and applied it in the latest update.

Cheers,
Zach