Willow: A Uniform Search Interface

Ketchell, Debra S.; Freedman, M. M.; Jordan, William E.; Lightfoot, Edward M.; Heyano, Scott L.; Libbey, Peter A.

doi:10.1136/jamia.1996.96342647

Cited by 5 publications

(2 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Interestingly, Z39.50 access to library catalogs is still widely available across libraries, including our own library (Library of Congress, 2023). Z39.50 has traditionally been used to support data delivery for graphical-based applications like federated search (Ketchell et al, 1996), as well as for connecting bibliographic software to library catalogs (East, 2003). However, Z39.50 can also be used to search library catalogs programmatically with scripts.…”

Section: Z3950 For Library Catalog Datamentioning

confidence: 99%

Creating a Scholarly API Cookbook: Supporting Library Users with Programmatic Access to Information

Scalfani,

Walker,

Simpson

et al. 2023

ISTL

View full text Add to dashboard Cite

Scholarly web-based application programming interfaces (APIs) allow users to interact with information and data programmatically. Interacting with information programmatically allows users to create advanced information query workflows and quickly access machine-readable data for downstream computations. With the growing availability of scholarly APIs from open and commercial library databases, supporting access to information via an API has become a key support area for research data services in libraries. This article describes our efforts with supporting API access through the development of an online Scholarly API Cookbook. The Cookbook contains code recipes (i.e., tutorials) for getting started with 10 different scholarly APIs, including for example, Scopus, World Bank, and PubMed. API tutorials are available in Python, Bash, Matlab, and Mathematica. A tutorial for interacting with library catalog data programmatically via Z39.50 is also included, as traditional library catalog metadata is rarely available via an API. In addition to describing the Scholarly API Cookbook content, we discuss our experiences building a student research data services programming team, challenges we encountered, and ideas to improve the Cookbook. The University of Alabama Libraries Scholarly API Cookbook is freely available and hosted on GitHub. All code within the API Cookbook is licensed with the permissive MIT license, and as a result, users are free to reuse and adapt the code in their teaching and research.

show abstract

Section: Z3950 For Library Catalog Datamentioning

confidence: 99%

Creating a Scholarly API Cookbook: Supporting Library Users with Programmatic Access to Information

Scalfani,

Walker,

Simpson

et al. 2023

ISTL

View full text Add to dashboard Cite

show abstract

“…In the 1980s, librarians collaborated with campus computing to develop a graphical interface to MEDLINE and other literature databases using the X‐Windows platform (Ketchell et al , 1996a, 1992). This local development placed bibliographic databases directly onto the wards in the medical centers.…”

Section: Introductionmentioning

confidence: 99%

FDR_x (Federated Drug Reference) project as change agent

Jankowski

Ketchell

2005

Reference Services Review

View full text Add to dashboard Cite

PurposeAt the foundation of FDRx was the drug formulary for UW Medicine published by the Drug Information Center. The DIC pharmacist had contracted with USPDI to receive the full text of its drug information electronically and reformat it into a print, pocket‐sized guide for distribution to clinicians. The goal of the FDRx project was to add to this core and distribute an expanded drug reference as part of a clinical resource.Design/methodology/approachLibrarians at the University of Washington Health Sciences Libraries collaborated with clinicians to create an electronic federated drug knowledge resource, FDRx, to be used at the point of care.FindingsSkills and experiences gained in previous projects, e.g. negotiating the licensure of campus‐wide access to bibliographic databases, project leadership, developing interfaces, instruction in the use of information resources, and IAIMS planning, easily transferred to the development of the FDRx project. The most immediate outcome, FDRx itself, had a short but successful lifespan, meeting the drug information needs of its users.Originality/valueThis partnership set the stage for future developments in the knowledge management arena at the University of Washington and changes in the roles of librarians.

show abstract