Editing SIARD Suite

{{Infobox tool
|purpose=SIARD Suite is a freeware tool for the conversion of contents of relations databases into the SIARD format.
|homepage=https://www.bar.admin.ch/bar/en/home/archiving/tools/siard-suite.html
|license=Vendor-specific licence agreement. Redistribution prohibited
|platforms=should run under Java 1.8 on any operating system
|formats_out=SIARD
|function=File Format Migration
|content=Database
}}
{{Infobox tool details}}
== Description ==
<!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. -->
SIARD Suite extracts the contents from a relational database and saves them in the SIARD format which is appropriate for archiving. 

In this format, the data is stored for future generations and can be uploaded into a new database that may differ from the original. 

Therefore, this method allows to retain data independently of the original database and to reuse them in the future in modern database systems. 
 
 
==== SIARD format ====
SIARD stands for Software Independent Archiving of Relational Databases. Originally the Swiss Federal Archives (SFA) have developed the SIARD format as a sustainable solution for the archiving of relations databases. 
 
In early 2013 SIARD format has been adopted as an eCH Standard (eCH-0165: SIARD format specification http://www.ech.ch/vechweb/page?p=dossier&documentNumber=eCH-0165).
 
eCH is the Swiss organization for standardization in the field of e-government. eCH Standards define guidelines for recurring applications and their results, as for example format definitions or procedural standards. The aim of those standards is to unify and thus facilitate the electronic collaboration between authorities as well as between authorities and organizations, educational and research institutions, firms and private organizations. 
 
 
==== Which types of databases does SIARD Suite support? ====
* Oracle
* Microsoft SQL Server
* MySQL
* DB/2
* Microsoft Access
 
 
==== How can I order SIARD Suite? ====
You can get SIARD Suite from https://www.bar.admin.ch/bar/en/home/archiving/tools/siard-suite.html or https://github.com/sfa-siard/SiardGui/releases 
 
==== Intellectual Property Rights ====
SIARD Suite is a development of Enter AG for the Swiss Federal Archives. The copyright owners publish SIARD Suite as open-source software under the CDDL-1.0 license (in the SIARD distribution as doc/licenses/CDDL-1.0.txt).

SIARD Suite relies on the components of other manufacturers. For detailed information on all components and their licenses see /doc/manual of the Siard Suite

. 


== User Experiences ==
<!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. -->
 
.
*This user experience is only about SiardEdit, the GUI version of SIARD Suite. The program works fast and because of the minimalistic user interface and the good documentation is the programm easy to use. 

*If SIARD has some problems to create the .siard file from a database, then the program will stop and the user gets the message "not successful". A detailed describtion of the error and the reason of this problems is desirable. A useful error message is only avaiable when the error is detected by the database, then SIARD will print out the error message of the database.

*Searching in a .siard file is not possible in a appropriated way. For that the user have to convert the .siard file in a "normal" database and then the user work and search in the database in the typical way.

*Using admin accounts to download a database will cause errors. The best way is to create a achive account which has reading rights to the part of the database which should be archived.

*For converting a MS Access database in a .siard file, SIARD will not store any information about the primary keys. In SIARD only tables can be stored. Views and something like that can't be stored, thats way it is important to make sure the database can be used and read without any extras.

== Development Activity ==
<!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. -->
 
<!-- Add the Ohloh.com ID for the tool, if known. -->