270 likes | 435 Views
System Design/Implementation and Support for Build 2. PDS Management Council Face-to-Face Mountain View, CA Nov 30 - Dec 1, 2011 Sean Hardman. Topics. Overview Key Drivers and Requirements Build 2 Deliverables Build 2 Deployment Next Steps. Architectural Elements Addressed in Build 2 .
E N D
System Design/Implementation and Support for Build 2 PDS Management Council Face-to-Face Mountain View, CA Nov 30 - Dec 1, 2011 Sean Hardman
Topics • Overview • Key Drivers and Requirements • Build 2 Deliverables • Build 2 Deployment • Next Steps System Design and Support for Build 2
Architectural ElementsAddressed in Build 2 System Design and Support for Build 2
Topics • Overview • Key Drivers and Requirements • Build 2 Deliverables • Build 2 Deployment • Next Steps System Design and Support for Build 2
Build 2 Drivers • Transition the central catalog to the registry infrastructure. • Ingestion of PDS3 and PDS4 catalog-level metadata moving forward. • Facilitate catalog-level search of the registered metadata. • Provide PDS4 software tools to support early adopters. • Includes tools for designing, generating and validating PDS4 product labels. System Design and Support for Build 2
Core Concepts • Service-Based Design • Support remote access to data and services to bring the federation together both for ingestion and distribution. • System of Registries • Adopt a system of registries to support improved tracking and access. • Common Search • A publicly available layer facilitating search across PDS. • Enhanced Tool Suite • A tool-based approach is still appropriate for certain functions. System Design and Support for Build 2
Level 3 RequirementsPertaining to Build 2 System Design and Support for Build 2
Level 3 RequirementsPertaining to Build 2 (cont) System Design and Support for Build 2
Level 3 RequirementsPertaining to Build 2 (cont) System Design and Support for Build 2
Level 3 RequirementsPertaining to Build 2 (cont) System Design and Support for Build 2
Level 3 RequirementsPertaining to Build 3 and Beyond • 3.1.2 PDS will provide online interfaces for discipline-specific searching • 3.1.3 PDS will allow products identified within a search to be selected for retrieval • 3.2.2PDS will provide a mechanism for offline delivery of portions of the archive to users • 3.2.3 PDS will provide mechanisms to ensure that data have been transferred intact • 3.3.2 PDS will provide a capability for opening and inspecting the contents (e.g. label, objects, groups) of any PDS compliant archival product • 3.3.3 PDS will provide tools for translating archival products between selected formats • 3.3.4 PDS will provide tools for translating archival products between selected coordinate systems • 3.3.5 PDS will provide tools for visualizing selected archival products • 4.2.4 PDS will provide a mechanism to upgrade products or data sets which do not meet usability requirements (e.g., data sets from old missions) System Design and Support for Build 2
Topics • Overview • Key Drivers and Requirements • Build 2 Deliverables • Build 2 Deployment • Next Steps System Design and Support for Build 2
Build 2 Deliverables • Initial Distribution Subsystem • This includes the Search component and an updated Data Search interface at the EN. • Replicate EN functionality with PDS 2010 infrastructure. • Ingestion Subsystem • Completed core componentswith support for PDS3 products and keeping pace with changes in the data model. • Tools • A stable suite of tools for early adopters including Design, Generate and Validate tools. • Operations • Configuration of the Report component, selection of an off-the-shelf product for Monitor, and modification of existing search interfaces. System Design and Support for Build 2
Build 2 DeliverablesCore System Components • Registry Service • Provides functionality for tracking, auditing, locating, and maintaining artifacts (e.g., products, services, etc.) within the system. • Harvest Tool • Provides functionality for capturing and registering product metadatawith the Registry Service. • Search Service • Provides functionality for searching the metadata contained in the Registry Service instances. System Design and Support for Build 2
Build 2 DeliverablesSupport System Services • Security Service • Provides the authentication and authorization functions for the system. • Report Service • Provides functionality for capturing and reporting metrics. * These services are satisfied with COTS or Open Source software products. System Design and Support for Build 2
Build 2 DeliverablesTools • Design Tool • Provides functionality for designing product label schemas using the XML Schema standard. • Generate Tool • Provides functionality for generating product labels from and conforming to the specific product schema. • Validate Tool • Provides functionality for validating product labels and product data. System Design and Support for Build 2
Development ProgressBuild 2a – New and Modified Features • Introduced the Search Service and the initial implementation of the PDS Search Protocol. • Modified the Harvest Tool with respect to association handling and representation in the Registry Service. • Updated the Validate Tool with the latest set of schemas for Build 2a. • Updated the Registry User Interface to expand support for viewing additional object types. System Design and Support for Build 2
Topics • Overview • Key Drivers and Requirements • Build 2 Deliverables • Build 2 Deployment • Next Steps System Design and Support for Build 2
Build 2 Deployment • Engineering Node • Deployment of the core components replacing the central catalog. • Will run side-by-side for six months. • Existing search interfaces reworked to utilize the PDS4 infrastructure. • Discipline Nodes • Deployment of the core components at the Nodes will be phased with the Build 2b delivery for testing. • Once deployment and testing is complete, Nodes can begin registration of PDS3 products with the Harvest Tool. System Design and Support for Build 2
Build 2 DeploymentEngineering Node System Design and Support for Build 2
Build 2 DeploymentDiscipline Node System Design and Support for Build 2
PDS3 Support • The Harvest Tool supports both PDS4 registration and PDS3 registration. • PDS3 support consists of converting PDS3 labels into PDS4 proxy labels. • Registered for tracking and reporting purposes. • Will be replaced when the corresponding PDS3 data set is migrated to PDS4. • The current Catalog Ingest Tool is updated to convert the catalog files to context products and register them with the registry. System Design and Support for Build 2
PDS3 Support cont. System Design and Support for Build 2
Topics • Overview • Key Drivers and Requirements • Build 2 Deliverables • Build 2 Deployment • Next Steps System Design and Support for Build 2
Build 2 Liens • Finalize implementation of the Catalog Ingest Tool supporting ingestion of PDS3 catalog files into the PDS4 registry. • Add support for XML Schema 1.1 to the Harvest and Validate Tools. • Upgrade the Data Search interface to remove the dependence on the PDS3 catalog database. System Design and Support for Build 2
Next Steps • Planned for Build 2b • Address any software liens required to achieve operational objectives for Build 2. • Continue development of capabilities targeted for Build 3 deployment. • Planned for Build 3 • Implement data-related tools for transformation and visualization. • Integrate above functionality into PDS search and distribution services. • Replace any existing software (and its functionality) that is dependent on the PDS3 catalog database. System Design and Support for Build 2