Editing Duke Data Accessioner
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 |
| − | |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. | + | |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. |
| − | |homepage= | + | |image= |
| − | + | |homepage=http://library.duke.edu/rubenstein/uarchives/about/data-accessioner | |
| − | |license= | + | |license= |
| − | + | |platforms= | |
| − | |platforms= | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
}} | }} | ||
| + | |||
| + | <!-- Delete the Categories that do not apply --> | ||
| + | [[Category:Preservation System]] | ||
| + | [[Category:Metadata Processing]] | ||
| + | |||
= Description = | = 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. | + | 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. |
====Provider==== | ====Provider==== | ||
| − | + | Duke University Libraries | |
====Licensing and cost==== | ====Licensing and cost==== | ||
| − | The software is free and | + | The software is free and available for non-commercial, educational and research purposes under an open-source, Duke-written license. |
====Platform and interoperability==== | ====Platform and interoperability==== | ||
| − | The software is written in Java, which renders it platform independent. | + | 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 [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. | |
| − | |||
====Functional notes==== | ====Functional notes==== | ||
| − | The Data Accessioner is comprised of | + | 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 [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. | ||
| + | ====Documentation and user support==== | ||
| + | The website offers a short online written specifically for Duke employees; while some of the instructions are tailored for that institution, much of the information is universally helpful. | ||
| + | The website also links to an online contact form. | ||
====Usability==== | ====Usability==== | ||
The Data Accessioner uses a simple and straightforward Graphical User Interface. | 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. | 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 | + | 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==== | ====Standards compliance==== | ||
| − | The software includes a PREMIS metadata manager. | + | The software includes a PREMIS metadata manager. Incorporation of other metadata standards requires a custom-built module. |
====Influence and take-up==== | ====Influence and take-up==== | ||
| − | No statistics are available | + | The Duke University Library uses the Data Accessioner in its accessioning workflow. No statistics are available on outside use. |
| − | + | ||
| − | |||
= User Experiences = | = User Experiences = | ||
| − | |||
| − | |||
= Development Activity = | = Development Activity = | ||
| − | + | ||
| + | {{Infobox_tool_details | ||
| + | |ohloh_id=Duke Data Accessioner | ||
| + | }} | ||