Archive Data Repository Functional Area

Description

'Archive Data Repository' collects data and data catalogs from one or more data sources and stores the data in a focused repository that is suited to a particular set of ITS data users. It includes capabilities for performing quality checks on the incoming data, error notification, and archive to archive coordination. It includes the capability to define a data registry that allows registration of data identifiers or data definitions for interoperable use throughout a region. It supports a broad range of implementations, ranging from simple data marts that collect a focused set of data and serve a particular user community to large–scale data warehouses that collect, integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region. Repositories may be established to support operations planning, performance monitoring and management, and policy and investment decisions.

Included In

Ohio DOT Traffic Data Archive System
Criminal Justice Information Sharing (CJIS)
NOACA Regional Transportation Data Archive
Cuyahoga County Traffic Count Data Archive
Ohio DPS Crash Records Database
Municipal Traffic Count Data Archives

Functional Requirements

IDRequirement
01The center shall collect data from centers.
02The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the collection of archived data and may include descriptions of the schema or structure of the data, a description of the contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail).
03The center shall store collected data in an information repository.
04The center shall perform quality checks on collected data.
05The center shall notify the system operator of errors related to data collection, analysis and archival.
06The center shall include capabilities for archive to archive coordination.
07The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations, aggregations, or transformations applied to the data before it is stored in the archive.
08The center shall collect data from data distribution systems and other data sources.
09The center shall respond to requests from the administrator interface function to manage center–sourced data collection.
10The center shall respond to requests from the administrator interface function to manage the archive data.
11The center shall respond to requests for archive data from archive data users (centers, field devices).
12The center shall provide a mechanism for archive data users to request archive data by meta–data range.
13The center shall associate meta–data with archived data, including catalog data, statistical products determined from method execution and data longevity.