SDCIDA_0001 =========== aareadme.lbl - This file has variable-length records. - This contains a DOCUMENT object. I've been told by CN in the past the DOCUMENTs must be in the DOCUMENT directory. Is this based on an approved model? errata.txt - There seem to be no errata, so there shouldn't be an errata file. Is this a place-holder? voldesc.cat - This file has variable-length records. - There can be only one DATA_PRODUCER in a VOLUME object. Crediting a software vendor as a data producer seems inappropriate. - Who decided on the VOLUME_SERIES_NAME? Strikes me as way too generic. - line 26: "MAX-PLANCK-INSITUT" is not the way the name appears in the data dictionary. (Note that there is also a typo in the dictionary in this name that should be corrected. - line 27: Is that really the correct spelling for the FACILITY_NAME? Two Es in a row looks odd to me. - line 66: Syntax error (comma at end). - Is this the right TARGET? Isn't this an instellar dust analyzer, which would make the target interstellar dust? CATALOG/ -------- - All these files have variable-length records. - Are these the latest versions of the mission and instrument host files? cidads.cat - SPACECRAFT_NAME is a deprecated keyword. Use INSTRUMENT_HOST_NAME instead. - Missing ARCHIVE_STATUS keyword. - Is this a sufficiently specific DATA_SET_NAME? Will there be no other CIDA data from the Stardust mission? - "INTERSTELLAR PARTICLES" is not a known TARGET_NAME and no TARGET catalog file is supplied for it. Neither is it listed in the voldesc.cat file in the root directory. - This file contains two DATA_SET_TARGET objects - only one is allowed. - line 13: "spectrums" should be "spectra". - This file claims that the OBJECT_TYPE is "SPECTRUM", but the data files here are all TABLEs. cidainst.cat - Is CIDA really a "COSMIC DUST ANALYSER" (as opposed to a "DUST IMPACT DETECTOR" or "DUST ANALYZER" or "MASS SPECTROMETER")? - The INSTRUMENT_NAME given here does not agree with the instrument name given in the aareadme.txt file in the root directory, or with the INSTRUMENT_TYPE. - line 14: REFERENCE_KEY_ID values are not suitable substitutes for standard short forms of citation. - Standard headings are not used in the INSTRUMENT_DESC text. - Who is the author of this text? Who owns the copyright? - line 50: There should be no apostrophe in "flyby's". - I made no systematic attempt to proof text. insthost.cat - The LABEL_REVISION_NOTE does not indicate what was done on the successive revisions. - There should be a REFERENCE object and citation for the Stardust Mission Plan quoted in this file. It should be listed in the INSTRUMENT_HOST_ REFERENCE_INFO object. - I made no attempt to proof text or compare to other versions on other disks. mission.cat - LABEL_REVISION_NOTE does not indicate what was done at each revision. - MISSION_STOP_DATE should not be unknown - there is an ending date mentioned in the text. - There may only be a single MISSION_TARGET object (it may be multi-valued). - Who wrote this text? Who owns the copyright? - There should be a REFERENCE object and citation for the Stardust Mission Plan quoted in this file. It should be listed in the MISSION_REFERENCE_ INFORMATION object. - The "INTERSTELLAR PARTICLES" target mentioned in the DATA_SET catalog object is not mentioned here. - I made no attempt to proof text or compare to other versions on other disks. person.cat - line 13: INSTUTITION_NAME should match standard value (except for typo) - line 14, 69: "FINISH" should probably be "FINNISH" - All phone numbers must be in quotes. ref.cat - Reference text is missing information (contains strings of "??"). DOCUMENT/ --------- cidasis.txt - This is not valid syntax for an attached DOCUMENT object label. The label should be in a separate file or an appropriate object pointer provided. - I did not attempt to proof. lblinfo.txt - line 17: This statement is incorrect. In fact, all of the documents in this directory have attached labels. - How does this file compare with other files on the same name on other Stardust volumes? - I did not attempt to proof. onlabels.txt - How does this file compare with other files on the same name on other Stardust volumes? - I did not attempt to proof. DOCUMENT/EXAMPLE/ ----------------- calexmpl.oct - What is "octave"? calexmpl.pdf - Who owns the copyright on this? - Any chance of an ASCII version of the text part of this? INDEX/ ------ index.tab - The indentation is odd and variable through this file. Any particular reason? - Columns 6 & 7 (SPACECRAFT_CLOCK_START_COUNT and SPACECRAFT_CLOCK_STOP_COUNT) have a DATA_TYPE of "TIME", but are not in ISO 8601 format. Spacecraft times should have a DATA_TYPE of CHARACTER, ASCII_INTEGER or ASCII_REAL, as appropriate. (In the data file they are treated as character strings.) - The required PRODUCT_ID column is missing. - SPACECRAFT_NAME is a deprecated keyword. Use INSTRUMENT_HOST_NAME. DATA/ ----- datainfo.txt - This file doesn't seem to add anything, and the grammar in the one sentence is less than optimal. This is true for all the *info.txt files included in this hierarchy. This information is better presented in the aadreadme.txt file in the root directory. DATA/EDFASCII/CRUISE/NEGATIVE/ & /POSITIVE/ --------------------------------------------- *.tab - PRODUCT_TYPE is incorrect. It should be {"EDF","HK"} (based on current standard values). It has nothing to do with data objects. - Proposed INSTRUMENT_MODE_ID is overly long and is not an ID - it's a name. cida_header.fmt - There are undefined acronyms in here (ADC, FDAQ) - UNIT values are in lower case and abbreviated. DATA/EDFASCII/ENCOUNTR/ ----------------------- These directories are empty. DATA/HKVALUES/CRUISE/ --------------------- *.tab - PRODUCT_TYPE is incorrect. DATA/HKVALUES/ENCOUNTR/ ----------------------- This directory is empty.