The Year of Living Dangerously: Implementing CARL New Circulation at CU, Boulder.

Fuente: ERIC Institute of Education Sciences

Saved in:

Bibliographic Details
Main Author:	Seaman, Scott
Format:	Recurso educativo Open Access
Language:	en
Published:	1992
Subjects:	College Libraries Computer Software Debugging (Computers) Guidelines Higher Education Library Automation Library Circulation
Online Access:	Acceder al recurso
Tags:	Add Tag No Tags, Be the first to tag this record!

_version_	1867181653888073728
author	Seaman, Scott
author_facet	Seaman, Scott Seaman, Scott
collection	Education Resources Information Center
contents	The Year of Living Dangerously: Implementing CARL New Circulation at CU, Boulder. Seaman, Scott College Libraries Computer Software Debugging (Computers) Guidelines Higher Education Library Automation Library Circulation This paper outlines the procedures used to implement and test the CARL version C100 circulation system at the University of Colorado's Boulder Campus. Intended to serve as a guide to other libraries implementing new circulation software, the paper describes a broad approach to testing such software, describes procedures that speed and organize the process, and suggests staffing levels and equipment to have available. The focus is on describing methods to test the accuracy of data transfer, determine the functionality of the features, and to confirm that the local parameters interact properly with all circulation functions. The following steps are covered: (1) test preparations, such as involving technical staff and organizing work area and materials; (2) documenting the transfer of data from the old system to CARL by preparing forms for checking the accuracy of the transfer and providing a means, such as fax or email, to document discussions with CARL about problems identified during the test; (3) implementing test procedures to check the accuracy of the transfer of data on materials, patron records, and transactions; (4) testing to make sure functions and features, such as In-transit, Added Borrower, and Renew-All, perform as they are supposed to; (5) stress testing the system by such means as adding 500 books to a patron's account and renewing them all; (6) alert CARL that the system is ready to go live after identified problems are cleared up; and (7) continuing to retest critical elements such as parameters and functions after the system goes live. The prospective user of these guidelines is warned that although testing is time and labor intensive, it is essential; even though others have implemented the system, there may still be bugs that have not been resolved. (KRN)
format	Recurso educativo Open Access
id	eric_ED352039
institution	ERIC Institute of Education Sciences
language	en
publishDate	1992
record_format	eric
spellingShingle	The Year of Living Dangerously: Implementing CARL New Circulation at CU, Boulder. Seaman, Scott College Libraries Computer Software Debugging (Computers) Guidelines Higher Education Library Automation Library Circulation The Year of Living Dangerously: Implementing CARL New Circulation at CU, Boulder. Seaman, Scott College Libraries Computer Software Debugging (Computers) Guidelines Higher Education Library Automation Library Circulation This paper outlines the procedures used to implement and test the CARL version C100 circulation system at the University of Colorado's Boulder Campus. Intended to serve as a guide to other libraries implementing new circulation software, the paper describes a broad approach to testing such software, describes procedures that speed and organize the process, and suggests staffing levels and equipment to have available. The focus is on describing methods to test the accuracy of data transfer, determine the functionality of the features, and to confirm that the local parameters interact properly with all circulation functions. The following steps are covered: (1) test preparations, such as involving technical staff and organizing work area and materials; (2) documenting the transfer of data from the old system to CARL by preparing forms for checking the accuracy of the transfer and providing a means, such as fax or email, to document discussions with CARL about problems identified during the test; (3) implementing test procedures to check the accuracy of the transfer of data on materials, patron records, and transactions; (4) testing to make sure functions and features, such as In-transit, Added Borrower, and Renew-All, perform as they are supposed to; (5) stress testing the system by such means as adding 500 books to a patron's account and renewing them all; (6) alert CARL that the system is ready to go live after identified problems are cleared up; and (7) continuing to retest critical elements such as parameters and functions after the system goes live. The prospective user of these guidelines is warned that although testing is time and labor intensive, it is essential; even though others have implemented the system, there may still be bugs that have not been resolved. (KRN)
title	The Year of Living Dangerously: Implementing CARL New Circulation at CU, Boulder.
topic	College Libraries Computer Software Debugging (Computers) Guidelines Higher Education Library Automation Library Circulation
url	https://eric.ed.gov/?id=ED352039

