Keep the Juno SRU volume up-to-date in the PDS3 holdings

[mseritan]

Our PDS3 holdings do not include the volume JNOSRU_0001. (I believe that this is currently the only volume of data from the SRU, and it is downloadable from the IMG website.) This issue covers the task of downloading this volume, putting it into our holdings, and generating all the associated archive/checksum/shelf/etc. files.

[mseritan]

The JNOSRU_0001 volume has been downloaded from the IMG website and put into holdings on pdsdata-admin, and all its auxiliary files (archives, checksums, shelf files, etc.) have been generated.

Next up: @markshowalter and I will figure out how to generate metadata for this volume. Once the metadata is complete and all the metadata auxiliary files have been generated, then we will sync to pdsdata-staging.

[mseritan]

The volset/volume JNOSRU_0xxx/JNOSRU_0001 currently exists on pdsdata-admin. The auxiliary files for the volume have been created, but no metadata (and thus no metadata auxiliary files) have been created. Nothing for SRU exists on pdsdata-staging or pdsdata-production yet.

The volume directory on pdsdata-admin was created on 7/8/2025 and modified on 8/20/2025. On the IMG website, the "Last modified" date for the SRU volume is 7/8/2025. It appears that the volume JNOSRU_0001 gets overwritten with a new version, rather than additional volumes (ex. JNOSRU_0002 and etc.) being added to the IMG website.

I need to check if the SRU volume that we currently have on pdsdata-admin is current or not before proceeding with metadata generation with Mark.

I currently check monthly for any updates to the SRU volume on the IMG website. I will keep this issue open when I am actively updating the SRU data in our holdings, close the issue when it's up-to-date, and then reopen the issue when I see that there is updated SRU data to add. I've also changed the title of the issue to reflect this use.

[mseritan]

I've assigned @markshowalter since we will work on metadata generation together.

[mseritan]

As of Tuesday 10/14: the JNOSRU_0001 volume that is currently on pdsdata-admin covers through orbit 68, while the JNOSRU_volume on the IMG website covers through orbit 71.

[mseritan]

The newest version of the SRU volume is now on admin. We have decided to version the old versions of the volume via the volset name, ex:

JNOSRU_0xxx/JNOSRU_0001 contains the latest version of the volume
JNOSRU_0xxx_v1/JNOSRU_0001 contains the previous version of the volume

Next up is to (1) generate the auxiliary files (paying attention to the versioning on the old version), (2) create my first pass of the metadata generation script that Mark gave me notes on during our meeting on Monday.

[matthewtiscareno]

We noticed today that Orbits 1 through 35 (that is, the Juno prime mission) are missing from the Juno SRU volume. I emailed Heidi Becker about this, and I even asked whether PDS could take on the task of archiving the prime mission data (we could ask for an overguide) if Juno has no funding to do so. Heidi's response was:

We are awaiting direction from NASA. You can direct these types of questions on Juno to Scott Bolton

[mseritan]

The holdings have been updated to include the new version of JNOSRU_xxxx (and the old one was versioned to be JNOSRU_xxxx_v1). Both are now available on Viewmaster.

[mseritan]

The Juno SRU volume was updated on 29 April 2026, so I am reopening this issue until I've gotten the updated volume into our holdings.