SDDFMI_0001 =========== o Apply uniform label conventions across all Stardust data file wherever possible. o Data tables are too long and too wide. Split if feasible. o Column 24 of data labels have quotes inside the field when the value is "ON". o Columns with ITEMS should be split into separate COLUMNs o If the NOT_APPLICATION_CONSTANT and UNKNOWN_CONSTANT values are never actually used in the data, they should be removed from the label. o The CSV versions of the data tables have more headers than columns. There appears to be an extra angle label on the end. o There are cut-and-paste errors in the aareadme.txt file. o Verify the number of rows in each table against the number given in the labels. o START/STOP_TIMEs in the label match the .tab files but not the .csv files. o Remove the "software" directory and delete references to it from aareadme.txt, voldesc.cat, etc. o Change the DATA_SET_ID to "SDU-C/E/L-DFMI-2-EDR-V1.0" in all labels, catalog files and indices as applicable. o In document/calrpt/dfmical.lbl, DOCUMENT_FORMAT should be "ADOBE PDF". o In document/images/images.lbl, DOCUMENT_FORMAT value "JPEG" should be "JPG". o In document/scdesc/scdesc.lbl, DOCUMENT_FORMAT value "PDF" should be "ADOBE PDF". o In the data labels, DATA_TY{E of "ASCII INTEGER" should be "ASCII_INTEGER". o Change TARGET_NAME to "81P/WILD 2 (1978 A2)" in all labels and catalog files. o Supply a TARGET catalog file and add to voldesc.cat. o aareadme.lbl: - 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? Modify accordingly. o voldesc.cat - Where did that VOLUME_SERIES_NAME come from? o 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. o 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. It should be reviewed carefully by an editor - a human editor - prior to archiving. o inst.cat - Missing INSTRUMENT_REFERENCE_INFO - Headings do not follow standards. - Who is the author of this text? An author or an attribution must be provided. - 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. It should be reviewed by an editor prior to archiving. o 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. It should be reviewed by an editor prior to archiving. o 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? Indicate author or attribution. - No attempt to read text. It should be reviewed by an editor prior to archiving. o person.cat - all phone numbers must be in quotes. o 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? If not, replace it with a DOCUMENT object. - UNKNOWN_CONSTANT is not appropriate in labels (PDS use is that unknown values will be supplied prior to final archiving). Is the value really unknown, or is it missing, not applicable or out of range? Replace with the appropriate keyword. - There is a great deal of text at the beginning of this file. Who is the author and who owns the copyright? Either author or attribution must be supplied. 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? o docinfo.txt - The "images/" subdirectory is unexplained in this text, as are the "onlabels.txt" and "lblinfo.txt" files. This file must be updated to address all directory contents. o 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). o dfmical.lbl - This is not an appropriate use of the TEXT object. Replace with a DOCUMENT object/ - What is the relationship between the text file and the PDF? Make this clear in the labels and the docinfo.txt file. - The PDf file is set up as a journal submission. Where was it published? Do we have permission to republish? Copyright acknowledgment must be included or this should be deleted and referenced via the publication. - If the text file is a translation of the PDF file, it must be proofed by a human editor. If it is not, it must be explained in the label and docinfo.txt file, then proofed by a human editor. o 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? Acknowledgements must be included or the files withdrawn. - 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. Include them, replace them, or remove them entirely from the HTML. - Who owns the copyright on the web document? Acknowledgement must be included or it should be withdrawn. - This differs from other versions presented on other disks. Is this the latest version? If so, it should be propagated; if not, replaced. o extras/jgr_dfmi.lbl - Documentation should not be put in an EXTRAS directory. - This paper appears to be nearly identical to the dfmical.pdf file in the document directory. If so, why are both present? Do we have copyright permission for both? o There is no index subdirectory. It is required and must be supplied with at least the minimum required PDS INDEX_TABLE file. ________________ ________________