LibGuides Administration: Roadmap To Engaging Content

Libraries purchase LibGuides software in the effort to provide all users with easy access to engaging library content. Active administration of the software is a vital component in realizing this goal. In the summer of 2014, Miami University Libraries migrated from LGv1 to LGv2. A small group had traditionally overseen the administrative aspects of the LibGuides software that included managing accounts and troubleshooting. The migration to LGv2 created a unique opportunity for the group to re-evaluate their administration and take a more active role in implementing a broader vision of the use of LibGuides in order to meet the needs of faculty, staff, and students

Abstract Interfaces for Data Analysis: Component Architecture for Data Analysis Tools

The fast turnover of software technologies, in particular in the domain of interactivity (covering user interface and visualisation), makes it difficult for a small group of people to produce complete and polished software-tools before the underlying technologies make them obsolete. At the HepVis '99 workshop, a working group has been formed to improve the production of software tools for data analysis in HENP. Beside promoting a distributed development organisation, one goal of the group is to systematically design a set of abstract interfaces based on using modern OO analysis and OO design techniques. An initial domain analysis has come up with several categories (components) found in typical data analysis tools: Histograms, Ntuples, Functions, Vectors, Fitter, Plotter, Analyzer and Controller. Special emphasis was put on reducing the couplings between the categories to a minimum, thus optimising re-use and maintainability of any component individually. The interfaces have been defined in Java and C++ and implementations exist in the form of libraries and tools using C++ (Anaphe/Lizard, OpenScientist) and Java (Java Analysis Studio). A special implementation aims at accessing the Java libraries (through their Abstract Interfaces) from C++. This paper gives an overview of the architecture and design of the various components for data analysis as discussed in AIDA

Publishing E-resources of Digital Institutional Repository as Linked Open Data: an experimental study

Linked open data (LOD) is an essential component in semantic web architecture and is becoming increasingly important over time due to its ability to share and re-use structured data which is both human and computer readable over the web. Currently, many libraries, archives, museums etc. are using open source digital library software to manage and preserve their digital collections. They may also intend to publish their e-resources as “Linked Open Datasets” for further usage. LOD enables the libraries or information centers to publish and share the structured metadata that is generated and maintained with their own bibliographic and authority data in such a way that the other libraries and general community across the world can consume, interact, enrich and share. In this context, the key issue is to convert the library bibliographic data which is commonly known as metadata into LOD dataset. The purpose of this paper is to provide a methodology and technical aspects to design and publish a structured LOD dataset of bibliographic information from a digital repository developed with DSpace digital library software so that other libraries can link their repositories with these LOD for providing additional relevant resources to their end-users. The paper shows the process of integration and configuration of Apache Jena Fuseki (a tool for SPARQL Endpoint interface) with DSpace for converting metadata into Resource Description Framework (RDF) triple model and make them available in various RDF formats. It also discusses a model for building a LOD framework to convert and store RDF graph and RDF triple. Finally, it tests the accessibility of the inked open dataset by querying RDF data through a SPARQL endpoint interface

Bridging the gap between design and implementation of components libraries

Object-oriented design is usually driven by three main reusability principles: step-by-step design, design for reuse and design with reuse. However, these principles are just partially applied to the subsequent object-oriented implementation, often due to efficienc y constraints, yielding to a gap between design and implementation. In this paper we provide a solution for bridging this gap for a concrete framework, the one of designing and implementing container-like component libraries, such as STL, Booc h Components, etc. Our approach is based on a new design pattern together with its corresponding implementation. The proposal enhances the same principles that drive the design process: step-by--step implementation (adding just what is needed in every step), implementation with reuse (component implementations are reused while library implementation progresses and component hierarchies grow) and implementation for reuse (intermediate component implementations can be reused in many different points o f the hierarchy). We use our approach in two different manners: for building a brand-new container-like component library, and for reengineering an existing one, Booch Components in Ada95.Postprint (published version

Software (Re-)Engineering with PSF III: an IDE for PSF

We describe the design of an integrated development environment (IDE) for PSF. In the software engineering process we used process algebra in the form of PSF for the specification of the architecture of the IDE. This specification is refined to a PSF specification of the IDE system as a ToolBus application, by applying vertical and horizontal implementation techniques. We implemented the various tools as specified and connected them with a ToolBus script extracted from the system specification

Safety-related challenges and opportunities for GPUs in the automotive domain

GPUs have been shown to cover the computing performance needs of autonomous driving (AD) systems. However, since the GPUs used for AD build on designs for the mainstream market, they may lack fundamental properties for correct operation under automotive's safety regulations. In this paper, we analyze some of the main challenges in hardware and software design to embrace GPUs as the reference computing solution for AD, with the emphasis in ISO 26262 functional safety requirements.Authors would like to thank Guillem Bernat from Rapita Systems for his technical feedback on this work. The research leading to this work has received funding from the European Re-search Council (ERC) under the European Union's Horizon 2020 research and innovation programme (grant agreement No. 772773). This work has also been partially supported by the Spanish Ministry of Science and Innovation under grant TIN2015-65316-P and the HiPEAC Network of Excellence. Jaume Abella has been partially supported by the Ministry of Economy and Competitiveness under Ramon y Cajal postdoctoral fellowship number RYC-2013-14717. Carles Hernández is jointly funded by the Spanish Ministry of Economy and Competitiveness and FEDER funds through grant TIN2014-60404-JIN.Peer ReviewedPostprint (author's final draft

Turnaround Time Between ILLiad’s Odyssey and Ariel Delivery Methods: A Comparison

Interlibrary loan departments are frequently looking for ways to reduce turnaround time. The advent of electronic delivery in the past decade has greatly reduced turnaround time for articles, but recent developments in this arena have the potential to decrease that time even further. The ILLiad ILL management system has an electronic delivery component, Odyssey, with a Trusted Sender setting that allows articles to be sent to patrons without borrowing staff intervention, provided the lending library is designated as a Trusted Sender, or this feature is enabled for all lenders. Using the tracking data created by the ILLiad management system, the turnaround time for two delivery methods, Ariel and Odyssey, was captured for two different academic institutions. With the Trusted Sender setting turned on, Odyssey delivery was faster than Ariel for the institutions studied

Extending the 5S Framework of Digital Libraries to support Complex Objects, Superimposed Information, and Content-Based Image Retrieval Services

Advanced services in digital libraries (DLs) have been developed and widely used to address the required capabilities of an assortment of systems as DLs expand into diverse application domains. These systems may require support for images (e.g., Content-Based Image Retrieval), Complex (information) Objects, and use of content at fine grain (e.g., Superimposed Information). Due to the lack of consensus on precise theoretical definitions for those services, implementation efforts often involve ad hoc development, leading to duplication and interoperability problems. This article presents a methodology to address those problems by extending a precisely specified minimal digital library (in the 5S framework) with formal definitions of aforementioned services. The theoretical extensions of digital library functionality presented here are reinforced with practical case studies as well as scenarios for the individual and integrative use of services to balance theory and practice. This methodology has implications that other advanced services can be continuously integrated into our current extended framework whenever they are identified. The theoretical definitions and case study we present may impact future development efforts and a wide range of digital library researchers, designers, and developers