Data Standards Development

August 29, 2012

2

Topics

1. Current Status2. What was delivered for Build 2c3. How was IPDA supported4. What mission support is being provided5. What will be delivered for Build 3a6. Status of RFAs7. Plan for FY13

3

Current Status

• Node bundle development and testing has allowed significant progress toward stabilizing the PDS4 core data standards.• The resulting RFAs have been much more specific and

have help to mature the core information model and resulting schemas.

• Issues with significant impact on core software (registry and harvester) have been identified and are being addressed for build 3a.

• After build 3a the work will be realigned toward supporting data users, specifically in the discipline and mission level areas of the model.

What was delivered for Build 2c

• Posted PDS4 Data Standards release 0800k for operational use.• Release 0800k was primarily a maintenance release

with about 66 changes due to RFAs from previous builds.

• Added support for additional data products including those with images and bit fields.

• Improved support for MAVEN and LADEE. • Migrated the PDS3 central catalog content to PDS4

context products. • Documents posted to http://pds.nasa.gov/pds4 (not

yet linked from homepage)• Released new versions of the DPH and Standards

Reference.

How was IPDA supported

• Synchronized the 2012 IPDA “PDS4 Prototype” project activities with PDS4 build 2b and 2c releases.• The project prototyped a PDS4 product pipeline.

• The IPDA project provided review comments for:• Information model• XML Schemas• Documentation

• Also provided development input for local data dictionary prototype and conversion tools

6

Mission Preparation - LADEE

• Schedule• SIS development has begun – ready for

review by end of October 2012• Review of sample products and SIS

complete by end of January 2013• Completion of liens by June 2013• Launch end of July – Beginning of August• Early 2014 – first data delivery

7

Mission Preparation - LADEE

• Instruments: • Ultraviolet/Visible Spectrometer (ATM) • Neutral Mass Spectrometer (ATM) • Lunar Dust EXperiment (SBN)

• Data types:• ASCII tables

• Requirements on PDS4 Data Standards • Character Table: These are stable enough

in the current version to support LADEE.

8

Mission Preparation - MAVEN• Schedule• SIS development has begun• 2015-Apr: first data delivery

• Instruments: • 4 particle, MAG, Plasma wave.

• Data types:• ASCII tables and binary tables

9

Mission Preparation - MAVEN• Requirements on PDS4 Data Standards • character and binary tables: These are stable

enough in the current version to support MAVEN.

• bit fields – These have been successfully tested using selected Radio Science data. Searching for remaining issues. 

• delivery packages – Three packages have been prototyped and are under review. They are based on the original PPI concept and the OAIS Information Package.

10

Mission Preparation - Bepi Colombo

• Schedule• Begin prototype labels in November with

instrument teams

11

What will be delivered for Build 3a

• Collection.Inventory – Separated the logical from the physical

• Primary Results Summary – Identified a set of cross-discipline search attributes and values.• Discipline specific values will be placed in the discipline

area of the label

• Vector/Quaternions – Review and finalize models.• Define the Local Data Dictionary • Synchronize standards documents to the build

release of the information model• Glossary, Standards Reference, DPH, Data Dictionary, and

Data Provider’s WIKI .

• Plus additional resolved RFAs

RFA Status

• Summary of Major Changes since Build 2c • Simplified the Collection.Inventory by moving the physical

information to a separate structure and changed the format to Delimited.Table.

• Redesigned the Primary_Result_Description class.

* RFAs have become very specific, but generally result in simple changes12

SUMMARY ACCEPTED 0 PENDING 39 IMPLEMENTED 108 DELIVERED 15 CLOSED 85 POSTPONED 9TOTAL 256

RFA Statuses

13

.• ACCEPTED – RFA reviewed, accepted and in queue; work not yet started.

• PENDING – RFA reviewed, accepted but little work done.

• IMPLEMENTED – RFA reviewed, accepted, and work completed. Re-review and re-opening allowed.

• DELIVERED – RFA reviewed, accepted, and work completed. Released in build.

• POSTPONED – RFA reviewed and accepted but work scheduled for later build.

• CLOSED – RFA reviewed and either subsumed or contradicts a DDWG decision. No work done.

RFA Resolution Philosophy

14

.• Anyone can submit an RFA.

• Each RFA is bookkept and reviewed.

• First decision point is whether the RFA contradicts a previously made DDWG or system decision. If so the RFA is closed.

• An RFA can be also be closed if it can be subsumed by a similar RFA.

• Second decision point is whether the RFA is actionable. If so then the work is done.

• Finally it is assumed that the RFA requires DDWG discussion. It is put on the DDWG agenda for discussion and resolution.

Example RFAs

15

.  • Determine impact of updated ebXML standard on PDS4 system and

data - Closed  

• Modification_Detail has cardinality 1 when used in Modification_History. – Implemented

• No default unit for file_size is specified. – Implemented

• Grouped fields appear to be a mess. – Delivered

• Naming of types and elements should be consistent. (E.g., Array_2D vs. UnitOfMeasure_Storage) – Pending

• Array_Element scaling_factor and value_offset - It would be very convenient if a default value were given. – Pending

16

Plan for FY13• Align the Standards Reference with the Information

Model.• Support deployment of the PDS4 system

• Support the development of web services for PDS4 Data Standards. (e.g. Data Dictionary service)

• Refocus efforts to discipline and mission level areas of the model• For example cartography, geometry, and calibration

• Augment regression test suite with the node Bundle tests and make them available to developers.

• Update and activate Standards Change Control Process for PDS4

Backup

17