*** dfms_ts_abundance ***

data_description.pdf
- This is PDF/A-2b, not -1a or -1b.

inventory.csv
- Suggestion: name this file collection.csv or collection_inventory.csv,
per PDS4 Standards section 2B.2.2.2



*** document ***

collection.xml
- For lid_references to 
  urn:nasa:pds:context:instrument:liciacube.leia
  urn:nasa:pds:context:instrument:liciacube.luke
please provide those context products to EN if/when ready



*** leia_calibrated ***

collection.xml
- For lid_references to 
  urn:nasa:pds:context:instrument:liciacube.leia
please provide those context products to EN if/when ready

inventory.csv
- Suggestion: name this file collection.csv or collection_inventory.csv,
per PDS4 Standards section 2B.2.2.2



*** leia_raw ***

collection.xml
- For lid_references to 
  urn:nasa:pds:context:instrument:liciacube.leia
please provide those context products to EN if/when ready

inventory.csv
- Suggestion: name this file collection.csv or collection_inventory.csv,
per PDS4 Standards section 2B.2.2.2



*** luke_calibrated ***

collection.xml
- For lid_references to 
  urn:nasa:pds:context:instrument:liciacube.luke
please provide those context products to EN if/when ready
- The following LID is unknown - is this lid_reference correct:
  urn:nasa:pds:liciacube:luke_derived:luke_calibrated_overview
The leia_calibrated file had a lid_reference to
  urn:nasa:pds:liciacube:leia_calibrated:leia_calibrated_overview
If this is what's intended, please ensure that file exists someday.

inventory.csv
- Suggestion: name this file collection.csv or collection_inventory.csv,
per PDS4 Standards section 2B.2.2.2



*** luke_raw ***

collection.xml
- For lid_references to 
  urn:nasa:pds:context:instrument:liciacube.luke
please provide those context products to EN if/when ready

inventory.csv
- Suggestion: name this file collection.csv or collection_inventory.csv,
per PDS4 Standards section 2B.2.2.2

prelaunch/liciacube_luke_l0_0717839687_18230_01.xml
- The image looks odd given the values (many lines removed)
      <Element_Array>
        <data_type>UnsignedByte</data_type>
      <Axis_Array>
        <elements>2048</elements>
      <Axis_Array>
        <elements>1088</elements>
Changing those to
      <Element_Array>
        <data_type>UnsignedMSB2</data_type>
      <Axis_Array>
        <elements>544</elements>
      <Axis_Array>
        <elements>2048</elements>
produces a better image since the .fits file seems to have two-byte data:
  ...
  00001680: 2d1c 2d1d 2e1d 2d1d 2d1d 2e1d 2e1d 2d1c
  00001690: 2e1d 2d1c 2d1d 2f1d 2e1c 2d1f 2d1c 2d1e
  ...
The original 1-byte and the modified 2 are attached: lukeraw1.jpg, lukeraw2.jpg



*** mbc_gn ***

.../*.xml
- Suggestion: add lid_references to targets. Data labels have something like
  <Target_Identification>
    <name>238P/2005 U1 (Read 3)</name>
    <type>Comet</type>
  </Target_Identification>
If requested, EN can create a LID and context product for each comet, allowing
  <Target_Identification>
    <name>238P/2005 U1 (Read 3)</name>
    <type>Comet</type>
    <Internal_Reference>
      <lid_reference>urn:nasa:pds:context:target:comet.238p_read</lid_reference>
      <reference_type>data_to_target</reference_type>
    </Internal_Reference>
  </Target_Identification>
This would allow searches for the target at pds.nasa.gov to return this
collection. It would also lengthen collection.xml though, as lid_references
to context products should bubble up.

inventory.csv
- Suggestion: name this file collection.csv or collection_inventory.csv,
per PDS4 Standards section 2B.2.2.2

overview.pdf
- not PDF/A-1a or -1b



*** mbc_gs ***

.../*.xml
- Suggestion: add lid_references to targets. Data labels have something like
  <Target_Identification>
    <name>176P/1999 RE70 (LINEAR 52)</name>
    <type>Comet</type>
  </Target_Identification>
If requested, EN can create a LID and context product for each comet, allowing
  <Target_Identification>
    <name>176P/1999 RE70 (LINEAR 52)</name>
    <type>Comet</type>
    <Internal_Reference>
      <lid_reference>urn:nasa:pds:context:target:comet.176p_linear</lid_reference>
      <reference_type>data_to_target</reference_type>
    </Internal_Reference>
  </Target_Identification>
This would allow searches for the target at pds.nasa.gov to return this
collection. It would also lengthen collection.xml though, as lid_references
to context products should bubble up.

inventory.csv
- Suggestion: name this file collection.csv or collection_inventory.csv,
per PDS4 Standards section 2B.2.2.2

overview.pdf
- not PDF/A-1a or -1b



*** shapemodel ***

collection.xml
- For lid_references to 
  urn:nasa:pds:context:instrument:liciacube.leia
  urn:nasa:pds:context:instrument:liciacube.luke
please provide those context products to EN if/when ready

inventory.csv
- Suggestion: name this file collection.csv or collection_inventory.csv,
per PDS4 Standards section 2B.2.2.2

model01/*grv*.xml
model01/*nvf*.xml
- Record_Binary/fields = 6 should be 10

model01/g_08440mm_spc_dtm_dimo_0000n00000_v002.fits
- The xml label for this file wasn't given, oddly.

model01/l_08575mm_spc_obj_dimo_1325s10722_v002.xml
- The header, as defined, overlaps the data table:
    <Header>
       <offset unit="byte">0</offset>
       <object_length unit="byte">2916</object_length> [...]
    </Header>
    <Table_Character>
      <local_identifier>VERTEX_TABLE</local_identifier>
      <offset unit="byte">2909</offset>
I think the right solution is to change header/object_length
       <object_length unit="byte">2909</object_length> [...]



*** shapemodeldoc ***

collection.xml
- For lid_references to 
  urn:nasa:pds:context:instrument:liciacube.leia
  urn:nasa:pds:context:instrument:liciacube.luke
please provide those context products to EN if/when ready

dart_coordinate_system_for_didymos_and_dimorphos_v1.pdf
- This is PDF/A-2b, not -1a or -1b.



*** swan_derived ***

.../*.xml
- Unfortunately, the LID for the mission is wrong.
  urn:nasa:pds:context:investigation:mission.moho
should be
  urn:nasa:pds:context:investigation:mission.solar_and_heliospheric_observatory
- Suggestion: add lid_references to targets. Data labels have something like
  <Target_Identification>
    <name>2P/1818 W1 (Encke)</name>
    <type>Comet</type>
  </Target_Identification>
If requested, EN can create a LID and context product for each comet, allowing
  <Target_Identification>
    <name>2P/1818 W1 (Encke)</name>
    <type>Comet</type>
    <Internal_Reference>
      <lid_reference>urn:nasa:pds:context:target:comet.2p_encke</lid_reference>
      <reference_type>data_to_target</reference_type>
    </Internal_Reference>
  </Target_Identification>
This would allow searches for the target at pds.nasa.gov to return this
collection. It would also lengthen collection.xml though, as lid_references
to context products should bubble up.

inventory.csv
- Suggestion: name this file collection.csv or collection_inventory.csv,
per PDS4 Standards section 2B.2.2.2
- Presumably, this is intentional, but if not, this file lists 94 LIDs, but
this collection in total has only 16 .xml files.