Editing Tufts Submission-Agreement Builder Tool

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=SABT is a web-based tool that guides records creators and records managers through the process of creating submission agreements, both for single transfers and for standing submissions.
 
|purpose=SABT is a web-based tool that guides records creators and records managers through the process of creating submission agreements, both for single transfers and for standing submissions.
 +
|image=
 
|homepage=http://sites.tufts.edu/dca/about-us/research-initiatives/taper-tufts-accessioning-program-for-electronic-records/deliverables/
 
|homepage=http://sites.tufts.edu/dca/about-us/research-initiatives/taper-tufts-accessioning-program-for-electronic-records/deliverables/
|function=Planning, Data capture and Deposit
+
|license=
}}
+
|platforms=
{{Infobox tool details
 
|ohloh_id=Tufts Submission-Agreement Builder Tool
 
 
}}
 
}}
 +
 +
<!-- Delete the Categories that do not apply -->
 +
[[Category:Planning]]
 +
 +
 
= Description =
 
= Description =
 
The [http://sites.tufts.edu/dca/about-us/research-initiatives/taper-tufts-accessioning-program-for-electronic-records/deliverables/ Tufts Submission-Agreement Builder Tool] (SABT) is a web-based tool that guides records creators and records managers through the process of creating submission agreements, both for single transfers and for standing submissions. Following an accompanying XML schema, the tool prompts the user to input data that has been determined to be necessary for a complete agreement, ultimately producing a finished document.
 
The [http://sites.tufts.edu/dca/about-us/research-initiatives/taper-tufts-accessioning-program-for-electronic-records/deliverables/ Tufts Submission-Agreement Builder Tool] (SABT) is a web-based tool that guides records creators and records managers through the process of creating submission agreements, both for single transfers and for standing submissions. Following an accompanying XML schema, the tool prompts the user to input data that has been determined to be necessary for a complete agreement, ultimately producing a finished document.
 
The SABT was designed for use with electronic records, but can presumably be adapted.
 
The SABT was designed for use with electronic records, but can presumably be adapted.
 
 
====Provider====
 
====Provider====
 
The Digital Collections and Archives (DCA) at Tufts University, as part of the Tufts Accessioning Program for Electronic Records (TAPER) project
 
The Digital Collections and Archives (DCA) at Tufts University, as part of the Tufts Accessioning Program for Electronic Records (TAPER) project
 
 
====Licensing and cost====
 
====Licensing and cost====
 
[http://www.gnu.org/licenses/agpl.html GNU Affero General Public License] &ndash; free.
 
[http://www.gnu.org/licenses/agpl.html GNU Affero General Public License] &ndash; free.
+
====Development activity====
 +
The SABT code was released July 2011.
 +
The TAPER Project has ended; however, since the SABT is at the centre of the DCA accessioning workflow, it should presumably remain supported.
 
====Platform and interoperability====
 
====Platform and interoperability====
 
The SABT requires a modern Unix-based OS and has been shown to work on Solaris, Linux, and Mac OS X. &nbsp;It should be possible to run it on Windows, but this is untested.
 
The SABT requires a modern Unix-based OS and has been shown to work on Solaris, Linux, and Mac OS X. &nbsp;It should be possible to run it on Windows, but this is untested.
 
SABT is designed for the Apache web server and FastCGI. It also requires Perl, version 5.8.8 or later, to support the Catalyst web framework, MySQL, version 5 or later, the GNU C compiler and the Make utility.
 
SABT is designed for the Apache web server and FastCGI. It also requires Perl, version 5.8.8 or later, to support the Catalyst web framework, MySQL, version 5 or later, the GNU C compiler and the Make utility.
 
 
====Functional notes====
 
====Functional notes====
 
The tool creates agreements for both standing submissions, which cover serial ingest projects, and regular submissions covering a single ingest. The tool uses three XML schemas to do so: one for regular submissions, one for standing submissions, and one for common elements between the two.
 
The tool creates agreements for both standing submissions, which cover serial ingest projects, and regular submissions covering a single ingest. The tool uses three XML schemas to do so: one for regular submissions, one for standing submissions, and one for common elements between the two.
 
The access platform for the SABT is designed to be integrated into an institution&#39;s own website; it does not function as a stand-alone application.
 
The access platform for the SABT is designed to be integrated into an institution&#39;s own website; it does not function as a stand-alone application.
 
 
====Documentation and user support====
 
====Documentation and user support====
 
The DCA created three pairs of instructional videos and guides that walk through the steps of using the SABT. These guides are in the context of the Tufts implementation of the software, but are illustrative of its general functionality.
 
The DCA created three pairs of instructional videos and guides that walk through the steps of using the SABT. These guides are in the context of the Tufts implementation of the software, but are illustrative of its general functionality.
The software&rsquo;s [https://github.com/TuftsUniversity/sabt github site] includes extensive user documentation for both the SABT and the XML schema. The access platform&rsquo;s developer documentation is attached to the Perl modules that define its backend.
+
The software&rsquo;s [https://github.com/dcatufts/sabt github site] includes extensive user documentation for both the SABT and the XML schema. The access platform&rsquo;s developer documentation is attached to the Perl modules that define its backend.
 
 
====Usability====
 
====Usability====
 
Demonstrations of the web interface seem simple and intuitive. However, the fact that the web application is designed to be integrated into an existing repository website render setup and configuration quite complex.
 
Demonstrations of the web interface seem simple and intuitive. However, the fact that the web application is designed to be integrated into an existing repository website render setup and configuration quite complex.
 
 
====Expertise required====
 
====Expertise required====
 
Installation and configuration require solid knowledge of web application design and technologies, and system administration. Records managers should review the XML schemas to determine whether the elements match the requirements for their repository.
 
Installation and configuration require solid knowledge of web application design and technologies, and system administration. Records managers should review the XML schemas to determine whether the elements match the requirements for their repository.
 
 
====Standards compliance====
 
====Standards compliance====
 
The DCA created its own XML schemas for submission agreement elements. No information is available regarding any standards underlying the schema.
 
The DCA created its own XML schemas for submission agreement elements. No information is available regarding any standards underlying the schema.
 
 
====Influence and take-up====
 
====Influence and take-up====
 
The Tufts DCA uses the SABT and the accompanying XML schemas. Information regarding wider use is unavailable.
 
The Tufts DCA uses the SABT and the accompanying XML schemas. Information regarding wider use is unavailable.
Line 44: Line 42:
  
  
= Development Activity =  
+
= Development Activity =
<!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. -->
+
 
The SABT code was released July 2011.
+
{{Infobox_tool_details
The TAPER Project has ended; however, since the SABT is at the centre of the DCA accessioning workflow, it should presumably remain supported.
+
|ohloh_id=Tufts Submission-Agreement Builder Tool
+
}}
All development activity is visible on GitHub: http://github.com/TuftsUniversity/sabt/commits
 
 
 
=== Release Feed ===
 
Below the last 3 release feeds:
 
<rss max=3>https://github.com/TuftsUniversity/sabt/releases.atom</rss>
 
 
 
 
=== Activity Feed ===
 
Below the last 5 commits:
 
<rss max=5>https://github.com/TuftsUniversity/sabt/commits/master.atom</rss>
 

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)