A Dynamic Approach to Make CDS/ISIS Databases Interoperable over the Internet Using the OAI Protocol

Fuente: ERIC Institute of Education Sciences

Saved in:

Bibliographic Details
Main Authors:	Jayakanth, F., Maly, K., Zubair, M., Aswath, L.
Format:	Recurso educativo Open Access
Language:	en
Published:	2006
Subjects:	Electronic Libraries Metadata Databases Internet
Online Access:	Acceder al recurso
Tags:	Add Tag No Tags, Be the first to tag this record!

_version_	1867181908123713536
author	Jayakanth, F. Maly, K. Zubair, M. Aswath, L.
author_facet	Jayakanth, F. Maly, K. Zubair, M. Aswath, L. Jayakanth, F. Maly, K. Zubair, M. Aswath, L.
collection	Education Resources Information Center
contents	A Dynamic Approach to Make CDS/ISIS Databases Interoperable over the Internet Using the OAI Protocol Jayakanth, F. Maly, K. Zubair, M. Aswath, L. Electronic Libraries Metadata Databases Internet Purpose: A dynamic approach to making legacy databases, like CDS/ISIS, interoperable with OAI-compliant digital libraries (DLs). Design/methodology/approach: There are many bibliographic databases that are being maintained using legacy database systems. CDS/ISIS is one such legacy database system. It was designed and developed specifically for handling textual data. Over the years, many databases have been developed using this package. There is, however, no mechanism supported by the package for seamless interoperability of databases. The open archives initiative (OAI) addresses the issue of interoperability by using a framework to facilitate the discovery of content stored in distributed archives or bibliographic databases through the use of the OAI Protocol for Metadata Harvesting (OAI-PMH). The protocol is becoming a de facto standard for interoperability of DLs. Many of the legacy database systems that are in use today, to the best of our knowledge, for various reasons, are not OAI-compliant. This makes it difficult for the legacy databases to share their metadata automatically. There are two possible approaches to make legacy databases OAI-compliant--static and dynamic. In this paper, we discuss the dynamic approach to make CDS/ISIS databases OAI-compliant. Findings: The dynamic approach is a simple way to make legacy databases OAI-compliant so that they become interoperable with other OAI-compliant DLs. Research limitations/implication: Developing a general-purpose tool to make legacy databases OAI-compliant may be difficult as the driver software needed for database connectivity may not be easily available. Also, the structure of the databases are likely be so varied that identifying the fields that make up the databases programmatically will be very challenging. Originality/value: Provides a dynamic approach to making legacy databases interoperable with OAI-compliant libraries.
format	Recurso educativo Open Access
id	eric_EJ901967
institution	ERIC Institute of Education Sciences
language	en
publishDate	2006
record_format	eric
spellingShingle	A Dynamic Approach to Make CDS/ISIS Databases Interoperable over the Internet Using the OAI Protocol Jayakanth, F. Maly, K. Zubair, M. Aswath, L. Electronic Libraries Metadata Databases Internet A Dynamic Approach to Make CDS/ISIS Databases Interoperable over the Internet Using the OAI Protocol Jayakanth, F. Maly, K. Zubair, M. Aswath, L. Electronic Libraries Metadata Databases Internet Purpose: A dynamic approach to making legacy databases, like CDS/ISIS, interoperable with OAI-compliant digital libraries (DLs). Design/methodology/approach: There are many bibliographic databases that are being maintained using legacy database systems. CDS/ISIS is one such legacy database system. It was designed and developed specifically for handling textual data. Over the years, many databases have been developed using this package. There is, however, no mechanism supported by the package for seamless interoperability of databases. The open archives initiative (OAI) addresses the issue of interoperability by using a framework to facilitate the discovery of content stored in distributed archives or bibliographic databases through the use of the OAI Protocol for Metadata Harvesting (OAI-PMH). The protocol is becoming a de facto standard for interoperability of DLs. Many of the legacy database systems that are in use today, to the best of our knowledge, for various reasons, are not OAI-compliant. This makes it difficult for the legacy databases to share their metadata automatically. There are two possible approaches to make legacy databases OAI-compliant--static and dynamic. In this paper, we discuss the dynamic approach to make CDS/ISIS databases OAI-compliant. Findings: The dynamic approach is a simple way to make legacy databases OAI-compliant so that they become interoperable with other OAI-compliant DLs. Research limitations/implication: Developing a general-purpose tool to make legacy databases OAI-compliant may be difficult as the driver software needed for database connectivity may not be easily available. Also, the structure of the databases are likely be so varied that identifying the fields that make up the databases programmatically will be very challenging. Originality/value: Provides a dynamic approach to making legacy databases interoperable with OAI-compliant libraries.
title	A Dynamic Approach to Make CDS/ISIS Databases Interoperable over the Internet Using the OAI Protocol
topic	Electronic Libraries Metadata Databases Internet
url	https://eric.ed.gov/?id=EJ901967

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
VUFIND_SESSION	"6bbb299c140c3e15a14c250451f2203f"
ui	"standard"
language	"en"

Session

Key	Value
__Laminas	array:2 [`"_REQUEST_ACCESS_TIME" => 1789197239.4947 "_VALID" => array:1 [ "Laminas\Session\Validator\Id" => "6bbb299c140c3e15a14c250451f2203f" ]`]
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	"VUFIND_SESSION=6bbb299c140c3e15a14c250451f2203f; ui=standard; language=en"
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	"22101"
REDIRECT_URL	"/Record/eric_EJ901967/Details"
GATEWAY_INTERFACE	"CGI/1.1"
SERVER_PROTOCOL	"HTTP/1.1"
REQUEST_METHOD	"GET"
QUERY_STRING	""
REQUEST_URI	"/Record/eric_EJ901967/Details"
SCRIPT_NAME	"/index.php"
PHP_SELF	"/index.php"
REQUEST_TIME_FLOAT	1789197239.4871
REQUEST_TIME	1789197239

Environment Variables empty

Registered Handlers

0. Whoops\Handler\PrettyPageHandler

Environment & details:

GET Data empty

POST Data empty

Files empty

Key	Value
VUFIND_SESSION	"6bbb299c140c3e15a14c250451f2203f"
ui	"standard"
language	"en"

Session

Key	Value
__Laminas	array:2 [`"_REQUEST_ACCESS_TIME" => 1789197239.4947 "_VALID" => array:1 [ "Laminas\Session\Validator\Id" => "6bbb299c140c3e15a14c250451f2203f" ]`]
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	"VUFIND_SESSION=6bbb299c140c3e15a14c250451f2203f; ui=standard; language=en"
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	"22101"
REDIRECT_URL	"/Record/eric_EJ901967/Details"
GATEWAY_INTERFACE	"CGI/1.1"
SERVER_PROTOCOL	"HTTP/1.1"
REQUEST_METHOD	"GET"
QUERY_STRING	""
REQUEST_URI	"/Record/eric_EJ901967/Details"
SCRIPT_NAME	"/index.php"
PHP_SELF	"/index.php"
REQUEST_TIME_FLOAT	1789197239.4871
REQUEST_TIME	1789197239

Environment Variables empty

Registered Handlers

0. Whoops\Handler\PrettyPageHandler

Similar Items

Environment & details:

Environment & details: