Difference between revisions of "Duke Data Accessioner"

From COPTR
Jump to navigation Jump to search
Line 1: Line 1:
 
{{Infobox_tool
 
{{Infobox_tool
|purpose=Duke Data Accessioner provides a graphical user interface to aid in migrating data from physical media to a dedicated file server, documenting the process and using MD5 checksums to identify any errors introduced in transfer.
+
|purpose=Data Accessioner provides a graphical user interface to aid in migrating data from physical media to a dedicated file server, documenting the process and using MD5 checksums to identify any errors introduced in transfer.
 
|image=
 
|image=
 
|homepage=http://dataaccessioner.org/
 
|homepage=http://dataaccessioner.org/
Line 12: Line 12:
  
 
= Description =
 
= Description =
The Duke Data Accessioner provides a graphical user interface to aid in migrating data from physical media to a dedicated file server, documenting the process and using MD5 checksums to identify any errors introduced in transfer. The software also offers a way to integrate metadata tools into the migration workflow. The tool is primarily designed for use by technical services librarians in small institutions with little or no IT support.
+
The Data Accessioner provides a graphical user interface to aid in migrating data from physical media to a dedicated file server, documenting the process and using MD5 checksums to identify any errors introduced in transfer. The software also offers a way to integrate metadata tools into the migration workflow. The tool is primarily designed for use by technical services librarians in small institutions with little or no IT support.
 
====Provider====
 
====Provider====
Duke University Libraries
+
Data Accessioner website and POWRR.
 
====Licensing and cost====
 
====Licensing and cost====
 
The software is free and available for non-commercial, educational and research purposes under an open-source, Duke-written license.
 
The software is free and available for non-commercial, educational and research purposes under an open-source, Duke-written license.

Revision as of 14:04, 19 August 2014

Data Accessioner provides a graphical user interface to aid in migrating data from physical media to a dedicated file server, documenting the process and using MD5 checksums to identify any errors introduced in transfer.
Homepage:http://dataaccessioner.org/
License:Free
Platforms:Java

Description

The Data Accessioner provides a graphical user interface to aid in migrating data from physical media to a dedicated file server, documenting the process and using MD5 checksums to identify any errors introduced in transfer. The software also offers a way to integrate metadata tools into the migration workflow. The tool is primarily designed for use by technical services librarians in small institutions with little or no IT support.

Provider

Data Accessioner website and POWRR.

Licensing and cost

The software is free and available for non-commercial, educational and research purposes under an open-source, Duke-written license.

Platform and interoperability

The software is written in Java, which renders it platform independent. Plugins are used via the Java Plugin Framework (JPF); a noted issue is that the JPF plugins do not work when running in a Mac OSX environment. Existing plugins for JHOVE and DROID are available on the Accessioner webpage.

Functional notes

The Data Accessioner is comprised of four main components; a graphical interface, a migrator, a metadata manager, and optional adapters. The migrator recursively navigates a file tree, copying it to a given destination with the option of skipping specified files and directories. It also creates a MD5 checksum for both the original file and the new copy, comparing the two to detect and notify the user of any errors. The project has thus far created two adapters; the JHOVE and DROID plugins allow users to insert these outside tools directly into their accessioning workflow. Using a custom metadata manager, the Data Accessioner can also be used as an ingest interface to repository systems such as Fedora. While the software’s website does not give any information on volume or file format limitations, a University of Illinois case study encountered both. Overall, the user was extremely happy with the software; however, the project was unable to migrate information in CDA format and encountered a JVM error when attempting to migrate a large backup disk.

Usability

The Data Accessioner uses a simple and straightforward Graphical User Interface. If the user wishes to exclusively run the migratory element of the software it must be done through command-line; however, this should not be necessary in the vast majority of uses.

Expertise required

The project’s goal was to create software for technical services librarians, able “to be easily adopted by smaller institutions with little or no IT staff.” Metadata customisation, however, entails the construction of a separate plugin, which requires solid knowledge of application design.

Standards compliance

The software includes a PREMIS metadata manager. Incorporation of other metadata standards requires a custom-built module.

Influence and take-up

The Duke University Library uses the Data Accessioner in its accessioning workflow. No statistics are available on outside use.

Other

The old home page can be found here:http://library.duke.edu/rubenstein/uarchives/about/data-accessioner

User Experiences

Development Activity



2017-04-17 19:52:14
[tag:github.com,2008:Grit::Commit/b298e83f64efb6441808d0d14b4c2a2a34a6d0d4 Line wrap DC metadata values, About the Source, and Additional Notes …]
by prater@wisc.edu
2017-02-20 22:42:58
[tag:github.com,2008:Grit::Commit/9ccf4d371d61ab8c90ff40c2a503a9438a02bc0f Adjust file permissions for jar]
by prater@wisc.edu
2017-02-17 16:19:06
[tag:github.com,2008:Grit::Commit/59096069d8485bc37b59087a9197f35838c0c468 Merge branch 'master' of github.com:seth-shaw/DataAccessioner]
by prater@wisc.edu
2017-02-17 16:18:10
[tag:github.com,2008:Grit::Commit/99c9ce5feab90818ddf32506472cbf99c1cf4c9e Fix reference to The Archives of the Episcopal Church]
by prater@wisc.edu
2017-02-03 21:45:11
[tag:github.com,2008:Grit::Commit/090b4d1a7c139a759ea52dd024085b8ef8d5616a Merge pull request #16 from seth-shaw/1.1]
by prater@wisc.edu