Group: org.apache.oodt - All Dependencies

Catalog and Archive Service Generic Multi-valued Metadata Container · A Multi-valued, generic Metadata container class. The class uses an internal Map of string keys pointing to vectors of strings. The data structure looks like the following: [std:string key]⇒std:vector of std:strings The multi-valued nature of the class is handled transparently by this Metadata container. Since all values are stored internally as string vectors, the difference between a scalar value and a non-scalar is handled by determining whether the list of values for a particular key is greater than 1.

Common Utilities · Apache OODT Common Utilities Project

Catalog and Archive File Management Component · The file management component of a Catalog and Archive Service. This component purposefully separates data stores and metadata stores as standard interfaces, and provides some out of the box backend implementations of them (including one based on the javax.sql.DataSource interface). This component provides everything that you need to catalog, archive and manage files, and directories, and their associated metadata.

Catalog and Archive Workflow Management Component · The workflow management component of a Catalog and Archive Service. This component purposefully separates workflow repositories and workflow engines standard interfaces, and provides some out of the box backend implementations of them (including one based on the javax.sql.DataSource interface). This component provides everything that you need to execute workflows, and science processing pipelines.

Query Expression · This component provides a way to express queries in a generic manner. Its centerpiece is a class called XMLQuery that uses boolean postfix expressions to capture the domain, range, and constraint of a query, regardless of the source of the query (SQL, keyword query, etc.). It can also encapsulate the results of a query. It's used by many other components as the standard way to pass a query and its results between servers, clients, nodes, and other components.

Process Control System Core Package · The Process Control System's core system framework. PCS is an agglomeration of CAS services and components needed to build a science data system.

Catalog and Archive Crawling Framework · The Catalog and Archive Service Crawling Framework.

Profile Service · The Profile Service describes and locates resources using metadata descriptions. These descriptions, called profiles, tell of a resource's inception, composition, and location using a mix of Dublin Core and ISO-11179 metadata as well as URIs for locations. The Profile Service catalogs metadata descriptions and provides creating, updating, and querying capabilities.

Product Service · The Product Service provides access to data products. Products can be scientific datasets, images, documents, or anything with an electronic representation. The Product Service accepts standard query expressions (see the Query Expression component) and returns zero or more matching products. In addition, the product service can transform products from proprietary formats and into Internet standard formats or run other transformations, all without impacting local stores or operations.

OODT - Configuration Management · OODT project for distributed configuration management support

Process Control System Input Data Package · The Process Control System's data handling package. This package contains data structures and readers and writers to write an input file format similar to HDF, as represented in XML.

Catalog and Archive Resource Management Component · The resource management component of a Catalog and Archive Service. This component provides job management, and management of the underlying software system hardware and resources, such as disk space, computational resources, and shared identity.

CAS Curation Web Services · Services for ingesting files into the file manager and iteratively extracting metadata.

CAS Product Server Web Application · This project builds on top of the CAS file management component and exposes its underlying data delivery capabilities using the OODT ProductServer component. All-in-all, this project contributes an OODT LargeProductHandler component, that can be used to deliver and format a CAS product structure into an OODT XML Query Result Set.