if (filemtime($filename) + $maxlifetime < time()) { unlink($filename); $count++; } } return $count; } /** * A function that is called internally when session data is to be saved. * * @param string $sessId The current session ID * @param string $data The session data to write * * @return bool */ protected function saveSession($sessId, $data): bool { $sessFile = $this->path . '/sess_' . $sessId; if ($handle = fopen($sessFile, 'w')) { $return = false; // Lock the file for exclusive access to avoid issues with multiple // processes writing session simultaneously: if (flock($handle, LOCK_EX)) { $return = fwrite($handle, $data); // Make sure that there's no trailing data by truncating the file to // the correct length: ftruncate($handle, strlen($data)); fflush($handle); flock($handle, LOCK_UN); } fclose($handle); if ($return !== false) { return true; } } // If we got this far, something went wrong with the file output... // It is tempting to throw an exception here, but this code is called // outside of the context of exception handling, so all we can do is // echo a message.

// Anecdotal testing Today and Yesterday seems to indicate destroy() // is called by the garbage collector and everything is good. // Something to keep in mind though. return 0; } /** * Write function that is called when session data is to be saved. * * @param string $sessId The current session ID * @param string $data The session data to write * * @return bool */ public function write($sessId, $data): bool { if ($this->writesDisabled) { return true; } return $this->saveSession($sessId, $data); } /** * A function that is called internally when session data is to be saved. * * @param string $sessId The current session ID * @param string $data The session data to write * * @return bool */ abstract protected function saveSession($sessId, $data): bool; }

* * @return void */ public function writeClose() { // The assumption is that we're using PHP's ext/session. // session_write_close() will actually overwrite $_SESSION with an // empty array on completion -- which leads to a mismatch between what // is in the storage object and $_SESSION. To get around this, we // temporarily reset $_SESSION to an array, and then re-link it to // the storage object. // // Additionally, while you _can_ write to $_SESSION following a // session_write_close() operation, no changes made to it will be // flushed to the session handler. As such, we now mark the storage // object isImmutable. $storage = $this->getStorage(); if (! $storage->isImmutable()) { $_SESSION = $storage->toArray(true); session_write_close(); $storage->fromArray($_SESSION); $storage->markImmutable(); } } /** * Attempt to set the session name * * If the session has already been started, or if the name provided fails * validation, an exception will be raised. * * @param string $name * @return SessionManager * @throws Exception\InvalidArgumentException */ public function setName($name) { if ($this->sessionExists()) { throw new Exception\InvalidArgumentException( 'Cannot set session name after a session has already started'

Environment & details:

GET Data empty

POST Data empty

Files empty

Key	Value
language	"en"
VUFIND_SESSION	"fa707aa189e7f4cc98e546438c38fd9b"
ui	"standard"

Session

Key	Value
__Laminas	array:2 [`"_REQUEST_ACCESS_TIME" => 1789299018.3168 "_VALID" => array:1 [ "Laminas\Session\Validator\Id" => "fa707aa189e7f4cc98e546438c38fd9b" ]`]
SessionState	Laminas\Stdlib\ArrayObject {#938}
FlashMessenger	Laminas\Stdlib\ArrayObject {#1455}
SessionHelper	Laminas\Stdlib\ArrayObject {#1785}

Server/Request Data

Key	Value
REDIRECT_VUFIND_LOCAL_DIR	"/usr/local/vufind/local"
REDIRECT_HTTPS	"on"
REDIRECT_SSL_TLS_SNI	"info.umar.mx"
REDIRECT_STATUS	"200"
VUFIND_LOCAL_DIR	"/usr/local/vufind/local"
HTTPS	"on"
SSL_TLS_SNI	"info.umar.mx"
HTTP_ACCEPT	"/"
HTTP_USER_AGENT	"Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)"
HTTP_COOKIE	"language=en; VUFIND_SESSION=fa707aa189e7f4cc98e546438c38fd9b; ui=standard"
HTTP_ACCEPT_ENCODING	"gzip, br, zstd, deflate"
HTTP_HOST	"info.umar.mx"
PATH	"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/snap/bin"
SERVER_SIGNATURE	"<address>Apache/2.4.66 (Ubuntu) Server at info.umar.mx Port 443</address>\n"
SERVER_SOFTWARE	"Apache/2.4.66 (Ubuntu)"
SERVER_NAME	"info.umar.mx"
SERVER_ADDR	"200.23.222.19"
SERVER_PORT	"443"
REMOTE_ADDR	"216.73.216.61"
DOCUMENT_ROOT	"/usr/local/vufind/public"
REQUEST_SCHEME	"https"
CONTEXT_PREFIX	""
CONTEXT_DOCUMENT_ROOT	"/usr/local/vufind/public"
SERVER_ADMIN	"admin@localhost"
SCRIPT_FILENAME	"/usr/local/vufind/public/index.php"
REMOTE_PORT	"39685"
REDIRECT_URL	"/Record/eric_ED352039/Details"
GATEWAY_INTERFACE	"CGI/1.1"
SERVER_PROTOCOL	"HTTP/1.1"
REQUEST_METHOD	"GET"
QUERY_STRING	""
REQUEST_URI	"/Record/eric_ED352039/Details"
SCRIPT_NAME	"/index.php"
PHP_SELF	"/index.php"
REQUEST_TIME_FLOAT	1789299018.3123
REQUEST_TIME	1789299018

Environment Variables empty

Registered Handlers

0. Whoops\Handler\PrettyPageHandler

Environment & details:

GET Data empty

POST Data empty

Files empty

Key	Value
language	"en"
VUFIND_SESSION	"fa707aa189e7f4cc98e546438c38fd9b"
ui	"standard"

Session

Key	Value
__Laminas	array:2 [`"_REQUEST_ACCESS_TIME" => 1789299018.3168 "_VALID" => array:1 [ "Laminas\Session\Validator\Id" => "fa707aa189e7f4cc98e546438c38fd9b" ]`]
SessionState	Laminas\Stdlib\ArrayObject {#938}
FlashMessenger	Laminas\Stdlib\ArrayObject {#1455}
SessionHelper	Laminas\Stdlib\ArrayObject {#1785}

Server/Request Data

Key	Value
REDIRECT_VUFIND_LOCAL_DIR	"/usr/local/vufind/local"
REDIRECT_HTTPS	"on"
REDIRECT_SSL_TLS_SNI	"info.umar.mx"
REDIRECT_STATUS	"200"
VUFIND_LOCAL_DIR	"/usr/local/vufind/local"
HTTPS	"on"
SSL_TLS_SNI	"info.umar.mx"
HTTP_ACCEPT	"/"
HTTP_USER_AGENT	"Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)"
HTTP_COOKIE	"language=en; VUFIND_SESSION=fa707aa189e7f4cc98e546438c38fd9b; ui=standard"
HTTP_ACCEPT_ENCODING	"gzip, br, zstd, deflate"
HTTP_HOST	"info.umar.mx"
PATH	"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/snap/bin"
SERVER_SIGNATURE	"<address>Apache/2.4.66 (Ubuntu) Server at info.umar.mx Port 443</address>\n"
SERVER_SOFTWARE	"Apache/2.4.66 (Ubuntu)"
SERVER_NAME	"info.umar.mx"
SERVER_ADDR	"200.23.222.19"
SERVER_PORT	"443"
REMOTE_ADDR	"216.73.216.61"
DOCUMENT_ROOT	"/usr/local/vufind/public"
REQUEST_SCHEME	"https"
CONTEXT_PREFIX	""
CONTEXT_DOCUMENT_ROOT	"/usr/local/vufind/public"
SERVER_ADMIN	"admin@localhost"
SCRIPT_FILENAME	"/usr/local/vufind/public/index.php"
REMOTE_PORT	"39685"
REDIRECT_URL	"/Record/eric_ED352039/Details"
GATEWAY_INTERFACE	"CGI/1.1"
SERVER_PROTOCOL	"HTTP/1.1"
REQUEST_METHOD	"GET"
QUERY_STRING	""
REQUEST_URI	"/Record/eric_ED352039/Details"
SCRIPT_NAME	"/index.php"
PHP_SELF	"/index.php"
REQUEST_TIME_FLOAT	1789299018.3123
REQUEST_TIME	1789299018

Environment Variables empty

Registered Handlers

0. Whoops\Handler\PrettyPageHandler

Similar Items

Environment & details:

Environment & details: