CARA Liens ========== Note: It is expected that a new version of the data will be extracted from the CARA database after consultation with SBN on format and content. These notes should guide that consultation and re- drafting. Science Liens ------------- o Filter "S" needs to be described in the documentation (from Vilnius system, it is similar to 497nm narrowband filter. o Need definitions for all filters and abbreviations used in the data. Probably this should be a separate document that can be referenced in subsequent deliveries. o Comments on slides 6-8 should be taken as liens unless otherwise indicated. o Check to make sure the star catalog name is spelled out somewhere. o Regarding the missing phase angle values that could be calculated in the example case relatively easily, this needs to be investigated and a reasonable solution applied. o Not all observers are identified by code which is then expended in a separate file. Ideally, this information should be given in a consistent fashion in all cases (either always explicit in the table or always as a code that is expanded in an accopmanying file). o Improve the cara_description.txt document to serve as the collection description (need tech editing). In this description: - Define Af(rho) and each term individually - Cite A'Hearn, et al. (1984), AJ 89, 579. - Note that Af(rho) varies with phase angle because of the scattering properties of dust, and that this is NOT accounted for in these results (is it?). - Consider referencing the CARA project website o Column 8 is described as "Radius of coma in km", but is more likely to be "Radius of the aperture used to measure the coma at the distance of the comet in km." o Unit of column 10 appears to be "cm". o Define abbreviations used for reference catalogs (probably best as a separate document). o Provide phase angle for all observations (the JPL Horizons system can calculate it, for example). o Field 7 description: "brightnessof" should be 2 words. It should probably just be described as a magnitude in the particular filter. o Complete the information in cara_observer_code.txt (many missing codes). o Please add as much additional information about individual observing systems as might be available (in the data, in the codes list, or wherever it makes sense). PDS4 Standards Liens -------------------- PDS4 identifiers: o Since everything in this bundle is, by definition, coming from the CARA project, it is not necessary or desirable to continually repeat "cara" in every file name and at every level of ID. o All current LIDs below the bundle level are invalid (they contain placeholder strings and uppercase letters). bundle.xml o The description should not use the undefined acronym "CARA". o There should be a Context_Area to link the bundle to a CARA context object (TBD) and to provide any appropriate Primary_Result_Summary values and target information. gbo-cara:cara_documents ----------------------- Formatting notes: - Collection members should be in a subdirectory (data/ or document/), even in degenerate cases. collection.xml - Schematron validation is not set up in this label. The labels are not valid. o Description in Citation_Area is insufficient and uses the undefined acronym "CARA". o Context_Area does not provide links to observing campaign or mission. o Neither Citation description nor Primary_Result_Summary give any indication what sort of observations are in the collection (image, spectrum, derived properties, etc.) o The collection inventory incorrectly lists the collection label - a collection is not a member of itself. cara_observer_code.xml - Schematron validation has not been set up in this label. o Citation Area description uses the undefined acronym "CARA". The description is also not sufficient if there is additional data expected in future. o There is no Context_Area to tie this documentation to campaign or other appropriate search terms. o "First" is not an appropriate value in this context. ("Text Version" would be.) o The accompanying file is defined as being "7-bit ASCII Text" but is clearly not. gbo-cara:comet-afrho -------------------- 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. collection.xml - Schematron validation not enabled. o Invalid collection ID o Citation description is too cryptic, uses the undefined acronym "CARA" and provides too little detail. o Insufficient Primary_Result_Summary information o No context links to search terms o Collection inventory table lists the collection label. data labels (Example: 116P.xml and 116P.tab) - No Schematron validation. o The label is not schematically valid. o Product LID contains uppercase characters and is dangerously generic. o Citation description is insufficient. o Investigation is listed as "None" but clearly there is one, given the constant repetition of the CARA acronym. o Context object references are inappropriate and were not vetted prior to inclusion. These must change. o Primary Result Summary is missing. o Observing System is inadequately described. o Target identification is not in the correct format for small bodies. o The Table definition contains an invalid value for o The table file does not have the required CR/LF delimiters. o The Table record_length is wildly inappropriate. o The table file itself uses delimiters between columns inapproriately. o 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. o 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. o "Reference Catalog" and "Analyst" appear to contain identical data. This is not consistent with the the field descriptions. o 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. data files o Missing or inconsistent use of CR/LF delimiters o Inconsistemt record length within files.