Abstract: Article discussing the notion that viewing MARC from a modern technological perspective leads to interpretive problems such as a confusion of "bibliographic data" with "catalog records"

Abstract: This article discusses how the UC San Diego Libraries developed and implemented a mobile website by giving a small collaborative group decision-making authority for all of the library stakeholders. The group used rapid development and testing cycles with an understanding that delivering a fast and good enough service was preferable over slow and seemingly perfect development.

Abstract: The Mansfield Library subscribes to the Readex database U.S. Congressional Serial Set, 1817-1994 (full-text historic reports of Congress and federal agencies). Given the option of purchasing MARC records for all 262,000 publications in the Serial Set or making use of free access to simple Dublin Core records provided by Readex, the library opted to repurpose the free metadata. The process that the Mansfield Library used to obtain the Dublin Core records is described, including the procedures for crosswalking the metadata to MARC21 and batch loading the bibliographic records complete with holdings information to the local catalog. This report shows that we successfully achieved our goals of dramatically increasing access to Serial Set material by exposing metadata in the local catalog and discusses the challenges we faced along the way. We hope that others tasked with the manipulation of metadata will be able to use what we learned from this project.

Abstract: This article describes the implementation of SubjectsPlus to manage the subject guides at the Wichita State University Libraries. The decision to implement an open source solution, the implementation process, and customizations to the software are discussed. In addition to the subject guides, SubjectsPlus is also used to manage course specific and miscellaneous topic guides, the library staff directory, and database links. The article also covers the reception of SubjectsPlus by the librarians and teaching faculty.

Abstract: Many organizations, including libraries, are turning to content management systems to simplify the management of their websites. Alfred University‘s Herrick Memorial Library recently implemented a new website using Joomla, an open-source content management system. While Drupal has received significant attention in the library community, Joomla may be a more practical choice for some libraries. The purpose of this paper is to share our experience with Joomla so that other libraries can more easily evaluate its suitability to their environment.

Abstract: Many researchers make their publications available on personal web pages. In this paper, we propose a simple method for the automatic aggregation of these documents. We search faculty web pages for archived publications and present their full text links together with the author’s name and short content excerpts on a comprehensive web page. The excerpts are generated simply by querying a standard web search engine.

Abstract: Members of a Swiss, Austrian and German network of health care libraries planned to build a collaborative article reference database. Since different libraries were cataloging articles on their own, and many national health care journals can not be found in other repositories (free or commercial) the goal was to merge existing collections and to enable participants to catalog articles on their own. As of November, 2010, the database http://bibnet.org contains 45,000 article references from 17 libraries. In this paper we will discuss how the software concept evolved and the problems we encountered during this process.

Abstract: Drupal is a powerful, but complex, Web Content Management System, being adopted by many libraries. Installing Drupal typically involves adding additional modules for flexibility and increased functionality. Although installing additional modules does increase functionality, it inevitably complicates usability. At the University of Houston Libraries, the Web Services department researched what modules work well together to accomplish a simpler interface while simultaneously providing the flexibility and advanced tools needed to create a successful user experience within Drupal. This article explains why particular modules were chosen or developed, how the design enhanced the user experience, how the CMS architecture was created, and how other library systems were integrated into Drupal. URI http://journal.code4lib.org/articles/4578 http://hdl.handle.net/10657/1304 Collections UH Faculty, Staff, and Student Works DSpace software copyright © 2002-2016 DuraSpace Contact Us | Send Feedback Theme by Improving the Drupal user experience  use them. Placing an emphasis on the content authoring experience will undoubtedly impact the way we build our sites, but I believe this is for the better. And I’m not the only one, which is why Drupal 8 will be shipping with a plethora of improvements on the content authoring front. But let’s talk about Drupal 7 for now. Drupal already has the structure in place to be user-friendly from a content creator’s perspective. Every field we create in Drupal comes with a help text section. Some developers fill in this field a brief instruction, some even leave it blank. I say, FILL IT UP PROPERLY!

Abstract: In 2008, the Library of Virginia (LVA) selected the digital asset management system DigiTool to host a centralized collection of digital state government publications. The Virginia state digital repository targets three primary user groups: state agencies, depository libraries and the general public. DigiTool's ability to create depositor profiles for individual agencies to submit their publications, its integration with the Aleph ILS, and product support by ExLibris were primary factors in its selection. As a smaller institution, however, LVA lacked the internal resources to take full advantage of DigiTool's full set of features. The process of cataloging a heterogenous collection of state documents also proved to be a challenge within DigiTool. This article takes a retrospective look at what worked, what did not, and what could have been done to improve the experience.