Difference between revisions of "Db-preservation-toolkit"

From COPTR
Jump to: navigation, search
Line 12: Line 12:
  
 
<!-- Add one ore more categories to describe the function of the tool. Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). The following are common category examples, remove those that don't apply -->
 
<!-- Add one ore more categories to describe the function of the tool. Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). The following are common category examples, remove those that don't apply -->
[[Category:Metadata Extraction]]
+
[[Category:Migration]]
[[Category:Preservation System]]
+
 
  
 
<!-- Add relevant categories to describe the content type that the tool addresses. Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. The following are common category examples, remove those that don't apply -->
 
<!-- Add relevant categories to describe the content type that the tool addresses. Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. The following are common category examples, remove those that don't apply -->

Revision as of 11:25, 21 November 2014



Enables conversion between database formats or dumping from live database systems for the purposes of preservation.
Homepage:http://keeps.github.io/db-preservation-toolkit/
License:LGPL v3
Platforms:Platform independent - Java

The Database Preservation Toolkit allows conversion between Database formats, including connection to live systems, for purposes of digitally preserving databases. The toolkit allows conversion of live or backed-up databases into preservation formats such as DBML, an XML format created for the purpose of database preservation. The toolkit also allows conversion of the preservation formats back into live systems to allow the full functionality of databases. For example, it supports a specialized export into MySQL, optimized for PhpMyAdmin, so the database can be fully experimented using a web interface.

Features

At the current version (1.0.0) the following database management systems import/export modules are supported:

  • MySQL
  • MS SQL Server
  • MS Access
  • Oracle (untested)
  • PostreSQL
  • DBML (Database Markup Language)

Additionally it is possible to export a database management system to a specific database SQL using the following export modules:

  • PostgreSQLFile
  • MySQLFile
  • SQLServerFile
  • GenericSQLFile

More import/export modules are being developed at the current time being DB2 one of them. Besides, it is also being developed the modules to support the SIARD database preservation format formats:SIARD. (2014-03-11)


Development Activity

Code is being actively developed at [Database Preservation Toolkit GitHub repository] and [Database Preservation Toolkit GitHub Forked repository]. Lastest version is db-preservation-toolkit 1.0.0 (release at 2013-09-10).


Contributors

Lfaria (21.0%), Andy Jackson (3.4%), Prwheatley (10.8%), Chlara (14.0%), Mcoutada (50.8%)