Difference between revisions of "CHRONOS"
(Trial import from script.) |
(Added links to Function and/or Content Type) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{Infobox tool |
|purpose=Database Retirement, Partial and Ongoing Database Archiving, Application Retirement. | |purpose=Database Retirement, Partial and Ongoing Database Archiving, Application Retirement. | ||
| − | |||
|homepage=http://www.csp-sw.de/en/inhalt.php?kategorie=c273_Functions&position=0 | |homepage=http://www.csp-sw.de/en/inhalt.php?kategorie=c273_Functions&position=0 | ||
|license=NDA | |license=NDA | ||
| − | | | + | |function=File Format Migration |
| + | |content=Database | ||
| + | }} | ||
| + | {{Infobox tool details | ||
| + | |ohloh_id=CHRONOS | ||
}} | }} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
= Description = | = Description = | ||
| − | CHRONOS is a commercial product owned by CSP and emerged through a joint research cooperation between the department of computer science at the university for applied science in Landshut. | + | CHRONOS is a commercial product owned by CSP and emerged through a joint research cooperation between the department of computer science at the university for applied science in Landshut. |
Product Description: [http://www.csp-sw.de/en/inhalt.php?kategorie=c272_Solutions_CHRONOS_Product_description] | Product Description: [http://www.csp-sw.de/en/inhalt.php?kategorie=c272_Solutions_CHRONOS_Product_description] | ||
| − | {quote}CHRONOS provides all mandatory bits at the required level of complexity to accomplish the challenges of database retirement as well as the ongoing/continuous and partial archiving scenarios. | + | {quote}CHRONOS provides all mandatory bits at the required level of complexity to accomplish the challenges of database retirement as well as the ongoing/continuous and partial archiving scenarios. |
The file structure of an exported database archive within CHRONOS separates the actual tabular data from its structural description. There are connectors for all major database vendors. Core features Chronos is able to provide is running SQL92 queries on top of the archived data with database like performance, support for revisions, syntactical and semantical schema modifications, resolving cyclic dependency, external referential integrity handling, a full blown access control and data retention layer, etc. Besides the core functionality CHRONOS provides support for the use case of application retirement with tools that allow re-modeling of business objects, application logic and reporting functionality and by being able to directly serve as middleware layer for legacy applications. The rich set of programmatic interfaces allows both to integrate with most of the system’s functionality as well as to grant access to data via standard mechanism as JDBC.{quote} | The file structure of an exported database archive within CHRONOS separates the actual tabular data from its structural description. There are connectors for all major database vendors. Core features Chronos is able to provide is running SQL92 queries on top of the archived data with database like performance, support for revisions, syntactical and semantical schema modifications, resolving cyclic dependency, external referential integrity handling, a full blown access control and data retention layer, etc. Besides the core functionality CHRONOS provides support for the use case of application retirement with tools that allow re-modeling of business objects, application logic and reporting functionality and by being able to directly serve as middleware layer for legacy applications. The rich set of programmatic interfaces allows both to integrate with most of the system’s functionality as well as to grant access to data via standard mechanism as JDBC.{quote} | ||
| Line 43: | Line 40: | ||
= Development Activity = | = Development Activity = | ||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 19:15, 20 April 2021
Description[edit]
CHRONOS is a commercial product owned by CSP and emerged through a joint research cooperation between the department of computer science at the university for applied science in Landshut.
Product Description: [1]
{quote}CHRONOS provides all mandatory bits at the required level of complexity to accomplish the challenges of database retirement as well as the ongoing/continuous and partial archiving scenarios.
The file structure of an exported database archive within CHRONOS separates the actual tabular data from its structural description. There are connectors for all major database vendors. Core features Chronos is able to provide is running SQL92 queries on top of the archived data with database like performance, support for revisions, syntactical and semantical schema modifications, resolving cyclic dependency, external referential integrity handling, a full blown access control and data retention layer, etc. Besides the core functionality CHRONOS provides support for the use case of application retirement with tools that allow re-modeling of business objects, application logic and reporting functionality and by being able to directly serve as middleware layer for legacy applications. The rich set of programmatic interfaces allows both to integrate with most of the system’s functionality as well as to grant access to data via standard mechanism as JDBC.{quote}
User Experiences[edit]
{noformat}@ARTICLE{ author = {Andrew Lindley}, title = {Database Preservation Evaluation Report - SIARD vs.CHRONOS}, journal = {10th International Conference on Preservation of Digital Objects}, year = {2013}, abstract = {Preserving information systems is one of the greatest challenges in digital preservation. In this paper we outline the existing strengths and shortcomings of a record-centric driven preservation approach for relational databases by lining up a state-of-the art industry database archiving tool CHRONOS1 against SIARD2 one of the most popular products in the GLAM (galleries libraries archives museums) world. A functional comparison of both software products in the use cases of database retirement, continuous and partial archiving as well as application retirement is presented. The work focuses on a technical evaluation of the software products - organizational and process aspects of digital preservation are out of scope. We explain why preserving complex structures as databases through a record centric approach does not only depend on the amount of information captured in the preservation package and present a brief overview on available functional aspects in CHRONOS that help to address challenges of application decommissioning. The paper at hand presents the results of a case study which was undertaken 2012 at AIT - Austrian Institute of Technology GmbH.}, }{noformat}
{noformat} @ARTICLE{ author = {Stefan Brandl and Peter Keller-Marxer}, title = {Long-term Archiving of Relational Databases with CHRONOS}, journal = {First International Workshop on Database Preservation}, year = {2007}, month = {March}, } {noformat}