SDDFMI_0001 =========== aareadme.lbl - This is not really an appropriate use of a TEXT object. Has this been approved by CN? - This file implies that these are all the DFMI data that there will ever be, sort of. Is that true? The dataset.cat file does not indicate that the experiment has been shut down, so why is this volume not called "Early Cruise Data", as for NAVCAM? voldesc.cat - Where did that VOLUME_SERIES_NAME come from? - Why no TARGET_CATALOG? CATALOG/ ======== catinfo.txt - This file claims there is "more information about contacting the PDS Central Node" in the aareadme.txt file. This is not true. It refers to "this CD". This is probably not a good idea - there's no reason to assume a user will be reading from a CD. dataset.cat - There are syntax errors in this file: line 4 & 312: TARGET_NAME is not quoted and contains a hyphen. - SPACECRAFT_NAME is a deprecated keyword - use INSTRUMENT_HOST_NAME. - TARGET_NAME is not consistent with other instruments (specifically NAVCAM). - DATA_SET_REFERENCE_INFORMATION is missing - DATA_SET_INFORMATION is missing ARCHIVE_STATUS and DATA_SET_TERSE_DESC. - DATA_SET_NAME is not properly formatted. - DATA_SET_DESC subheadings do not follow the standards. - The comet name "Wild 2" is consistently misspelled throughout the text. - Defining individual columns of data tables in the DATA_SET_DESC is not appropriate. - It is not true that "PDS times do not require quotes". The rule is that ISO 8601-formatted time strings must not be quoted. - "UNK" and "N/A" are NOT for use in data tables - they are for use as values of keywords in labels. They cannot be used in numeric columns of data tables because they are not numbers. - "perfectness" is not a standard English word. Try "perfection". - Too much text to read it all carefully. inst.cat - Missing ISNTRUMENT_REFERENCE_INFO - Headings do not follow standards. - Who is the author of this text? - There is a reference to the /EXTRAS directory. This is inappropriate, as the /EXTRAS directory is not part of the deep archive. Documentation MAY NOT be delivered in the /EXTRAS directory. - No attempt to read the text carefully insthost.cat - INSTRUMENT_HOST_REFERENCE_INFO is missing. - Is this the most recent form of this file? If not, it should be replaced with it. - No attempt to read text carefully mission.cat - MISSION_TARGET is repeated - there can only be a single one (with multiple values, if appropriate). - Missing MISSION_REFERENCE_INFORMATION and MISSION_OBJECTIVES_SUMMARY - Is this the most recent form of this file? If not, it should be replaced with it. - Who is the author and who owns the copyright? - No attempt to read text. person.cat - all phone numbers must be in quotes. DATA/ ===== dfmicru001.lbl - TARGET_NAME is not the standard value. And why is the target the comet and not dust? - SPACECRAFT_NAME is a deprecated keyword - use INSTRUMENT_HOST_NAME - DATA_SET_NAME is problematic. - This is a highly questionable use of a TEXT object. Has CN approved it? - UNKNOWN_CONSTANT is not usually appropriate in labels. Is the value really unknown, or is it missing, or out of range? - FORMAT descriptions for fields with ITEMS are missing repetition counts. - There is a great deal of text at the beginning of this file. Who is the author and who owns the copyright? dfmienc001.lbl - TARGET_NAME is not the standard value. And why is the target the comet and not dust? - SPACECRAFT_NAME is a deprecated keyword - use INSTRUMENT_HOST_NAME - DATA_SET_NAME is problematic. - This is a highly questionable use of a TEXT object. Has CN approved it? - UNKNOWN_CONSTANT is not usually appropriate in labels. Is the value really unknown, or is it missing, or out of range? - FORMAT descriptions for fields with ITEMS are missing repetition counts. - There is a reference to the "DFMI Technical Manual, which is kept on file at the Planetary Data Systems Small Bodies Node." I've never heard of it and this is not true. Where is this document? - There is a great deal of text at the beginning of this file. Who is the author and who owns the copyright? DOCUMENT/ ========= docinfo.txt - The "images/" subdirectory is unexplained in this text, as are the "onlabels.txt" and "lblinfo.txt" files. lblinfo.txt - What is the point of this file? If it stays, it should contain the similar information which is currently languishing in the DATA_SET_DESC text (where it certainly does not belong). DOCUMENT/CALRPT/ ================ dfmical.lbl - This is not an appropriate use of the TEXT object. Has CN approved it? - What is the relationship between the text file and the PDF. - The PDf file is set up as a journal submission. Where was it published? Do we have permission to republish? - If the text file is a translation of the PDF file, has it been proofed? DOCUMENT/IMAGES/ ================ There are no labels in this directory. DOCUMENT/SCDESC/ ================ scdesc.lbl - Who owns the copyright on the aerogel brochure? Do we have permission to republish? Do we have permission to use the photos in this context? - The DOCUMENT_NAME is wrong for the Aerogel brochure. It should be "Aerogel: Mystifying 'Blue Smoke'" - When I look at this I see at least one photo laying over text, making it unreadable. - The HTML files reference non-local image files which are not in this directory and are not mentioned in the label. - Who owns the copyright on the web document? - This differs from other versions presented on other disks. Is this the latest version? EXTRAS/ ======= jgr_dfmi.lbl - This paper appear to be nearly identical to the dfmical.pdf file in the document directory. If so, that document is plagiarized and must be removed. - Documentation should not be put in an EXTRAS directory. INDEX/ ====== There is no index subdirectory. It is required and must be supplied with at least the minimum required PDS INDEX_TABLE file. SOFTWARE/ ========= softinfo.txt - The abbreviation "XVT" is used but never defined. In fact, its mention seems to be a non-sequitor. What is it? - The last sentence of the second paragraph makes no sense. - No version number is given for NASAview in the text. Three different version numbers are given in the directory tree listing - why? - Why is there no Linux directory? - There is no mention of Windows XP and 2000. Aren't these supported? SOFTWARE/MACPPC/ ================ nv1r12b.lbl - This is not an appropriate use of a TEXT object. Has CN approved it? - The SOFTWARE object is mission SOFTWARE_INFORMATION, SOFTWARE_ONLINE and SOFTWARE_PURPOSE subobjects. - There are both missing and invalid keywords in this label. - There are numerous additional syntactic and semantic errors in this label. It is not even close to being compliant or even self-consistent. No further attempt to verify. SOFTWARE/PCWIN32/ ================= nv2r52.lbl - Same sort of rampant errors as for MACPPC/. No attempt to verify. SOFTWARE/SUNSOLAR/ ================== nv2r53a.lbl - Same sort of rampant errors as for MACPPC/. No attempt to verify.