Editing Db-preservation-toolkit

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
{{Infobox tool
+
<!-- Use the structure provided in this template, do not change it! -->
 +
 
 +
{{Infobox_tool
 +
|name=db-preservation-toolkit
 
|purpose=Enables conversion between database formats or dumping from live database systems for the purposes of preservation.
 
|purpose=Enables conversion between database formats or dumping from live database systems for the purposes of preservation.
|homepage=https://www.database-preservation.com
+
<!-- |image=image.png -->
 +
|homepage=http://keeps.github.io/db-preservation-toolkit/
 
|license=LGPL v3
 
|license=LGPL v3
 
|platforms=Platform independent - Java
 
|platforms=Platform independent - Java
|function=File Format Migration
 
|content=Database
 
|name=db-preservation-toolkit
 
 
}}
 
}}
{{Infobox tool details
 
|ohloh_id=db_preservation_toolkit
 
}}
 
== Description ==
 
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 SIARD, a XML-based 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.
 
  
The Database Preservation Toolkit supports the following Database Management Systems:
 
* MySQL/MariaDB
 
* PostgreSQL
 
* Oracle
 
* Microsoft SQL Server
 
* Microsoft Access
 
* And other databases (using JDBC)
 
  
Database Preservation Toolkit can convert any of the above DBMS to the following preservation formats:
+
<!-- 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 -->
* SIARD 1
+
[[Category:File Format Migration]]
* SIARD 2
+
 
* SIARD DK
 
  
The Database Preservation Toolkit is also capable of loading preserved databases into any of the above DBMS.
+
<!-- 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 -->
 +
[[Category:Database]]
  
== User Experiences ==
+
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.
<!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. -->
 
  
* https://zenodo.org/record/1171715
+
== Features ==
* https://zenodo.org/record/1173099
+
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)
  
== Development Activity ==
+
Additionally it is possible to export a database management system to a specific database SQL using the following export modules:  
Code is being actively developed at [https://github.com/keeps/db-preservation-toolkit Database Preservation Toolkit GitHub repository].
+
*PostgreSQLFile
+
*MySQLFile
 +
*SQLServerFile
 +
*GenericSQLFile
  
=== Release Feed ===
+
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)
  
https://github.com/keeps/db-preservation-toolkit/releases 
+
<!-- == User Experiences == -->
+
<!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. -->
=== Activity Feed===
 
  
https://github.com/keeps/db-preservation-toolkit/commits/master
+
== Development Activity ==
+
Code is being actively developed at [[https://github.com/keeps/db-preservation-toolkit Database Preservation Toolkit GitHub repository]] and [[https://github.com/miguelsc/db-preservation-toolkit Database Preservation Toolkit GitHub Forked repository]]. Lastest version is db-preservation-toolkit 1.0.0 (release at 2013-09-10).
  
 
<!-- Add the Ohloh.com ID for the tool, if known. -->
 
<!-- Add the Ohloh.com ID for the tool, if known. -->
 +
{{Infobox_tool_details
 +
|ohloh_id=db-preservation-toolkit
 +
}}

Please note that all contributions to COPTR are considered to be released under the Attribution-ShareAlike 3.0 Unported (see COPTR:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)