Data Availability Dates Mitch Gordon Emily Law Jordan

Data Availability Dates Mitch Gordon, Emily Law, Jordan Padams, Mike Cayanan

Motivation • At least two issues were identified as a result of the 2018 Cassini DAP. 1. Need for a single source (master calendar) for the projected release dates for all mission data coming into PDS. • Ensure all proposers have equal access to the information when preparing Step 1 Proposals. 2. Need for a single source for the actual dates data became publicly available for all data in PDS. • Ensure all proposers have equal access to the information when preparing Step 2 Proposals. 3/28/19 Gordon 2

Motivation • At least two issues were identified as a result of the 2018 Cassini DAP. 1. Need for a single source (master calendar) for the projected release dates for all mission data coming into PDS. • Ensure all proposers have equal access to the information when preparing Step 1 Proposals. 2. Need for a single source for the actual dates data became publicly available for all data in PDS. • Ensure all proposers have equal access to the information when preparing Step 2 Proposals. 3/28/19 Gordon 3

ROSES 2019 Section C. 1 - 3. 4 Use of Mission Data Spacecraft mission data to be used in proposed work must be available in the Planetary Data System (PDS) or an equivalent, publicly accessible archive at least 30 days prior to the full proposal due date, unless otherwise specified in the program call. Section C. 8 (LDAP) – 1. 2 Sources of Information and Data Whether from the PDS or another source, if the data to be analyzed are not certified or otherwise have issues that might represent an obstacle to analysis, the obligation is on the proposer to clearly demonstrate that such potential difficulties can be overcome. 3/28/19 Gordon 4

3/28/19 Gordon 5

Timing • The long term solution is unlikely to be implemented before the fall build, and maybe not be ready until the subsequent build. • Clearly we need both long term and short term solutions. 3/28/19 Gordon 6

Possible Approaches 1. A table or a set of tables (e. g. , RMS Node ROSES support) 3/28/19 Gordon 7

3/28/19 Gordon 8

3/28/19 Gordon 9

The RMS Node Table • Viewing that table on my 27 inch monitor the table fills ~ 9 pages. • Concatenation to keep the table size manageable. CIRS_0401… would actually require 75 lines if listed by delivery. • This table is only RMS node’s current holdings. • Tables may be too hard to do – or at least not the best long term option. 3/28/19 Gordon 10

Possible Approaches 1. A table or a set of tables (e. g. , RMS Node ROSES support) 2. Searchable database – leverage the Tracking Service? 3/28/19 Gordon 11

Complications (probably not a comprehensive list. ) • Must support PDS 3 and PDS 4 • Must make clear distinctions between the date of the release announcements, the date the data were made publicly available, and the date the data were PDS certified. • EN announcements currently do not include publicly available or certification dates. • Accumulating datasets are not all handled the same way • Cassini – each new delivery contained new volumes (i. e. , the volume numbers incremented). • New Horizons – each new delivery produces a new version of an existing volume. • Under PDS 4, accumulating data generally will parallel the New Horizons algorithm, but the bundles and collections will be identified by LIDVID. 3/28/19 Gordon 12

Requirements on the Discipline Nodes 1. One time – provide the appropriate dates for all existing holdings. 2. With each new release provide the appropriate metadata for the EN data base. 3. If we’re clever in the short term, we won’t have to resubmit to support the long term solution. • How do we handle “Safed” data? 3/28/19 Gordon 13

What’s Next Short Term Solution • EN & Discipline nodes decide what metadata needs to go to EN, and how. • Nodes provide relevant information to EN. • EN posts to a web page or pages to which all users and nodes can refer (definitive source). • Should nodes maintain portion relevant to the node too? (Yes, No, Optional? ) Long Term Solution • Develop a comprehensive requirements document. • EN digest and determine the best approaches (short and long term). • EN schedule development (milestones & projected completion). 3/28/19 Gordon 14

Questions/Comments? 3/28/19 Gordon 15