Evaluation of Interoperability Protocols in Repositories of Electronic Theses and Dissertations

Fuente: ERIC Institute of Education Sciences

Saved in:

Bibliographic Details
Main Authors:	Hakimjavadi, Hesamedin, Masrek, Mohamad Noorman
Format:	Recurso educativo Open Access
Language:	en
Published:	2013
Subjects:	Electronic Libraries Theses Information Systems Computer Software Standards Mixed Methods Research Surveys
Online Access:	Acceder al recurso
Tags:	Add Tag No Tags, Be the first to tag this record!

_version_	1867181891728179200
author	Hakimjavadi, Hesamedin Masrek, Mohamad Noorman
author_facet	Hakimjavadi, Hesamedin Masrek, Mohamad Noorman Hakimjavadi, Hesamedin Masrek, Mohamad Noorman
collection	Education Resources Information Center
contents	Evaluation of Interoperability Protocols in Repositories of Electronic Theses and Dissertations Hakimjavadi, Hesamedin Masrek, Mohamad Noorman Electronic Libraries Theses Information Systems Computer Software Standards Mixed Methods Research Surveys Purpose: The purpose of this study is to evaluate the status of eight interoperability protocols within repositories of electronic theses and dissertations (ETDs) as an introduction to further studies on feasibility of deploying these protocols in upcoming areas of interoperability. Design/methodology/approach: Three surveys of 266 ETD repositories, 15 common ETD management software solutions, and 136 ETD experts were conducted in order to appraise the protocols. These protocols were evaluated in four categories of aggregation, syndication, distributed search, and publishing protocols. Findings: This study revealed that, despite its drawbacks, Protocol for Metadata Harvesting (PMH) is still the most utilized interoperability protocol within ETD providers, ETD software developers, and implementers, followed by ATOM and Object Reuse and Exchange (ORE) protocols. However, in all competitive areas related to performance and functionality, ORE surpasses other protocols. It was also found that the three protocols of ATOM, PMH, and ORE could be used interchangeably in the most used cases of interoperability protocols in repositories. Practical implications: In this research, a combination of methods was employed to evaluate the status of protocols, from the perspectives of data providers, software providers, and implementers. Practitioners may use these methods to assess other protocols in terms of effectiveness and efficiency. Originality/value: The conduct of this study has involved three types of surveys, through which different aspects of interoperability protocols are evaluated. Prior to the conduct of this study, there has yet any study focusing on the same topic, which has adopted the multi-method that has been adopted in this study. (Contains 9 tables and 16 figures.)
format	Recurso educativo Open Access
id	eric_EJ1004424
institution	ERIC Institute of Education Sciences
language	en
publishDate	2013
record_format	eric
spellingShingle	Evaluation of Interoperability Protocols in Repositories of Electronic Theses and Dissertations Hakimjavadi, Hesamedin Masrek, Mohamad Noorman Electronic Libraries Theses Information Systems Computer Software Standards Mixed Methods Research Surveys Evaluation of Interoperability Protocols in Repositories of Electronic Theses and Dissertations Hakimjavadi, Hesamedin Masrek, Mohamad Noorman Electronic Libraries Theses Information Systems Computer Software Standards Mixed Methods Research Surveys Purpose: The purpose of this study is to evaluate the status of eight interoperability protocols within repositories of electronic theses and dissertations (ETDs) as an introduction to further studies on feasibility of deploying these protocols in upcoming areas of interoperability. Design/methodology/approach: Three surveys of 266 ETD repositories, 15 common ETD management software solutions, and 136 ETD experts were conducted in order to appraise the protocols. These protocols were evaluated in four categories of aggregation, syndication, distributed search, and publishing protocols. Findings: This study revealed that, despite its drawbacks, Protocol for Metadata Harvesting (PMH) is still the most utilized interoperability protocol within ETD providers, ETD software developers, and implementers, followed by ATOM and Object Reuse and Exchange (ORE) protocols. However, in all competitive areas related to performance and functionality, ORE surpasses other protocols. It was also found that the three protocols of ATOM, PMH, and ORE could be used interchangeably in the most used cases of interoperability protocols in repositories. Practical implications: In this research, a combination of methods was employed to evaluate the status of protocols, from the perspectives of data providers, software providers, and implementers. Practitioners may use these methods to assess other protocols in terms of effectiveness and efficiency. Originality/value: The conduct of this study has involved three types of surveys, through which different aspects of interoperability protocols are evaluated. Prior to the conduct of this study, there has yet any study focusing on the same topic, which has adopted the multi-method that has been adopted in this study. (Contains 9 tables and 16 figures.)
title	Evaluation of Interoperability Protocols in Repositories of Electronic Theses and Dissertations
topic	Electronic Libraries Theses Information Systems Computer Software Standards Mixed Methods Research Surveys
url	https://eric.ed.gov/?id=EJ1004424

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	"eae0989b0ff9223a6b7044c264b33b65"

Session

Key	Value
__Laminas	array:2 [`"_REQUEST_ACCESS_TIME" => 1789485101.6476 "_VALID" => array:1 [ "Laminas\Session\Validator\Id" => "eae0989b0ff9223a6b7044c264b33b65" ]`]
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=eae0989b0ff9223a6b7044c264b33b65"
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	"38467"
REDIRECT_URL	"/Record/eric_EJ1004424/Details"
GATEWAY_INTERFACE	"CGI/1.1"
SERVER_PROTOCOL	"HTTP/1.1"
REQUEST_METHOD	"GET"
QUERY_STRING	""
REQUEST_URI	"/Record/eric_EJ1004424/Details"
SCRIPT_NAME	"/index.php"
PHP_SELF	"/index.php"
REQUEST_TIME_FLOAT	1789485101.6428
REQUEST_TIME	1789485101

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	"eae0989b0ff9223a6b7044c264b33b65"

Session

Key	Value
__Laminas	array:2 [`"_REQUEST_ACCESS_TIME" => 1789485101.6476 "_VALID" => array:1 [ "Laminas\Session\Validator\Id" => "eae0989b0ff9223a6b7044c264b33b65" ]`]
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=eae0989b0ff9223a6b7044c264b33b65"
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	"38467"
REDIRECT_URL	"/Record/eric_EJ1004424/Details"
GATEWAY_INTERFACE	"CGI/1.1"
SERVER_PROTOCOL	"HTTP/1.1"
REQUEST_METHOD	"GET"
QUERY_STRING	""
REQUEST_URI	"/Record/eric_EJ1004424/Details"
SCRIPT_NAME	"/index.php"
PHP_SELF	"/index.php"
REQUEST_TIME_FLOAT	1789485101.6428
REQUEST_TIME	1789485101

Environment Variables empty

Registered Handlers

0. Whoops\Handler\PrettyPageHandler

Similar Items

Environment & details:

Environment & details: