Complete documentation for Cassini ISS and VIMS in PDS4

[mace-space]

There are some further VIMS and ISS documents that it would be good to archive in PDS4. I forwarded @esimpson5678 the email thread between 4M's (RE: migration modifications euv/fuv (plus other Cassini docs questions)) for context but I'll summarise here (do please check I haven't missed anything):

• Documents to be included in ISS 2.0:

  • The Cassini Final Report (full report and relevant sections, see here. I'm working with Lyle (ATM) to archive these in a new "cassini-huygens" bundle.
  • Cassini-Huygens Mission (cassini-huygens-mission-description) and Cassini Orbiter (cassini-orbiter-instrument-host-description) catalog files. Similar to the point above, I'm working with Lyle (ATM) to archive these in a new "cassini-huygens" bundle
  • https://pds-rings.seti.org/holdings/documents/COISS_0xxx/VICAR-File-Format.pdf 
  • https://pds-rings.seti.org/holdings/volumes/COISS_2xxx/COISS_2116/catalog/saturnds.cat (Refer to comment from Mitch below*)
  • https://pds-rings.seti.org/holdings/volumes/COISS_1xxx/COISS_1009/catalog/jupiterds.cat (Refer to comment from Mitch below*)
  • https://pds-rings.seti.org/holdings/volumes/COISS_0xxx/COISS_0011/document/report/ (See https://seti.slack.com/archives/C03CM8FSKBJ/p1752538241607279?thread_ts=1752095701.860929&cid=C03CM8FSKBJ )
  • in_flight_cal.pdf, theoretical_basis.pdf, and iss-data-sis (but I think you've already taken care of these)
  • paper describing the End-of-mission calibration of ISS: https://doi.org/10.1016/j.pss.2020.104898.

• Documents to be included in VIMS 2.0:

  • The Cassini Final Report (full report and relevant sections, see here). I'm working with Lyle (ATM) to archive these in a new "cassini-huygens" bundle
  • Cassini-Huygens Mission (cassini-huygens-mission-description) and Cassini Orbiter (cassini-orbiter-instrument-host-description) catalog files. Similar to the point above, I'm working with Lyle (ATM) to archive these in a new "cassini-huygens" bundle
  • https://pds-rings.seti.org/holdings/volumes/COVIMS_0xxx/COVIMS_0094/catalog/dataset.cat (Refer to comment from Mitch below*)
  • vims-data-sis (but I think you've aready taken care of this).

*Here's the comment from Mitch regarding catalog files:

"For catalog files with useful information that you want to include in the PDS4 archives, I still recommend editing the catalog files by within the files removing the extraneous PDS3 overhead at the beginning and end of the file, removing “catalog” from the file names, and providing both PDF and plain text versions of each. In my view, removing the PDS3 overhead makes the files more readable and just doesn’t require much effort. The PDS4 labels should indicate the PDS3 catalog file from which the contents of the PDS4 files were extracted."

[esimpsons3ti]

Thank you for making a GitHub issue for this. Creating the references (especially in the case of the report/ directory, due to the volume of content) will take quite a bit of time.

New validation reports are generating now. I will put the new references into the labels during the lien resolution.

[esimpsons3ti]

I am adding onto this conversation from a discussion I had with Matt yesterday.

The following have already been prepared for archival into PDS4:

• The SIS files for ISS and VIMS (edrsis and dpsis)

Somehow, I thought I already prepared in_flight_cal.pdf and theoretical_basis.pdf, but somehow they are no longer there.

I am going to prepare the labels and documents for the single files.

How should I go about referencing the /report directory?

[mace-space]

There are several sections in the report/ directory. Each section (provided as HTML or PDF) could be described by a separate Document_File:

<Document>
    <document_name>...
    <doi>...
    ...
    <document_editions>...
   ...
    <Document_Edition>
   ...
  </files>n</files> 
  ...
<Document_File>
<file_name>...
 ...
 ... 
<document_standard_id> <!-- This can be HTML, PDF, PDF/A etc. Although the HTML and PDF would have to be converted into a PDS4-compliant format too -->
</Document_File>
<Document_File>
 ...
</Document_File>
<Document_File>
...
</Document_File>
... etc...
</Document_Edition>
...etc

refer to IM Specs.

Alternatively, if the amount of work to do this is deemed excessive, perhaps an External_Reference could be used to reference the report/, along with a description from the Acknowledgments section?

The SR (8A.3) states:

For archive integrity, it is preferable to have all relevant documentation within the archive; in
many cases, however, this is either impractical or impossible. For example, when a copyright
holder refuses re-use, the copyrighted material must be referenced through an outside source.
The Reference_List class may be used to point toward relevant material or source products either
inside or outside PDS. It may be associated with any of over two dozen different product classes
including Product_Context, Product_Document, Product_Collection, and Product_Browse. ...

There's a paper describing the End-of-mission calibration of ISS: https://doi.org/10.1016/j.pss.2020.104898, which I think should be referenced too by an External_Reference.

What are your thoughts, @matthewtiscareno?

[matthewtiscareno]

Wow, that directory is quite a piece of work. You can't easily see the directory's contents because there is a index.html file that causes your browser to go straight to interpreting it as a webpage. However, looking at it with the command line on Admin, there is in fact a single PDS label, namely isscalrpt.lbl. Could we have just one External_Reference that points to this label?

By the way, the label points to isscalrpt.htm, which (I've verified via a diff command) is exactly identical to the index.html file.

[mace-space]

Wow, thanks for spotting that! isscalrpt.lbl is very minimal so I'm not sure that would be particularly useful. Having the External_Reference point to the index.html / isscalrpt.htm is another option, with a comment saying that this is the homepage with several other sections linked. However, my preference would be for the External_Reference to link to the full report/ directory with a note describing the contents, including the index.html.

[matthewtiscareno]

It seems like a pretty subtle difference for the External_Reference to point to the directory, or the label, or the HTML file. Whichever seems good to you is fine with me.

[mace-space]

I suggested the directory as that makes it a bit clearer to the user that the report isn't in a single file, but as long as the <description> of the <External_Reference> clearly outlines the contents of the calibration report, I don't really have strong opinions.

[mace-space]

Also, Matt and I agree that the journal article (https://doi.org/10.1016/j.pss.2020.104898) should also be included as an External_Reference.

(I'm editing the initial post to include this in the listed documents.)

[esimpsons3ti]

Okay. What would you like the journal article to be called when it's placed in the documents directory?