Listed below are the liens/RIDs that were found at the PDS/PSA February 2016 review of the Prelanding thru Escort 1 phases of the Rosetta mission. Even though this particular data set may have not participated in the review, it uses the same pipeline and so the liens likely apply here as well. Please take note that some issues may be resolved, while others are not. If any other issues are discovered please let the PDS-SBN know. It is expected that a fully lien resolved version will be produced during post mission ops and archived with an incremented data set version number. 1)Reference ID (RID): RO-AR-RID-ESA/PSA-101-EG Dataset: Orbit, attitude and instrument pointing information Location: Ancillary data: SPICE Title: ASCII orbit/attitude information Description: Rosetta results appeal to space researcher, astronomers, cosmo-physiscists, and cosmo-chemists. Only the former are familiar with SPICE software. More accessible information than SPICE kernels is needed for supporting useful interaction to the Rosetta archive. E.g. comparing dust data from GIADA, RPC, and OSIRIS requires that one has a good understanding of the corresponding observation geometries without becoming a SPICE expert. For good reason PDS and RSA requires instrument data in simple ASCII tables. SPICE is a powerful tool kit to get orbit and attitude information for Rosetta and most other space missions. But in order to make use of it expensive software infrastructure (like IDL or Matlab) is needed which is no problem for most science institutions but for independent scientists (like me) it may not be available. Even JPL Horizons web site and the Rosetta 3dtool provide ephemerides and other relevant parameters in various formats including plain ASCII tables. Proposed solution by Reviewer: Orbit/attitude and instrument pointing information in ASCII format: Rosetta position and Instruments (e.g. COSIMA collector) pointing in ECL J2000, CG_SUN_SPIN, and other relevant frames. Like the JPL Horizons web site: http://ssd.jpl.nasa.gov/horizons.cgi Review board discussion outcome and Instrument team response: Accepted by PSA, will be investigated 2)Reference ID (RID): RO-AR-RID-COSIMA-101-EG Dataset: COSIMA CATALOG Location: DATASET.CAT Title: collector aperture geometry Description: The description in DATASET.CAT is insufficient to characterize the concentration effect of the Proposed solution by Reviewer: collector aperture. For this one needs the width and height (in m) of the dust funnel in relation to the positions of the three collector targets. Provide detailed collector aperture geometry information. Review board discussion outcome and Instrument team response: accepted 3)Reference ID (RID): RO-AR-RID-COSIMA-102-EG Dataset: COSIMA Location: Mass spectra Title: Mass scale and dead time correction Description: Interpretation of COSIMA mass spectra requires a precise mass scale and the correction of dead-time effects. The COSIMA Team (Silen et al., and Lehto et al., Geosci. Instrum. Method. Data Syst. Discuss., 2014) is currently developing sophisticated methods to solve both problems. Proposed solution by Reviewer: Provide Mass scale and dead time correction Review board discussion outcome and Instrument team response: accepted, the team is already working on this 4)Reference ID (RID): RO-AR-RID-COSIMA-103-EG Dataset: COSIMA Location: Mass spectra Title: Composition calibration Description: "COSIMA is a specialized instrument with unique characteristics. For calibration the only two laboratory setups in Göttingen and in Orleans have been used by the COSIMA Team: - spectra of inorganic compounds by Krüger et al., PSS, 2015 and - spectra of solid organic grains by LeRoy et al., PSS, 2015. " Proposed solution by Reviewer: It is requested that calibration data are submitted to PSA in a similar format as flight data. Review board discussion outcome and Instrument team response: accepted 5)Reference ID(RID): RO-AR-RID-COSIMA-104-EG Dataset: COSISCOPE Location:IM_x.LBL Title: Completeness of images Description: Frequently, only partial images are given without notification which sub-images are contained in the FITS file. It is requested that the image label file (IM_x.LBL) contain the appropriate information. Proposed solution by Reviewer: Characterize in image LBL whether complete image or partial image and which parts are shown in the corresponding FITS image. Review board discussion outcome and Instrument team response: accepted, already implemented in the next delivery 6)Reference ID(RID): RO-AR-RID-COSIMA-105-EG Dataset: COSIMA Location: Grain lists and mass spectra Title: Particle names list Description: Papers (e.g. Hilchenbach et al., ApJ, 2016 or Langevin et al., Icarus, 2016) that describe COSIMA results like particle compositions or structural properties identify the grains by names like: Estelle, Nyle, Veronique, Stefanie, Yuri, Charlotte, Gabriel, Pavel, Donia, Konstantin and others. These grain names including the collector target, their x, y positions and other properties like type, size, and height should be given in a table. Proposed solution by Reviewer: Provide list of named particles and their collector substrates and coordinates. Review board discussion outcome and Instrument team response: accepted, the team is already working on this 7)Reference ID (RID): RO-AR-RID-COSIMA-106-EG Dataset: COSISCOPE Loaction: GR__.TAB Title: Test images Description: Occasionally particle lists refer to test images: CS_2D0_20140721T032536_ GR__.TAB and CS_2D0_20140721T172540_GR__.TAB which are not identified in the header or otherwise. Appropriate identification should be given. Proposed solution by Reviewer: Identify particle lists (GR__.TAB) from test images (patterns) of COSISCOPE. Review board discussion outcome and Instrument team response: accepted 8)Reference ID (RID): RO-AR-RID-COSIMA-107-EG Dataset: COSISCOPE Location: GR__.TAB Title: Conditions during image taking Description: Analysis of grain lists GR__.TAB show significantly varying numbers of particles due to different conditions during image taking (illumination, substrate offsets and rotations). This should be indicated in the data description. Proposed solution by Reviewer: Identify conditions (illumination, substrate offsets and rotations) during image taking. Review board discussion outcome and Instrument team response: accepted 9)Reference ID (RID): RO-AR-RID-COSIMA-108-EG Dataset: Substrate history files Location: *_SUBSTRATE_HIST.TAB Title: Consitsent labeling of grain lists Description: in Substrate history files dust position lists are listed under IMAGE instead of GRAINS Proposed solution by Reviewer: label grain lists consitsently Review board discussion outcome and Instrument team response: accepted 10)Reference ID (RID): RO-AR-RID-COSIMA-101_SK Dataset: ro-c-cosima-3-v2.2 Location: cosimasis.pdf Title: Spelling mistakes Description: Multiple spelling mistakes Proposed solution by Reviewer: Correct the spelling mistakes Review board discussion outcome and Instrument team response: Documentation needs some TLC and accepted 11)Reference ID (RID): RO-AR-RID-COSIMA-102_SK Dataset: ro-c-cosima-3-v2.2 Location: cs_1d0_substrate_hist.tab Title: Missing table Description: cs_1d0_20141005t043347_sp_p.tab listed in the history file is missing Proposed solution by Reviewer: Verify that the volume really contains all files listed in the history tables Review board discussion outcome and Instrument team response: Team says they know why this happened and will fix it. 12)Reference ID (RID): RO-AR-RID-COSIMA-103_SK Dataset: ro-c-cosima-3-v2.2 Location: cosima_spectrum_peaks.fmt, cosima_spectrum_peak_scale.fmt Title: Incosistent collumn names Description:"The flag names are used inconsistently. E.g. the fflag INDEX refers to either time (index), or, in the peaks table, to masses. Often the descriptions are not comprehensible. interpretation of what values represent varies from record to record based on (poorly identified and explained) flag fields." Proposed solution by Reviewer: Use descriptive flag names, e.g. TIME_INDEX and MASS instead of INDEX. Improve the descriptions. Review board discussion outcome and Instrument team response: No response from team - presumably accepted 13)Reference ID (RID): RO-AR-RID-COSIMA-104_SK Dataset: ro-c-cosima-3-v2.2 Location: - Title: Add grain spectra table. Description: It is extremely difficult to identify spectra of interest. Proposed solution by Reviewer: Add a table which lists all spectra tables of collected dust grains together with the target ID, scan time, etc. Review board discussion outcome and Instrument team response: Will add something 14)Reference ID (RID): RO-AR-RID-COSIMA-105_SK Dataset: ro-c-cosima-3-v2.2 Location: cosimasis Title: Improve descriptions of tables Description: Improve the table descriptions, in particular the description of the peaks table. Proposed solution by Reviewer: - Review board discussion outcome and Instrument team response: No response from team - presumably accepted 15)Reference ID (RID): RO-AR-RID-COSIMA-105_SK Dataset: ro-c-cosima-3-v2.2 Location: cosimasis Title: CODMAC Level Description: The CODMAC level of the data is not really clear. Clearly describe and justify the CODMAC Level of the data in the SIS. Proposed solution by Reviewer: - Review board discussion outcome and Instrument team response: will clarify 16)Reference ID (RID): ro-c-cosima-102-RE Dataset: ro-c-cosima-3-v2.0 Location: document/cosimasis.pdf Title: nits in cosimasis.PDF Description: " - Section 4.3.6.2: the formatting broke down for COSIMA_HEATING_DATA.FMT (change font, not lined up, hard to read, can skip) - Section 4.3.7: No cleaning products or such .fmt files were in this volume. Perhaps there were none for this dataset? - Section 4.3.8: Also no cleaning housekeeping or such .fmt files. - Section 4.3.11: the COSISCOPE_HK.fmt file in this pdf lists 54 columns, but the actual file in label/cosiscope_hk.fmt has 55" Proposed solution by Reviewer: correct document Review board discussion outcome and Instrument team response: 17)Reference ID (RID): ro-c-cosima-101-SB Dataset: ro-c-cosima-3-v2.0 Location: instrument_host.CAT Title: update of instrument_host.CAT Description: The instrument_host.CAT provided is not the reference one Proposed solution by Reviewer: update Review board discussion outcome and Instrument team response: -