Call Us: US - +1 845 478 5244 | UK - +44 20 7193 7850 | AUS - +61 2 8005 4826

function of the data.

Collection Types Basic products must be organized into collections based on the type and function of the data. Data providers are expected to assign products to appropriate collections (e.g., only ‘quick-look’ or ‘browse’ products are expected to be assigned to a browse collection); the assignments will be considered during peer review. PDS recognizes the following types of collections. 2 Data providers are not obligated to include physical copies of secondary member products or collections when they deliver bundles to PDS, since the secondary members already exist elsewhere within PDS. PDS, on the other hand, must deliver copies of these secondary members when bundles are distributed (unless waived by the recipient). PDS Standards Reference 1.11.0 2018-10-01 12 A browse collection contains ‘quick-look’ products designed to facilitate use of the archive. Products in a browse collection are defined using appropriate classes; possibilities include Product_Browse and Product_Thumbnail. A calibration collection contains data and files necessary for the calibration of basic products. Products in a calibration collection are defined using the appropriate class; possibilities include Product_Observational and Product_Document. A context collection is the list of products comprising various objects, identified within the PDS4 registry, that are specific to the science bundle. These include physical objects such as instruments, spacecraft, and planets and conceptual objects such as missions and PDS nodes. All products in a context collection will be secondary members of the collection, since the primary versions are curated by the PDS Engineering Node or other responsible agency. A data collection contains observational products, often separated according to processing level, target, instrument mode, etc.; these are the science data that most users seek. Products in a data collection will typically be defined using the Product_Observational class. A document collection includes all components (figures, tables, text, etc.) of one or more related documents. The document collections included with a bundle are those deemed useful by the data preparer and consulting node for understanding, interpreting, and using other collections in the bundle. Documents may include software interface specifications (SISs), calibration reports, and data acquisition summaries, among other topics. Products in a document collection will be defined using the Product_Document class. A geometry collection contains non-SPICE geometry products — for example, Supplementary Experiment Data Record (SEDR) data, gazetteers, tables of anaglyph pairs, or footprint files. Detailed information about particular cartographic projections utilized in the archive may also be included. Products in a geometry collection are defined using an appropriate class; possibilities include Product_Observational, Product_Ancillary, and Product_Document. A miscellaneous collection contains supplementary information deemed by the data provider to be useful in the interpretation and use of other collections in the bundle but which does not fit within the scope of the other collections. For example, meta-data catalogs, data base dumps, and records of modification history could be included. Because of the disparate nature of the files included in a miscellaneous collection, no single class exists for miscellaneous products. The following are some of the possibilities: Product_Ancillary, Product_Document, Product_File_Text, Product_Observational, Product_Thumbnail, and Product_Zipped. An XML schema collection contains all XML schema files included in or referenced by XML labels in the bundle along with any Schematron files created for validation purposes. A bundle is required to contain an XML schema collection unless all of the collection members would be secondary in which case the XML schema collection becomes optional. There can be no more than one XML schema collection per bundle. A SPICE kernels collection contains individual SPICE files and their XML labels, organized by kernel type. Products in a SPICE kernels collection must be defined using the Product_SPICE_Kernel class.