# Presentation: 082214

## Label Design Tool

**Label Design Tool**

- Management Council F2F
- Washington, D.C.

- November 29-30, 2006
- http://pds.nasa.gov

## Background

- The PDS Management Council identified the development of a Data Product Label Design Tool as a key Engineering Node task for 2007. This development task was identified as one of three topics for discussion at the PDS October Technical Session.
- A working group consisting S. Slavney, E. Guinness, M. Rose, A. Raugh (honorary member), R. Joyner, and S. Hughes wrote a draft Use Case document to outline the scope of the tool and derived level 4 and 5 requirements.
- The Design Tool use cases are derived from PDS Level 3 requirements and early PDS node input, especially a straw-man set of design tool requirements written by the Geosciences Node.
- The Technical Session reviewed the Design Tool Use Cases , the level 4 requirements, many of the level 5 requirements, and developed a schedule and implementation plan.

- PDS Management Council

## Scope

- The PDS Data Product Label Design tool is only for label design. It is not intended to generate multiple labels in production mode.
- The user does not need to be a PDS expert because the tool guides the user through the label creation process.
- The tool will use an interactive label editor that gets input from:
- User
- PDS data dictionary (PSDD) and optional local data dictionaries (LDDs)
- PDS standards
- Outputs from the tool:
**PDS label template** that can be used to create PDS data product labels.
**Working Data Dictionary** that collects keywords and values that are not in the PSDD or LDDs.
**Specific Label Object Definition** suitable for validation

- PDS Management Council

## Summary of High-Level Use Cases

- User designs a new product label template with no example inputs
- User designs a new product label template by referencing an existing product label
- User designs a new product label template to describe an actual data file.
- User designs a new product label template to describe an actual data file by referencing a label for a similar data file.
- User designs a new product label template by referencing existing metadata.
- User continues the design of a product label template
- User requests label template validation report

|  |  | Have example label? |  |
| --- | --- | --- | --- |
|  |  | No | Yes |
| Have data file in need of a label? | No | Case 1 | Case 2 |
|  | Yes | Case 3 | Case 4 |

- PDS Management Council

## Summary of Level 4 Requirements

- The Level 4 Functional Requirements are derived directly from the PDS level 3 requirements and the higher level use cases documented in the Data Product Design Tool Use Cases.
- The Tool shall assist the user in designing a label template in one of the following modes:
- L4.LD.1 - The Tool shall assist the user in designing a label template without using an existing data product label or an existing data product as a reference for the design of the new label template.
- L4.LD.2 - The Tool shall assist the user in designing a label template by using an existing data product label as a reference for the design of the new label template. The user may provide the existing data product label or may select one from a set of examples provided by the Tool.
- L4.LD.3 - The Tool shall assist the user in designing a label template by using an existing data object as a reference for the design of the new label template.
- L4.LD.4 - The Tool shall assist the user in designing a label template by using an existing data product label and analyzing an existing data object. The user may provide the existing data product label or may select one from a set of examples provided by the Tool.
- L4.LD.5 - The Tool shall assist the user in designing a label template by translating existing metadata (with or without using a data product label) as input for the design of the new label template.
- The tool shall recognize a limited set of metadata formats, including FITS headers, VICAR headers, ISIS headers, and comma-separated-value text tables in a specific format.
- L4.LD.6 - The Tool shall allow the user to continue a label design session.
- L4.LD.7 - The Tool shall be able to determine and indicate to users the label template components that are non-compliant with the PDS Standards Reference [2].

- PDS Management Council

## Timeline

- Working Group writes Use Case and Requirements documents - Done
- Tech Session reviews documents (Oct 24-25, 2006) - Done
- Present high-level and low-level use cases
- Walk through and update Level 4 requirements
- Walk through Level 5 requirements
- Working Group updates documents based on Tech Session review - Done
- Tech Group reviews documents (Nov 17, 2006) – Done
- Present Status to MC (Nov 2006)
- Complete Level 4 and 5 requirements document (Jan 07)
- WG to review “working data dictionary” structure and uses.
- Prototype the user interface and design the tool
-  Review (May 07)
- Implement
- Release for Alpha Test  (Jul 07)
- Release for Beta Test (Sep 07)
- Operational Release (TBD)

- PDS Management Council

## Backup 

- PDS Management Council

## Level 3 Requirements

- 1.2.1 PDS will provide examples and suggestions on organization of data products, metadata, documentation and software
- 1.2.2 PDS will provide expertise in applying PDS standards
- 1.2.3 PDS will provide expertise to support the design of scientifically useful archival data sets
- 1.3.3 PDS will provide criteria for validating archival products.
- 1.4.1 PDS will define a standard for organizing, formatting, and documenting planetary science data
- 1.4.2 PDS will maintain a dictionary of terms, values, and relationships for standardized description of planetary science data
- 1.4.3 PDS will define a standard grammar for describing planetary science data
- 1.5.1 PDS will provide tools to assist data producers in generating PDS compliant products
- 1.5.2 PDS will provide tools to assist data producers in validating products against PDS standards
- 1.5.3 PDS will provide tools to assist data producers in submitting products to the PDS archive

- PDS Management Council

## Definitions 

**Data Element –** A term that has been defined for use in PDS data product labels or catalog templates and that has been defined in a PDS data dictionary. Also known in the PDS as a keyword.
**Data File –** A storage entity containing one or more data objects; for example, an image or an image plus a header.
**Data Object –** A contiguous sequence of bits, e.g., an image.
**Data Object Description –** An ODL description of a data object.
**Data Product –** A data product label and one or more data objects.
**Data Product Label –** One or more data object descriptions. Also known as a PDS Label.
**Keyword –** A term that has been defined for use in PDS data product labels or catalog templates and that has been defined in a PDS data dictionary. Also known as a data element.
**Label Fragment** – TBD
**Label Template –** An ODL specification that represents a model for a data product label and that can be used for the creation of data product labels either manually or using an automated tool.
**PDS Node –** Any PDS node including science discipline nodes, support nodes, or data nodes.
**Project File –** A file in which the design tool saves the state of the user’s work so that it can be resumed in a later session. The state includes the locations all data dictionaries in use, exported template labels and specific object definitions, and referenced labels, data objects, and metadata files.
**Specific Label Object Definition –** A PSDD definition template to be used for label validation that defines a product label as a specific object with no optional sub-objects or keywords allowed.
**Working Data Dictionary -** A data dictionary with the same structure as a local data dictionary that is created and managed by the design tool for the purpose of collecting objects, keywords, and keyword values that are not present in either the PSDD or a local data dictionary._ _

- PDS Management Council