200 likes | 309 Views
User Working Group 2013. Data Management System – Status 12 March 2013 http://podaac.jpl.nasa.gov. PO.DAAC Functional Areas. Data Access. Data Management & Stewardship. Provide intuitive services to discover, select, extract and utilize data .
E N D
User Working Group 2013 Data Management System – Status 12 March 2013 http://podaac.jpl.nasa.gov
PO.DAAC Functional Areas Data Access Data Management & Stewardship Provide intuitive services to discover, select, extract and utilize data Preserve NASA’s data for the benefit of future generations Science Information Services Provide a knowledgebase to help a broad usercommunity understand and interpret satellite ocean data and related information
PO.DAAC Functional Areas Data Access Data Management & Stewardship Provide intuitive services to discover, select, extract and utilize data Preserve NASA’s data for the benefit of future generations Science Information Services Provide a knowledgebase to help a broad usercommunity understand and interpret satellite ocean data and related information
High-Level Functions Data Providers Information Providers Consumers Information In Data In Information Out Data Out High-Level Access Tools Ingest Web Portal Visualization Web Services & Publishing Direct Data Access Inventory Archive
High-Level Functions Data Providers Information Providers Consumers Information In Data In Information Out Data Out High-Level Access Tools Ingest Web Portal Visualization Web Services & Publishing Direct Data Access Inventory Archive
Applicable 2012 UWG Recommendations • Recommendation 4 – Annualdataset gap analysis and prioritization Closed. (Just noting that the DGAP adoption process is referenced in the DSLP.) • Recommendation 6 – Create public webpage that documents PO.DAAC’s best practices: Open. (The Dataset Lifecycle Policy captures PO.DAAC best practices, but we have not yet gone public.) • Recommendation 7 – Creation of a dataset lifecycle policy: Closed. (Done, being applied to every new dataset, and refining / improving it as we uncover lessons-learned.) • Recommendation 8– Work with GHRSST on metadata practices: Closed. (Just noting that GHRSST is aware of our Dataset Lifecycle Policy, and is incorporating its basic constructs into their own approach.)
Outline Purpose of this Presentation: Status the Data Management System: Business processes, and IT infrastructure Presentation Outline: Data Management System = BP + IT Catching up IT Infrastructure Status Business Process Status
BP + IT PO.DAAC Data Management System Business Processes IT Infrastructure = + IT Infrastructure Includes hardware, software, networks, interfaces, etc. Examples: • Site Crawler capability • Data Handler capability • Data Reader capability • Data Dictionary implementation • Data Catalog capability • Data Archive capability • Server Infrastructure • Network Infrastructure • Storage Infrastructure Business Processes Includes policies, process descriptions, templates, procedures, etc. Examples: Overarching Dataset Lifecycle Policy Memorandum of Understanding template Data Management Plan template Database Audit procedure File Audit procedure Data Acceptance Policy Data Dictionary management process Dataset Types definitions Remote Dataset Policy/Approach
System Integration:Business Process and IT Services BP IT BP IT IT IT Maturity BP IT IT BP BP BP 2009 2010 2011 2012 2013 2014 2015
Infrastructure System Deliveries Already put significant effort into IT Solid baseline established in the first evolution Major pieces are in place and working smoothly That stability provides opportunities Reaping the benefits of a solid foundation
Business Practices IT is stabilized, so… Turning attention to business practices / processes Began with the Dataset Lifecycle Policy Working on tallying a list of all needed processes
Data Management System Business Processes (BPs) 2012 2013 2014 2015 SDLC A&C 1 Remote DSLP 1 UseCase DSLP 2 Templates DOIs Dictionary Types DB Audit A&C 2 File Audit
Data Management System Business Processes (BPs) 2012 2013 2014 2015 SDLC A&C 1 Remote DSLP 1 UseCase DSLP 2 Templates DOIs Dictionary Types DB Audit A&C 2 File Audit Note: Green = Defined processes. Orange = processes being actively worked.
BP: Dataset Lifecycle Policy controlled by… assigned to… Documents Templates Dataset Lifecycle Policy is written and active Worked via iterative discussions Document driven Consistent approach + best practices Follow the template, follow the policy. A living document Best Practices
Lifecycle Phases and Documents 4 6 7 8 Dataset Identification ✓ Dataset Approval ✓ ✓ ✓ Prepare the System ✓ Draft On New Version Integration ✓ Draft Draft Operations ✓ ✓ On Deprecation Retirement ✓
BP: Data Types Next BP we’re tackling is data types Came up in discussions of DSLP Clear we have a disconnect in both definition and flow
Data Types *Other miscellaneous types exist, for example: Dormant and Simulated
Current Type Progression Shared Open Retired Mission Datasets Controlled Community Datasets Preview Retired Open
Data Types Types and Lifecycle Policy not aligned Some types set visibility, others indicate progress Flow / progression doesn’t align Recognize there’s a problem, so working it Beginning with Remote