Db-preservation-toolkit - Revision history

Prwheatley at 14:14, 24 September 2021

2021-09-24T14:14:48Z

Rcdeboer: Added links to Function and/or Content Type

2021-04-20T19:32:50Z

Added links to Function and/or Content Type

Lfaria at 09:26, 16 August 2018

2018-08-16T09:26:09Z

Lfaria at 09:18, 16 August 2018

2018-08-16T09:18:30Z

Chlara: Formatting

2015-01-14T16:28:57Z

Formatting

Chlara: Replace 1. Features with 1. Description

2015-01-14T16:26:35Z

Replace 1. Features with 1. Description

Chlara: Development Activity: Added Release and Activity Feed

2015-01-14T16:23:20Z

Development Activity: Added Release and Activity Feed

MediaWiki default at 21:15, 23 November 2014

2014-11-23T21:15:29Z

Prwheatley at 11:25, 21 November 2014

2014-11-21T11:25:30Z

Prwheatley at 11:24, 21 November 2014

2014-11-21T11:24:00Z

@@ Line 9: / Line 9: @@
 }}
 {{Infobox tool details
-|ohloh_id=db-preservation-toolkit
+|ohloh_id=db_preservation_toolkit
 }}
 == Description ==

@@ Line 1: / Line 1: @@
-<!-- Use the structure provided in this template, do not change it! -->
+{{Infobox tool
 |purpose=Enables conversion between database formats or dumping from live database systems for the purposes of preservation.
 |homepage=https://www.database-preservation.com
 |license=LGPL v3
 |platforms=Platform independent - Java
 }}
 == 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.
@@ Line 57: / Line 50: @@
 <!-- Add the Ohloh.com ID for the tool, if known. -->

@@ Line 38: / Line 38: @@
 == User Experiences ==
 <!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. -->
@@ Line 45: / Line 48: @@
 === Release Feed ===
-Below the last 3 release feeds:
-<rss max=3>https://github.com/keeps/db-preservation-toolkit/releases.atom</rss>
+https://github.com/keeps/db-preservation-toolkit/releases
 === Activity Feed===
-Below the last 5 commits:
-<rss max=5>https://github.com/keeps/db-preservation-toolkit/commits/master.atom</rss>
+https://github.com/keeps/db-preservation-toolkit/commits/master

@@ Line 5: / Line 5: @@
 |purpose=Enables conversion between database formats or dumping from live database systems for the purposes of preservation.
 <!-- |image=image.png -->
-|homepage=http://keeps.github.io/db-preservation-toolkit/
+|homepage=https://www.database-preservation.com
 |license=LGPL v3
 |platforms=Platform independent - Java
@@ Line 19: / Line 19: @@
 == 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 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.
+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:
-At the current version (1.0.0) the following database management systems import/export modules are supported:
+* MySQL/MariaDB
-* MySQL
+* PostgreSQL
-* MS SQL Server
+* Oracle
-* MS Access
+* Microsoft SQL Server
-* Oracle (untested)
+* Microsoft Access
-* PostreSQL
+* And other databases (using JDBC)
-Additionally it is possible to export a database management system to a specific database SQL using the following export modules:
+Database Preservation Toolkit can convert any of the above DBMS to the following preservation formats:
-*PostgreSQLFile
+* SIARD 1
-*MySQLFile
+* SIARD 2
-*SQLServerFile
+* SIARD DK
-More import/export modules are being developed at the current time being '''DB2''' one of them.
+The Database Preservation Toolkit is also capable of loading preserved databases into any of the above DBMS.
 == User Experiences ==
@@ Line 44: / Line 41: @@
 == Development Activity ==
-Code is being actively developed at [http://github.com/keeps/db-preservation-toolkit Database Preservation Toolkit GitHub repository] and [http://github.com/miguelsc/db-preservation-toolkit Database Preservation Toolkit GitHub Forked repository].
+Code is being actively developed at [https://github.com/keeps/db-preservation-toolkit Database Preservation Toolkit GitHub repository].

@@ Line 18: / Line 18: @@
 [[Category:Database]]
 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.
-−
-== Description ==
 At the current version (1.0.0) the following database management systems import/export modules are supported:
 * MySQL

← Older revision		Revision as of 21:15, 23 November 2014
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:Migration]]	+	[[Category:File Format Migration]]

@@ 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 -->
-[[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 -->

@@ Line 3: / Line 3: @@
 {{Infobox_tool
 |name=db-preservation-toolkit
-|purpose=Database Preservation Toolkit
+|purpose=Enables conversion between database formats or dumping from live database systems for the purposes of preservation.
 <!-- |image=image.png -->
 |homepage=http://keeps.github.io/db-preservation-toolkit/