Comments produced for October 2025 R&A peer review by SBN:T.Barnes ======================================= urn:nasa:pds:gbl-keck_lab:ir_ices_lab_spectra::1.0 Are there any other authors to be added? Original delivery said "Zhang C. et al". Please ensure all authors and editors, if any, are included. No context objects for Observing_System or Observing_System_Component. These should be created. --> There does not appear to be any documentation related to the instrument. Not even a description is given in the PDS labels. Can any be provided? This in part could be resolved with a well defined context object. The target list has no context objects associated with them and so may not be findable? Update from IM 1.15.0.0 to more recent IM, especially to be able to add more author/editor meta data. file: 'bundle.xml' --> Time_Coordinates are most likely not needed and should be removed. Also they differ greatly from the child collection. file: 'ir_ices_lab_spectra/collection.xml' --> SBN to coordinate and create DOI for collection. files: 'ir_ices_lab_spectra/document/*.xml --> Ensure that each paper included herein can be reproduced (and published) in the PDS archive. --> --> One of the documents says it was downloaded by University of Hawaii, library serials dept at a specific IP address. --> Clarify in the Citation_Information.description that these papers are re-prints. --> Strongly suggest adding as an external reference with the citation for the paper's original publication. I will note that the DOI is included in the object. file: 'ir_ices_lab_spectra/overview.txt' --> Text is too sparse. Can we expand it and make it more informative? ======================================= urn:nasa:pds:gbo-mcdonald:comet_echelle_survey::1.0 Missing context objects. * urn:nasa:pds:context:telescope:mcdonald.smith2m7 --> Note that the mcdonald.smith2m7 used to exist (at least in draft form) and will now need to be created. Also when this is done, the name, "2.7m Telescope", should be expanded, and as a result fixed in all labels. * urn:nasa:pds:context:instrument:mcdonald.harlanjsmith_2m7.tull_coude_spectrograph Context object updates needed: (action for SBN) --> Add alternate name of "103P/1986 E2 (Hartley 2)" to urn:nasa:pds:context:target:comet.103p_hartley_2 --> Add alternate name of "19P/1904 Y2 (Borrelly 1)" to urn:nasa:pds:context:target:comet.19p_borrelly --> Add alternate name of "67P/1969 R1 (Churyumov-Gerasimenko 1)" to urn:nasa:pds:context:target:comet.67p_churyumov-gerasimenko For those targets w/o context reference already included, there are a several that have context references that could be included. Below are the ones I found: * : * alpha Lyr: urn:nasa:pds:context:target:star.alf_lyr * epsilon Orionis: urn:nasa:pds:context:target:star.eps_ori * HD 93521: urn:esa:psa:context:target:star.hd_93521 * HR 153: urn:esa:psa:context:target:star.zet_cas * HR 1544: urn:esa:psa:context:target:star.hd_30739 * HR 3982: urn:nasa:pds:context:target:star.alf_leo * HR 4468: urn:esa:psa:context:target:star.hd_100889 * HR 5191: urn:nasa:pds:context:target:star.eta_uma * HR 7001: urn:esa:psa:context:target:star.hd_172167 * HR 718: urn:esa:psa:context:target:star.hd_15318 * HR 8634: urn:nasa:pds:context:target:star.42_peg * Sun: urn:nasa:pds:context:target:star.sun * zeta Ophiuchi: urn:nasa:pds:context:target:star.zet_oph Should SBN create new context objects for each comet that does not already have one? Would it be of value for some/all of the tables in the PDF documents to be in an ascii table or csv file for much easier search-ability programmatically? For example to discover weather or other stats. If the data would rely or greatly benefit from any of the PDF documents (ex:tables) found in this collection, they should be referenced in the data labels in the Reference_List. I see important information related to each observation found in these tables and not in the data label meta data or the overview document they try to reference. If the tables are extracted into searchable PDS tables, referencing those tables would be better. Should any of the data providers be added as authors or editors or contributors to the collection? They could be added to the individual data labels they contributed to as well. I see at the end of the survey.pdf document some funding acknowledgment for at least some of the data taken. These could be added to the individual product labels with the Citation_Information.Funding_Acknowledgement object. Also they could be considered to be added for the collection as a whole. file: 'collection.xml' --> SBN to coordinate and create DOI for collection. --> Recommend adding Funding_Acknowledgement object to the Citation_Information for this collection if it exists. --> The start_date_time value is rounded up (due to lose of precision). From data, I see the value should be: 1995-10-03T11:37:29.600Z. Please correct. --> The stop_date_time value is wrong. From the data, it should be: 2024-11-01T03:35:50.350Z --> No target listed. Should one be? Something generic, or a list of all comets? files: 'data/*/*.xml' --> The collection overview document comet_echelle_survey:survey::1.0 is being referenced as comet_echelle_survey:overview in these labels. Please update the LID. --> --> Please make this a LIDVID reference instead of a LID reference. --> --> Also, please add a referencing what this document is or how it relates to the data file; basically why is it being referenced. Example: description of instrument, data, etc. file: 'survey.pdf' --> In the last paragraph in section 5, there is a typo "list incudes" but should be "list includes" ======================================= urn:nasa:pds:gbo-uwo_meteor_radar::1.0 Strongly recommend using the same IM for all of these products. Recommend updating the bundle, document, and meteor_shower to be IM version 1.24.0.0 instead of 1.15.0.0. Action for SBN: The context object for facility:observatory.uwo_meteor_radar needs to be updated. The last update says it added something that never was added, namely the instrument and telescope references. Can we find more meta data on the author for DOI generation and add to collection.xml files as appropriate? Example data: full name, ORCID, Funding Institution ROR ID# and name. To put this information in, it would require a more recent IM version for all except the meteor_orbits collection. Target_Identification name lists the name as "Multiple" and the type as "Meteoroid Stream". Can we decide on a better name to search on, perhaps "Multiple Meteoroid Streams" --> Should a context object be created for this kind of target? --> Is Dust an appropriate target? Several PDS4 xml label files have Citation_Information.publication_year values other than 2026. They should be updated from 2024 and 2025 to 2026. directory: 'document/' --> Why wasn't the 'observatory.uwo_meteor_radar.*' files originally delivered included here. The meteor_orbits copy has more information, but perhaps not enough to include in the archive? --> In general it appears that the copy from meteor_showers was used, but both copies are different, usually slightly, but the meteor_orbits tends to have a little bit more. These should be reconciled. --> The documents in this collection pretty much mirror the brief descriptions in the corresponding context objects, except formatted nicer. Is anything gained by having them here? file: 'document/collection.xml' --> Update the Citation_Information.publication_year from 2025 to 2026. directory: 'meteor_orbits/' --> Please add other meta data for each author and/or editor when mentioned in a label: person_orcid, contributor_type (if known), Affiliation, and optionally sequence_number. --> This collection appears to be derived from a network of cameras around the world. How is it associated Radar Orbiting_System described in each label? The data does not appear to have been taken with a radar instrument. --> --> Since this appears to be derived tabulated data, it doesn't appear to have been directly taken with any instrument, so what should be given? Each record gives the source of the data, a station, possibly one or more cameras. file: 'meteor_orbits/collection.xml' --> Recommend putting "(CAMS)" in the as is done in the <description>. --> typo in abstract, missing opening '(' for "(CAMS)" --> SBN to coordinate and create DOI for collection. --> The two papers referenced in the overview.xml appear to be pertinent to understanding and source of data for this collection as a whole and should probably be added the Reference_List here. file: 'meteor_orbits/data/*.xml' --> The "date" column is described as an UTF8_String and the data is column is mm/dd/yy. If this is acceptable, recommend adding to the <description> of this field the format of the date (to not be confused with dd/mm/yy) and that the year is in the 20xx. This is in part mentioned in the readme pdf document, but computers aren't going to read that here. --> The "stations" column is described as containing the contributing/participating camera numbers. Two comments: --> --> (1) where do we go to uncode the number with the camera? Please add to the description where this can be done. --> --> (2) the data appears to be formated with a leading underscore followed by a number. When there are multiple numbers, they are separated by an underscore. I believe this should be described in the description. --> It appears from the 'document/readme*' that the document is very important to understanding the data. If that is the case, please reference it in the Reference_List. file: 'meteor_orbits/overview.txt' --> SBN to coordinate and create DOI for collection. file: 'meteor_showers/collection.xml' --> Suggest renaming the collection <title> to be from Data collection to Database, or a complete rework of the title. Is these observations only from UWO CMOR? That might be nice to include. --> Please expand the Citation_Information.description to include the facility/instrument, etc. --> SBN to coordinate and create DOI for collection. --> Update the Citation_Information.publication_year from 2025 to 2026. --> Is there a DOI for the referenced published paper that this database is a source for? If so, please add to as an External_Reference in this file. file: 'meteor_showers/data/jenniskens_2023_listofshowers_embedded.xml' --> It appears from the 'document/readme*' that the document is very important to understanding the data. If that is the case, please reference it in the Reference_List --> Please add to the File_Area_Observational an area that describes the header bytes in the csv file. --> Should we define what it means when a field is empty? If so, should a constant be used? ======================================= urn:nasa:pds:neowise-derived:cryowisecomets::1.0 The <Investigation_Area> <name> "The Near-Earth Object Wide-Field Infrared Explorer (NEOWISE) MIssion" is a typo. It appears to have been propagated from the context object. I see the "MIssion" should be "Mission" (lowercase "i"), but also the S, "Survey", in WISE, is missing. The context object has been updated and will submitted for ingestion by SBN. file: collection.xml --> SBN to coordinate and create DOI for collection. --> Last author says "Wright10" but believe should be "Wright". --> Please add other meta data for each author and editor: person_orcid, contributor_type (if known), Affiliation, and optionally sequence_number. --> Please expand on the abstract. Especially saying what the two included tables contain. --> Action on PDS: Find a way to ensure comet surveys will be findable via search. This collection specifies the target as "Multiple Comets" of type Comet w/o a context reference. file: 'data/table*' --> The label says the first 3043 and 3604 bytes respectively are for the header, but it is actually the first 3042 and 3603 bytes respectively. That last byte is actually the the first byte for the data portion and so it gets cut off when you load the data using the PDS label. Please update the object_length for the Header object and the offset for the Table_Delimited object. --> The last column "Comet Type" description as found in the PDS label and csv header row says the values should be JFC or SPC, but I think it should be Long Period Comet (LPC) and SPC as is reflected in the csv record values and overview document. file: 'document/BauerEtAl17_AJ_154_53_pdfA.xml' --> Last author says "Wright10" but believe should be "Wright". --> Please add other meta data for each author and editor: person_orcid, contributor_type (if known), Affiliation, and optionally sequence_number. file: 'overview.txt' --> Will the user be confused about talking about two CSV files and then talking about Table 1 and Table 3, with the noticeable omission of Table 2? Should this be clarified? Note that in all PDS labels that Yanga R. "Fernandez" could be "Fernández" utilizing the diacritical marks.