Tools Discussion

1. Tools Discussion Engineering Node June 2016

2. Topics • EN Action Item • PDS-wide Development Approach • Scope of coordination • PDS-wide Tool Inventory • Tool Registration • Tool WG Proposal • Future of PDS3 Tools

3. EN Action Item • Performance review recommended that EN should be proactive in ensuring that tool development across PDS is coordinated • Maximize use of existing tools • Reduce duplication • Ensure coordination

4. Terminology • Core Tool Development • Tools which can be applied broadly across the PDS and IPDA • Provide a foundation for building PDS4 • Included in PDS4 builds and releases following I&T process • Discipline Node Tool Development • Coordinated by the DNs • Generally have applicability to the DN • Release follows DN practices • Some tools may be candidates to become core tools

5. PDS-wide Development Discipline Node Info Models Distribute to Community Transfer to Core Core PDS Development • (1) Information Models • (2) Software • PDS Core • System Components Change Control Board System Builds (Software+ Model Integration, Regression Testing, etc) System Release Distribute to Community PDS Management, Requirements Transfer to Core Discipline Node Software Tools Distribute to Community

6. Proposed Scope of Coordination • Capture and maintain existing tools across the PDS (both core and DN specific) • Identify needs for common tools and requirements • Ensure that PDS has a well defined Tool Plan/Roadmap • Identify tools that should be transferred and maintained as common

7. Inventory • PDS captured a list of active tools in 2015 which included EN, DN, and IPDA members. • See next slide • This becomes the basis for the Tool Registry • Recommend that PDS continue to maintain the list and provide to a WG for planning

8. Tool Status

9. Tool Status (continued)

10. Tool Status (continued)

11. DN Tool Status

12. DN Tool Status (continued)

13. DN Tool Status (continued)

14. DN Tool Status (continued)

15. DN Tool Status (continued)

16. Tool Registry • Initiated by the desire to expand the scope of the IPDA Tool Registry as well as the 9/28/15 action item to post a list of PDS tools. • Intent is to incorporate all PDS tool sources into a single registry. • The application will be built on top of existing PDS4 components. • The Product_Service class has been updated to support this application (CCB-123).

17. Tool Registry Architecture

18. Tool Registry - Search Page

19. Tool Registry – Submit 1

20. Tool Registry – Submit 2

21. Tool Registry – Submit 3

22. Tool RegistryProduct Label (Minimal Information) <?xml version="1.0" encoding="UTF-8"?> … <Product_Service …> <Identification_Area> <logical_identifier>urn:nasa:pds:context_pds3:service:test_tool</logical_identifier> <version_id>1.0</version_id> <title>Test Tool</title> <information_model_version>1.6.0.0</information_model_version> <product_class>Product_Service</product_class> <Modification_History> … </Modification_History> </Identification_Area> <Service> <name>Test Tool</name> <abstract_desc>This is a test tool.</abstract_desc> <version_id>1.0</version_id> <url>http://localhost:8080</url> <service_type>Tool</service_type> <category>Analysis</category> </Service> </Product_Service>

23. Tool Registry Status • An initial version of the interface is available on our test server. • http://pds-gamma.jpl.nasa.gov/tools/tool-registry • An initial migration of the Search Tools has been completed and loaded into the Registry and Search Services on pds-gamma. • Migration of the IPDA tool registry will be complete by the end of June. • The service will be operational by that date as well.

24. Proposal: Tool Working Group • Charter • Review and update PDS Level 3 requirements for tools • Review PDS-wide tool inventory and identify gaps and overlaps • Recommend tool priority and phasing • Review and comment on specific tool requirements • Maintain PDS-wide Tool Schedule and Plan • Host annual tool summit • Proposed Membership • PDS Engineering (Chair) • Discipline Nodes • IPDA Propose to have formal charter for July telecon

25. Tool Training and Discussion • We believe there is a need to provide hands-on and interactive discussions on tools with the tech staff • More to come later in the agenda on this!

26. PDS3 Planned Tool Support • From 2011 Transition Policy from PDS3-to-PDS4 “…NASA missions confirmed for flight after that date will be required to archive their data according to PDS4 standards, while missions confirmed for flight prior to that date are allowed to continue using PDS3.” https://pds.nasa.gov/policy/PolicyOnTransitionFromPDS3toPDS411162010.pdf

27. PDS3 Support Strategy • Enable backward compatibility in PDS4 tools for PDS3 • As PDS4 tools cover PDS3 functionality, begin deprecating tools which means • Tools will be identified as no longer being maintained • A note will be placed that the tools will eventually not be available online for distribution and use after a specific date

28. PDS3 Tool Deprecation Targets • PDS3 VTOOL (2017) • PDS3 Volume Validation (2017) • PSA3 LTDTOOL (2018) • PDS3 NASAView (2019) Note (1) : The planetary science data dictionary and other PDS3 capabilities will need to be maintained while PDS3 data is still being delivered. Note (2): At EN, most infrastructure is under PDS4.

29. Recommendations • PDS should capture and maintain a list of PDS tools • PDS should maintain that list in a registry • PDS should begin planning for decommission of PDS3 with ample time for course correction • PDS should form a working group on behalf of the Management Council for short and long-term planning of tools