Editing ACE (Audit Control Environment)

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
+
{{Infobox_tool
|purpose=The Auditing Control Environment is a mature set of software designed to help libraries and archives prove their holdings are intact and trustworthy.
+
|purpose=The Audit Control Environment is a mature set of software designed to help librarys and archives prove their holdings are intact and trustworthy.
|homepage=https://wiki.umiacs.umd.edu/adapt/index.php/Ace:Main
+
|image=
 +
|homepage=https://scm.umiacs.umd.edu/redmine/adapt/projects/list_files/ace
 
|license=Apache License
 
|license=Apache License
 
|platforms=Web-based and platform independent. Requires Java 1.6 or later; Tomcat 6.0 or later; MySQL 4.0 or later; and MySQL connector 5.0.7 or better
 
|platforms=Web-based and platform independent. Requires Java 1.6 or later; Tomcat 6.0 or later; MySQL 4.0 or later; and MySQL connector 5.0.7 or better
|function=Fixity
 
}}
 
{{Infobox tool details
 
|ohloh_id=ace
 
 
}}
 
}}
 +
 +
<!-- Delete the Categories that do not apply -->
 +
[[Category:Fixity]]
 +
 +
 
= Description =
 
= Description =
 
The Audit Control Environment is a mature set of software designed to help librarys and archives prove their holdings are intact and trustworthy. Recent developments of ACE include a new token store format to allow ACE tokens to be easily exported, transferred, and independently verified by third parties. To support the ACE tokens a python proof of concept has been developed to allow 3rd parties to write their own file validation routines using ACE tokens.  Developed by University of Maryland. Written in Java.
 
The Audit Control Environment is a mature set of software designed to help librarys and archives prove their holdings are intact and trustworthy. Recent developments of ACE include a new token store format to allow ACE tokens to be easily exported, transferred, and independently verified by third parties. To support the ACE tokens a python proof of concept has been developed to allow 3rd parties to write their own file validation routines using ACE tokens.  Developed by University of Maryland. Written in Java.
Line 14: Line 16:
 
= User Experiences =
 
= User Experiences =
  
* I deployed ACE-AM a few years ago, in it's servlet form, and it worked pretty well. The only problem was that for very large collections (millions of individual files) it would start to fall over due to running out of RAM. There is no technical need to keep the entire collection's checksum data in memory (as the system has a database available), so this could easily have been fixed by now. If this is a potential concern, I recommend monitoring memory usage as part of a large-scale test during evaluation. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 11:02, 11 September 2014 (UTC)
 
* [https://groups.google.com/forum/#!topic/digital-curation/ZT21Ac1aLQQ Discussion of fixity tools, including ACE on the Digital Curation google groups]
 
  
 
= Development Activity =
 
= Development Activity =

Please note that all contributions to COPTR are considered to be released under the Attribution-ShareAlike 3.0 Unported (see COPTR:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)