UWO and CAMS Meteor Data Liens ============================== Documentation ============= directory: 'document/' (UWO Meteor Radar Complex Document Collection) --> Both the Meteor Showers and Meteor Orbits collections are CAMS data, not UWO / Canadian Meteor Orbit Radar (CMOR) data. Since all references to UWO and CMOR must be removed from the data collections, evaluate whether this UWO CMOR document collection belongs in this bundle at all. --> If kept: - Why wasn't the 'observatory.uwo_meteor_radar.*' files originally delivered included here? The meteor_orbits copy has more information, though 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, though 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? - In 'uwo_meteor_radar.cmor.cmor_inst.txt', add "Instruments" to the title, and fix the typo: "no echoes are processed with their nominal elevation is below 20 degrees" => "if their nominal elevation is below 20 degrees". file: 'meteor_showers/overview.txt' --> A brief introduction is needed before launching into details. --> The text mentions "reference above", however no reference is provided in the text. Add the full citation from 'readme.pdf' (Jenniskens P., 2023. Atlas of Earth's Meteor Showers. Amsterdam: Elsevier, 838 pp). --> Major Issue (Paywalled Book Dependency): The dataset, parameter definitions, and methodologies (referred to Chapter 2 and specific page numbers of Jenniskens 2023) rely on a commercial book that is not open access. Data provider must provide original summary text in 'overview.txt' (and/or the documentation/labels) that defines all parameters in the table and explains the methodologies/derivations used to obtain the values. --> Unapproved IAU Meteor Showers: Some meteor showers in the dataset have been submitted to the IAU but are not yet officially approved/defined. Add a prominent note in the documentation (and labels) stating that these meteor showers have been submitted to the IAU and are awaiting official IAU approval (please check the official IAU list), and that the dataset will be updated in a later version (v2.0) once official IAU designations/numbers are finalized. file: 'meteor_showers/document/readme*' --> Clarify why 'readme.pdf' is provided if it does not add information beyond the table/overview, or merge its definitions into 'overview.txt' and the XML labels. file: 'meteor_orbits/overview.txt' --> Suggestion: use a more succinct title. --> The current text reads more like an abstract. More information is needed about what the tables provide, and how the parameters in the tables were derived (or refer to the relevant open-access papers). --> If 'readme_camsv3_0_pdfa.pdf' is kept, mention the references in 'overview.txt' (under "References"). --> Include a document/table in the 'document/' directory that maps the participating CAMS camera/station numbers (in the 'stations' column) to their actual station/camera identifications and locations, rather than forcing users to look up an external paper to decode the camera numbers. Data ==== Both Data Collections --> Remove/change ALL references to UWO and/or Canadian Meteor Orbit Radar (CMOR) in the embedded CSV headers (e.g., "Observing System Bookmark" in 'jenniskens_2023_listofshowers_embedded.csv' and 'cams_YYYY_embedded.csv'), as this is CAMS data, not UWO/CMOR data. --> Missing constants are often specified in the label and table headers but are not used in the table columns. Omit them if not used, or define what it means when a field is empty and whether a missing constant should be used. Meteor Showers ('meteor_showers/data/jenniskens_2023_listofshowers_embedded.csv') --> Remove the header line starting with "-99". --> Expand and clarify insufficient or cut-off column descriptions and units (in both the CSV header and XML label, applying to both 'video_' and 'radar_' prefixes where applicable): - PB Certainty (Level of certainty in parent body identification): Explain the method/computation for this parameter and specify what values of 1, 0.5, or 0 mean. - video_peak_sollong: Description is confusing; clarify if it means peak activity at solar longitude. - video_ra_drift [dec] [lambda] [beta] [i] [w] [node] [pi]: The unit should just be "degree". - video_vg_drift: The unit should just be "km/s". - video_q_uncertainty [pi]: States "observed one s dispersion"—clarify that this is 1-sigma dispersion. - video_q_drift: The unit should just be "AU". - video_chi: Explain what a magnitude distribution index is. - 48 / video_s (Mass distribution index): Explain what a mass distribution index is, and specify whether it is differential or cumulative (most likely differential). - 54 / video_fragile_flag: The description is an incomplete/cut-off sentence ("=1 indicates meteoroid fragmentation; -1 is"). Please complete. - video_source_video (and radar_ equivalent): Explain the entries (e.g., what do "C" and "V" stand for?). - orbit_type_a_group: Clarify "flag = 1 if a=0.86 and =65?". - orbit_type_lpc_pi_drift: Define "anomalous" and "aMo cluster". - orbit_type_attack_angle: Define "Earth Vh". - activity_sumnmpm_video [visual]: Define N(m) and P(m). - lightcurve_f_type: Define "F-value shape". - lightcurve_a1 & lightcurve_a2: Define deceleration values a1 and a2. - summary_n_: Define types (Ia, II, IIb, IV). Meteor Orbits ('meteor_orbits/data/cams_YYYY_embedded.csv') --> Note: The association to meteor showers will need to be updated in a future version once the IAU decides on the official names and designations of several showers. --> data_type for "number" should be integer. --> Change "Date of event" to "UT date of event". --> Describe what the acceleration parameter is (either in the column description or in 'overview.txt'); note that the given unit is "km/s", which is a velocity. --> max_mv: Zero point is given in irradiance, while max_mv is magnitude. Please clarify. --> stations: The data is currently formatted with leading/separating underscores (e.g., "_000802_000323") representing participating camera numbers. Please replace the underscores with a space as the delimiter between camera numbers, clarify the format in the description, and point to the new camera ID lookup document in the dataset. --> shower-id & component-id: Clarify whether 0 is really a shower-id/component-id or if it is a missing constant. --> pairs_flag: Clarify what a flag = 0 means, or if it is a missing constant. Labels ====== All XML Labels (Bundle and All Collections) --> Remove/change ALL references to UWO and/or Canadian Meteor Orbit Radar (CMOR), as this is a different instrument/institution. This includes: - Updating the bundle and collection LIDs so they do not contain "gbo-uwo_meteor_radar" (e.g., 'urn:nasa:pds:gbo-uwo_meteor_radar:meteor_shower:...'). - Removing entries for "Canadian Meteor Orbit Radar" and "UWO Meteor Radar Complex", and removing the to 'urn:nasa:pds:context:instrument:uwo_meteor_radar.cmor.cmor_inst'. - Replacing them with the appropriate CAMS context objects (coordinate with SBN/EN to create or look up the proper CAMS context objects). --> Strongly recommend using the same Information Model (IM) version for all products in the bundle. Update the bundle, document, and meteor_shower labels from IM 1.15.0.0 to 1.24.0.0 (matching meteor_orbits). --> Several PDS4 XML label files have Citation_Information.publication_year values of 2024 or 2025 (including 'document/collection.xml' and 'meteor_showers/collection.xml'). Update all publication_year values to 2026. --> Please add additional metadata for each author and/or editor across the collection and product labels (enabled by IM 1.24.0.0): full name, person_orcid, contributor_type (if known), Affiliation, Funding Institution ROR ID# and name, and optionally sequence_number. --> : Remove Spectroscopy (and check Radio in collection.xml), as these datasets are not spectroscopy results. Replace with an appropriate discipline/facet term or omit if none fits. --> : Currently lists Multiple and Meteoroid Stream. Update this to use a more descriptive name such as "Multiple Meteor Showers" / "Multiple Meteoroid Streams". (Note: Individual meteor shower context objects are not needed at this time). --> Action for SBN: The context object for 'facility:observatory.uwo_meteor_radar' needs to be updated (the last update noted adding instrument and telescope references that were never added). file: 'meteor_showers/collection.xml' --> Suggest renaming the collection from "Data collection..." to "Database...", or reworking the title. --> Please expand the Citation_Information.description to include the correct facility/instrument (CAMS, not UWO CMOR). --> SBN to coordinate and create DOI for collection. --> If there is a DOI for the referenced publication(s) that this database is sourced from, please add it as an External_Reference in this file. file: 'meteor_showers/data/jenniskens_2023_listofshowers_embedded.xml' --> Update all column descriptions and units to match the corrections made in the CSV file. --> Please add an area to File_Area_Observational (Header object) that describes the header bytes in the CSV file. --> If 'document/readme*' is retained and important to understanding the data, reference it in the Reference_List. file: 'meteor_orbits/collection.xml' --> Recommend putting "(CAMS)" in the <title> as is done in the <description>. --> Fix typo in abstract: missing opening "(" for "(CAMS)". --> SBN to coordinate and create DOI for collection (also noted for 'meteor_orbits/overview.txt'). --> The two papers referenced in 'overview.txt' appear pertinent to understanding the source of data for this collection as a whole and should be added to the Reference_List here. file: 'meteor_orbits/data/*.xml' --> Transfer the column descriptions from the 'data.csv' files into the 'data.xml' labels, as the CSV descriptions are more comprehensive (and ensure they are consistent with each other and include the data corrections noted above). --> The "date" column is described as a UTF8_String with data formatted as mm/dd/yy. Please add the exact date format (mm/dd/yy, so it is not confused with dd/mm/yy) and specify that the year is in the 20xx century in the field <description>. --> In the "stations" column <description>, explain how the camera numbers are formatted/delimited and point to the document in the bundle where users can decode the camera numbers. --> If 'document/readme*' is retained and important to understanding the data, reference it in the Reference_List.