bundle*.xml
*/collection*.xml
document/*.xml
- These have lid_references to
  urn:nasa:pds:context:facility:observatory.atlas_chile
  urn:nasa:pds:context:facility:observatory.atlas_haleakala
  urn:nasa:pds:context:facility:observatory.atlas_mauna_loa
  urn:nasa:pds:context:facility:observatory.atlas_south_africa
  urn:nasa:pds:context:telescope:atlas_chile.0m5
  urn:nasa:pds:context:telescope:atlas_haleakala.0m5
  urn:nasa:pds:context:telescope:atlas_mauna_loa.0m5
  urn:nasa:pds:context:telescope:atlas_south_africa.0m5
  urn:nasa:pds:context:instrument:atlas_chile.0m5.10kccd
  urn:nasa:pds:context:instrument:atlas_haleakala.0m5.10kccd
  urn:nasa:pds:context:instrument:atlas_mauna_loa.0m5.10kccd
  urn:nasa:pds:context:instrument:atlas_south_africa.0m5.10kccd
which do not match what data/.../*.xml have.  If these describe the same
things, please converge.  If not, bundle*.xml and collection*.xml should
have lid_references to a superset of those in the labels below them.

bundle_gbo.ast.atlas.survey_v0.0.xml
- Every bundle needs Citation_Information/doi, which can be obtained via
  https://pds-engineering.jpl.nasa.gov/content/doi
though SBN may have its own mechanism

data/59613/
- Is this bad? Ranges:
  01a59613o0029o - 01a59613o1012o: 12 files per file root, including .fz,.jpg
  02a59613o0029c - 02a59613o1016c: 12 files per file root, including .fz,.jpg
  04a59613o0001o - 04a59613o0320o: 10 files per file root; no .dph.csv
  04a59613o0132o: 4 files; no .dph.csv; no .ddc.csv; no .diff
  04a59613o0258o: 4 files; no .dph.csv; no .ddc.csv; no .diff
  04a59613o0260o: 4 files; no .dph.csv; no .ddc.csv; no .diff
  04a59613o0315o - 04a59613o0320o: 4 files; no ...

data/59613/*.xml
Observatory, telescope, instrument LIDs follow this format
  u:n:p:c:facility:observatory.<obsID>
  u:n:p:c:telescope:<obsID>.<teleID>
  u:n:p:c:instrument:<obsID>.<teleID>.<instID>
- Many files have lid_references to this set:
  urn:nasa:pds:context:facility:observatory.atlas-chl
  urn:nasa:pds:context:telescope:atlas-chl.0m5
  urn:nasa:pds:context:instrument:telescope.sta1600.atlas-chl
Assuming the inst LID is based on the telescope LID, the last should be
  urn:nasa:pds:context:instrument:atlas-chl.0m5.sta1600
- Many files have lid_references to this set:
  urn:nasa:pds:context:facility:observatory.atlas-hko
  urn:nasa:pds:context:telescope:atlas-hko.0m5
  urn:nasa:pds:context:instrument:telescope.sta1600.atlas-hko
The last should be
  urn:nasa:pds:context:instrument:atlas-hko.0m5.sta1600
- Many files have lid_references to this set:
  urn:nasa:pds:context:facility:observatory.atlas-mlo
  urn:nasa:pds:context:telescope:atlas-mlo.0m5
  urn:nasa:pds:context:instrument:telescope.sta1600.atlas-mlo
The last should be
  urn:nasa:pds:context:instrument:atlas-mlo.0m5.sta1600
- PDS does not have a generic target or target type for survey field. Our
current solution is to use
  <Target_Identification>
    <name>Multiple</name>
    <type>Asteroid</type>
  </Target_Identification>
in place of
  <Target_Identification>
    <name>SA018N58</name>
    <type>Survey Field</type>
    <Internal_Reference>
      <lid_reference>urn:nasa:pds:context:target:survey_field.atlas</lid_reference>
      <reference_type>data_to_target</reference_type>
    </Internal_Reference>
  </Target_Identification>
Not all data labels, e.g. *.csv.xml, include the Survey dictionary. Would it
be meaningful for those labels to include it? The presence of that dictionary
could indicate that the label's target is a survey.
- For whatever the final set of context LIDs ends up being, please provide EN
with the context objects for them, including the ones above as well as
  urn:nasa:pds:context:investigation:observing_campaign.atlas

data/59613/01a59613o0100o.dph.csv* (+ probably others)
- In the .xml, field 17 (apsky) has error_constant = -99.999, but in the .csv,
that column has many positive values plus a few -100.00 values. I.e. if -100.00
is meant to indicate an error, it doesn't match. If it means something else,
please define that constant. 

data/59613/01a59613o0100o.ddc.csv.xml (+ probably others)
- In File_Area_Observational, only the first Array_2D_Image has a
disp:Display_Settings (and img:Imaging) tied to it, via local_identifier
image_array. Any other Array_2D_Image intended to be viewed should have its
own disp:Display_Settings and img:Imaging with matching local_identifier.

data/59613/*dph.csv.xml
- Each one has an unknown lid_refernce, e.g. the first file has
  <lid_reference>urn:nasa:pds:bundle_id:59613:01a59613o0029o_fits</...>
  <reference_type>data_to_raw_product</...>
Perhaps ":bundle_id:" is a placeholder for an undetermined bundle? Please
resolve that before making the data public.