System Scope for Library Automation and Generalized Information Storage and Retrieval at Stanford University.

Fuente: ERIC Institute of Education Sciences

Saved in:

Bibliographic Details
Main Authors:	Cady, Glee, And Others
Format:	Recurso educativo Open Access
Language:	en
Published:	1970
Subjects:	Automation College Libraries Data Processing Decentralization Information Retrieval Information Science Information Storage Information Systems Library Networks Time Sharing
Online Access:	Acceder al recurso
Tags:	Add Tag No Tags, Be the first to tag this record!

_version_	1867181010129518592
author	Cady, Glee And Others
author_facet	Cady, Glee And Others Cady, Glee And Others
collection	Education Resources Information Center
contents	System Scope for Library Automation and Generalized Information Storage and Retrieval at Stanford University. Cady, Glee And Others Automation College Libraries Data Processing Decentralization Information Retrieval Information Science Information Storage Information Systems Library Networks Time Sharing The scope of a manual-automated system serving the 40 libraries and the teaching and research community of Stanford University is defined. Also defined are the library operations to be supported and the bibliographic information storage and retrieval capabilities to be provided in the system. Two major projects have been working jointly on library automation and information retrieval since 1968. One is the Bibliographic Automation of Large Library Operations on a Time-sharing System (BALLOTS) funded by the Office of Education and the other is the Stanford Physics Information Retrieval System (SPIRES), funded by the National Science Foundation. The creation of a production system for library automation (BALLOTS II) and generalized information storage and retrieval (SPIRES II) requires the continuation of a comprehensive system development process. This process has six phases: (1) preliminary analysis, (2) detailed analysis, (3) general design, (4) detailed design, (5) implementation and (6) installation. The document represents the main output of the preliminary analysis phase encompassing the definition of goals, description of the user environment, analysis of the existing system, selection of the system scope and establishment of gross technical feasibility of the selected first implementation scope. Included is a 20-page glossary of information science terminology. (MF)
format	Recurso educativo Open Access
id	eric_ED038153
institution	ERIC Institute of Education Sciences
language	en
publishDate	1970
record_format	eric
spellingShingle	System Scope for Library Automation and Generalized Information Storage and Retrieval at Stanford University. Cady, Glee And Others Automation College Libraries Data Processing Decentralization Information Retrieval Information Science Information Storage Information Systems Library Networks Time Sharing System Scope for Library Automation and Generalized Information Storage and Retrieval at Stanford University. Cady, Glee And Others Automation College Libraries Data Processing Decentralization Information Retrieval Information Science Information Storage Information Systems Library Networks Time Sharing The scope of a manual-automated system serving the 40 libraries and the teaching and research community of Stanford University is defined. Also defined are the library operations to be supported and the bibliographic information storage and retrieval capabilities to be provided in the system. Two major projects have been working jointly on library automation and information retrieval since 1968. One is the Bibliographic Automation of Large Library Operations on a Time-sharing System (BALLOTS) funded by the Office of Education and the other is the Stanford Physics Information Retrieval System (SPIRES), funded by the National Science Foundation. The creation of a production system for library automation (BALLOTS II) and generalized information storage and retrieval (SPIRES II) requires the continuation of a comprehensive system development process. This process has six phases: (1) preliminary analysis, (2) detailed analysis, (3) general design, (4) detailed design, (5) implementation and (6) installation. The document represents the main output of the preliminary analysis phase encompassing the definition of goals, description of the user environment, analysis of the existing system, selection of the system scope and establishment of gross technical feasibility of the selected first implementation scope. Included is a 20-page glossary of information science terminology. (MF)
title	System Scope for Library Automation and Generalized Information Storage and Retrieval at Stanford University.
topic	Automation College Libraries Data Processing Decentralization Information Retrieval Information Science Information Storage Information Systems Library Networks Time Sharing
url	https://eric.ed.gov/?id=ED038153

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"
ui	"standard"
VUFIND_SESSION	"06ef4b1af5625c08e11af550eb8972fb"

Session

Key	Value
__Laminas	array:2 [`"_REQUEST_ACCESS_TIME" => 1789095650.5974 "_VALID" => array:1 [ "Laminas\Session\Validator\Id" => "06ef4b1af5625c08e11af550eb8972fb" ]`]
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; ui=standard; VUFIND_SESSION=06ef4b1af5625c08e11af550eb8972fb"
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.170"
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	"61063"
REDIRECT_URL	"/Record/eric_ED038153/Details"
GATEWAY_INTERFACE	"CGI/1.1"
SERVER_PROTOCOL	"HTTP/1.1"
REQUEST_METHOD	"GET"
QUERY_STRING	""
REQUEST_URI	"/Record/eric_ED038153/Details"
SCRIPT_NAME	"/index.php"
PHP_SELF	"/index.php"
REQUEST_TIME_FLOAT	1789095650.5922
REQUEST_TIME	1789095650

Environment Variables empty

Registered Handlers

0. Whoops\Handler\PrettyPageHandler

Environment & details:

GET Data empty

POST Data empty

Files empty

Key	Value
language	"en"
ui	"standard"
VUFIND_SESSION	"06ef4b1af5625c08e11af550eb8972fb"

Session

Key	Value
__Laminas	array:2 [`"_REQUEST_ACCESS_TIME" => 1789095650.5974 "_VALID" => array:1 [ "Laminas\Session\Validator\Id" => "06ef4b1af5625c08e11af550eb8972fb" ]`]
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; ui=standard; VUFIND_SESSION=06ef4b1af5625c08e11af550eb8972fb"
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.170"
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	"61063"
REDIRECT_URL	"/Record/eric_ED038153/Details"
GATEWAY_INTERFACE	"CGI/1.1"
SERVER_PROTOCOL	"HTTP/1.1"
REQUEST_METHOD	"GET"
QUERY_STRING	""
REQUEST_URI	"/Record/eric_ED038153/Details"
SCRIPT_NAME	"/index.php"
PHP_SELF	"/index.php"
REQUEST_TIME_FLOAT	1789095650.5922
REQUEST_TIME	1789095650

Environment Variables empty

Registered Handlers

0. Whoops\Handler\PrettyPageHandler

Similar Items

Environment & details:

Environment & details: