Difference between revisions of "Duke Data Accessioner"

From COPTR
Jump to: navigation, search
Line 16: Line 16:
 
Data Accessioner website and POWRR.
 
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 licensed under the GNU Lesser General Public License (v 2.1).
 
====Platform and interoperability====
 
====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.
+
The software is written in Java, which renders it platform independent. (Requires Java 6.)
Existing plugins for [http://www.dcc.ac.uk/resource/external/jstorharvard-object-validation-environment-jhove JHOVE] and [http://www.dcc.ac.uk/resource/external/droid DROID] are available on the Accessioner webpage.
+
 
 +
For versions 0.3.1 and earlier 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.
 
====Functional notes====
 
====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.
+
The Data Accessioner is comprised of three main components; a graphical interface, a migrator, and a metadata manager. 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. As of version 1.0 the migrator also runs each file through FITS and sends the results to the metadata manager. The metadata manager, by default, transforms the FITS output to PREMIS (v 2.2) object metadata although this can be changed by updating an XSLT. Previous versions used Jhove, Droid, and custom metadata manager plugins.
 
While the software’s website does not give any information on volume or file format limitations, a [http://e-records.chrisprom.com/?p=1809 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.
 
While the software’s website does not give any information on volume or file format limitations, a [http://e-records.chrisprom.com/?p=1809 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====
 
====Usability====
Line 27: Line 28:
 
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.
 
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====
 
====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.
+
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 customization, however, entails either editing the FITS to PREMIS XSLT or modifying the application's source-code, which requires solid knowledge of application design.
 
====Standards compliance====
 
====Standards compliance====
The software includes a PREMIS metadata manager. Incorporation of other metadata standards requires a custom-built module.
+
The software includes a PREMIS metadata manager.
 
====Influence and take-up====
 
====Influence and take-up====
The Duke University Library uses the Data Accessioner in its accessioning workflow. No statistics are available on outside use.
+
No statistics are available although it has been featured in various conference presentations and workshops.
 
====Other====
 
====Other====
 
The old home page can be found here:http://library.duke.edu/rubenstein/uarchives/about/data-accessioner
 
The old home page can be found here:http://library.duke.edu/rubenstein/uarchives/about/data-accessioner
Line 40: Line 41:
  
 
{{Infobox_tool_details
 
{{Infobox_tool_details
|ohloh_id=Duke Data Accessioner
+
|ohloh_id=Data Accessioner
 
}}
 
}}
  
 
<rss max=5>https://github.com/seth-shaw/DataAccessioner/commits/master.atom</rss>
 
<rss max=5>https://github.com/seth-shaw/DataAccessioner/commits/master.atom</rss>

Revision as of 17:14, 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

Contents

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 licensed under the GNU Lesser General Public License (v 2.1).

Platform and interoperability

The software is written in Java, which renders it platform independent. (Requires Java 6.)

For versions 0.3.1 and earlier 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.

Functional notes

The Data Accessioner is comprised of three main components; a graphical interface, a migrator, and a metadata manager. 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. As of version 1.0 the migrator also runs each file through FITS and sends the results to the metadata manager. The metadata manager, by default, transforms the FITS output to PREMIS (v 2.2) object metadata although this can be changed by updating an XSLT. Previous versions used Jhove, Droid, and custom metadata manager plugins. 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 customization, however, entails either editing the FITS to PREMIS XSLT or modifying the application's source-code, which requires solid knowledge of application design.

Standards compliance

The software includes a PREMIS metadata manager.

Influence and take-up

No statistics are available although it has been featured in various conference presentations and workshops.

Other

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

User Experiences

Development Activity



Failed to load RSS feed from https://github.com/seth-shaw/DataAccessioner/commits/master.atom: Error fetching URL: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version

Contributors

Stacey (12.9%), Seth.e.shaw (10.7%), Prwheatley (18.4%), Mjf33 (13.4%), COPTR Bot (44.7%)