ear-c-multi-6-cara-pds4-v1.0 o The reviewers would like to see more information about the observatories and telescopes used to collect the data. gbo_cara ======== o Since everything in this bundle is, by definition, coming from the CARA campaign(?), it is inappropriate to continually repeat "cara" in every file name and at every level of ID. o All LIDs below the bundle level are invalid. o In bundle.xml - The description should not use the undefined acronym "CARA". - There should be a Context_Area to link the bundle to the observing campaign (assuming it is one) and to provide any appropriate Primary_Result_Summary values and target information. gbo_cara:cara_documents ======================= o Collection ID repeats elements in the bundle ID. It shouldn't. o Collection members should probably always be in a subdirectory. o There are observer codes used in the data that are not seen in cara_observer_code.txt. These should be added. o In collection.xml - Schematron validation is not set up in this label. - Description in Citation_Area is insufficient and uses the undefined acronym "CARA". - Context_Area does not provide links to observing campaign or mission. - Neither Citation description nor Primary_Result_Summary give any indication what sort of observations are in the collection (image, spectrum, derived properties, etc.) - The collection inventory incorrectly lists the collection label - a collection is not a member of itself. o In cara_observer_code.xml - Schematron validation has not been set up in this label. - Citation Area description uses the undefined acronym "CARA". The description is also not sufficient if there is additional data expected in future. - There is no Context_Area to tie this documentation to campaign or other appropriate search terms. - "First" is not an appropriate value in this context. - The accompanying file is defined as being "7-bit ASCII Text" but is clearly not. gbo_cara:comet-afrho ==================== o In some cases the values of Afrho obtained by the reviewers using the filters and apertures do not match with the reported values in the tables. o Need to explicitly define filter information either in a separate file or as part of the cara_description.txt file. In particular the reviewers were not familiar with the S filter. Reasonable values for Afrho were obtained by the reviewer using the following assumptions but they should be given explicitly: - B, V, R, I were standard Cousins filters - Ru, Vu were the same as Cousins R and V - R - S = 0.22 (e.g., “S” was between “R” and “I”) o Collection ID repeats elements in the bundle ID and is too generic. o LIDs in data products are not even consistently invalid with respect to the invalid collection LID. o There is no collection description. o Neither the collection label nor the product labels contain full citation information. At least one or the other must. o In cara_description.txt - Need to fix numerous typos as outlined in reviewers notes. - Need to move from the description file from 'Notes' area into the collection. - Define Afrho and reference original paper (A’Hearn et al. 1984, AJ, 89, 579). - Should note Afrho changes with phase angle due to scattering properties of dust and that it does not appear to be accounted for in this dataset. - Change description of column 8 so that it explains that this is the radius of the photometric aperture in km. - Need to confirm if Estimated Error (Column 10) is in cm and if so change the description. - In “cara_description.txt” column 7 is listed as “Measured Magnitude” but this is described as “brightness” in the column description of the .xml files. This can be easily understood to mean magnitude (presumably in the specified filter), which can be tied to physical units through measurement of a reference star and zero-point mag. But would a description simply as “magnitude” be better? o In collection.xml - Schematron validation not enabled. - Invalid collection ID - Citation description is too cryptic, uses the undefined acronym "CARA" and provides too little detail. - Insufficient Primary_Result_Summary information - No context links to search terms - Collection inventory table lists the collection label. o In data labels (Example: 116P.xml and 116P.tab) - In 29P.tab 8 phase angle entries were missing. These should be determined from Horizons and added into the table. - Need to confirm if Estimated Error (Column 10) is in cm and if so change the units. - The abbreviations for the reference catalogs need to be defined. - All *.xml files except C2013A1: typo in XML field character for column 7: “brightnessof” - No Schematron validation. - The label is not schematically valid. - Product LID contains uppercase characters and is dangerously generic. - Citation description is insufficient. - Investigation is listed as "None" but clearly there is one, given the constant repetition of the CARA acronym. - Context object references are inappropriate and were not vetted prior to inclusion. These must change. - Primary Result Summary is missing. - Observing System is inadequately described. - Target identification is not in the correct format for small bodies. - The Table definition contains an invalid value for - The table file does not have the required CR/LF delimiters. - The Table record_length is wildly inappropriate. - The table file itself uses delimiters between columns inapproriately. - The first field in the file is not appropriately formatted for a periodic comet number, and is inaccurately described as "MPC Comet Designation". Also, if there are going to be small body designations in the file, there need to be at least two of them in each record to help avoid mis-identifications. But as the target identification is in the label, it is odd that it is also included in the file - implying it might change from record to record. - Fields 8, 9, and 10 (at least) have data types of "ASCII_Real" but are, in fact, integers. The field_format descriptions for all these fields are incorrect. - "Reference Catalog" and "Analyst" appear to contain identical data. This is not consistent with the the field descriptions. - The last 2-4 columns clearly need to have either a missing or inapplicable constant defined. Values like "no entry" are clearly not real. There may be similar issues with other fields.