ALCTS Catalog Norms Interest Group Meeting, ALA Annual 2009
Beyond the OPAC:
Creating Different Interfaces
for Specialized Collections
in an ILS System
Sai Deng, Metadata Catalog Librarian
Wichita State University Libraries
Some Context
o DSpace Manakin:
o XML user interface using SAX & the Cocoon
framework in DSpace;
o Enable different “themes” (look and feel) for a
single page, a collection and a community.
o OPAC Skins:
o In Voyager 7, its OPAC is also called “Tomcat
WebVoyage”;
o Built on XML, XSLT, CSS, and a new directory
structure.
Some Context
o Limitations of the OPAC skins:
o What exactly can be displayed differently:
o Header, footer, record display, page messages;
o Separate display for serials;
o Embedded Googlebook search, embedded cover images…
o Content and skin need to be inside the ILS;
o Very limited in styling different sets of data.
o Our question: What if we would like to have
separate interfaces for featured collections, featured
authors and special occasions?
Some Context
o Why do we create websites featuring
collections?
o
o
o
o
o
Greater exposure of library materials;
Refined access and easier discovery;
More varied and appealing interfaces;
Increase publicity of a subject area or an author;
Supplemental to library programs and library
instructions;
o Data ready in Voyager, only needs some massage;
o “We have done local notes for years for donor notes
and collection information in Voyager.” (Nancy Deyoe)
Beyond the OPAC: Creating Different
Interfaces for Specialized Collections
o Faculty author website (for Shocker Scholar
Festival)
o Leisure reading collection
o Featured authors (tied to public
programming)
o Featured subject area (tied to library
instruction)
o Special formats: video resources, e-books
o Specialized collections (e.g. Wichita Art
Museum titles)
How to Draw Data from the Library
Catalog Database
o Systems:
o Ex Libris Voyager 7.0.4 ILS
o Sun Solaris 10 server
o Oracle 10g database
o Two options:
o Using an ODBC (Open Database Connectivity)
connection
o Using Voyager Analyzer
ODBC vs. Voyager Analyzer
o ODBC connection
o An interface to access data from diverse database management
systems (DBMSs);
o Microsoft Access connects to Voyager DB through ODBC driver;
o ODBC query results can be saved as text, html (plain table
looking), xml (showing fields from the query results table, not in
MarcXML format).
o We chose ODBC simply because we just recently purchased
Voyager Analyzer.
o Voyager Analyzer
o Intuitive Cognos web portal, connected to Voyager database;
o Output reports in HTML, PDF, Excel, Delimited Text (CSV) and
XML;
o Exported HTML is in plain table looking, and XML in the form of
“data” “row” “value” (not MarcXML).
Blob Query to Identify Faculty
Books
o SELECT DISTINCTROW RO_WSUDB_BIB_TEXT.BIB_ID,
RO_WSUDB_BIB_TEXT.AUTHOR, RO_WSUDB_BIB_TEXT.TITLE,
RO_WSUDB_BIB_TEXT.EDITION, RO_WSUDB_BIB_TEXT.ISBN,
RO_WSUDB_BIB_TEXT.PUBLISHER_DATE,
RO_WSUDB_BIB_TEXT.IMPRINT,
RO_WSUDB_BIB_LOCATION.LOCATION_ID,
GetFieldAll(GetBibBlob([RO_WSUDB_BIB_TEXT.BIB_ID]),"590")
AS Expr1,
GetFieldAll(GetBibBlob([RO_WSUDB_BIB_TEXT.BIB_ID]),"700")
AS Expr2 INTO query590view
o FROM RO_WSUDB_BIB_TEXT INNER JOIN
RO_WSUDB_BIB_LOCATION ON
RO_WSUDB_BIB_TEXT.BIB_ID=RO_WSUDB_BIB_LOCATION.BI
B_ID
o WHERE
((GetFieldAll(GetBibBlob([RO_WSUDB_BIB_TEXT.BIB_ID]),"590"
)) Like "*WSU Faculty*");
Web Delivery and Dataflow
If available
Web
RSS Feed
Display
Search
Syndetic Cover
Images
If not
available
ASP/
XHTML/
CSS
Access
(Query Results)
ODBC Blob Query
Voyager Oracle
Database
BibID
ISBN
Local Cover
Images
Project 1: Faculty Author Books
o Browse
by:
o Name
o Title
o Date
o Retrieve
data:
SELECT
[Fields]
From [Table]
ORDER
by…
o Page
division
in ASP
Site: http://library.wichita.edu/techserv/WSU_faculty/
Faculty Author Books: Search
o Keyword
Search
(Written in
ASP)
Adding Syndetic Cover and
Local Cover Images
o Added some local
covers for books
without Syndetic
covers;
o If local covers are
available, use
local images;
o If local covers not
available:
o
o
Use Syndetic
covers based
on ISBNs
(Either show
covers or
blank);
If no ISBN,
use a generic
local cover.
Adding Local and Syndetic Cover Images (*In
Case You Would Like to Refer to the Code)
o
o
o
o
o
o
o
o
o
o
o
o
o
o
Code from browse.asp:
Add specific
…<td class="image" rowspan="6">
large and small
<% If ((Recordset1.Fields.Item("localCover").Value <> "") AND
local covers
(Recordset1.Fields.Item("localCover").Value <> " ")) Then %>
<a href="localcover\<%=(Recordset1.Fields.Item("localCover").Value)%>L.jpg"
target="_blank">
<img border=0 src="localcover\<%=(Recordset1.Fields.Item("localCover").Value)%>.jpg"
/></a>
<% Else %>
Image link to add
<% If ((Recordset1.Fields.Item("ISBN").Value <> "") AND
(Recordset1.Fields.Item("ISBN").Value <> " ")) Then %>
Syndetic covers
<a
href="http://syndetics.com/hw7.pl?isbn=<%=(Recordset1.Fields.Item("ISBN").Value)%>/lc.j
pg&client=wichitasu" target="_blank">
<img border=0
src="http://syndetics.com/hw7.pl?isbn=<%=(Recordset1.Fields.Item("ISBN").Value)%>/sc.g
if&client=wichitasu" /></a>
<% Else %>
Add local
generic cover
<img alt="book cover" src=“localCover/cover.jpg" />
<% End If %>
<% End If %>
</td> …
Adding RSS Feed
RSS feed icon
Adding RSS Feed (*You can do
this)
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
pubupdate.rss
<channel>
<title>WSU Libraries: Faculty Author Published Books Update</title>
<link>http://library.wichita.edu/techserv/WSU_Faculty/index.asp</link>
<description>Update on published books of Faculty Author available at WSU Libraries</description>
<language>en-us</language>
<pubDate>Fri, 6 Mar 2009 04:00:00 GMT</pubDate>
Required Channel
<lastBuildDate>Fri, 6 Mar 2009 04:00:00 GMT</lastBuildDate>
elements:
<docs>http://library.wichita.edu/RSS</docs>
<managingEditor>…@wichita.edu</managingEditor>
title, link,
<webMaster>…@wichita.edu</webMaster>
description
<item>
<title>It grows in winter and other poems / Chinyere Okafor. </title>
<link>http://library.wichita.edu/techserv/WSU_faculty/browse.asp?browse_type=PUBLISHER_DATE</link>
<description>Get more information on this book and other WSU faculty publications at Faculty Research
added to the webpage
Showcase Website.</description>
header
<pubDate>Thu, 5 Mar 2009 04:00:00 GMT</pubDate>
</item>
…
</Channel>
</rss>
<link rel="alternate" type="application/rss+xml" title="Faculty Author - Recent Books
[RSS]" href="http://library.wichita.edu/techserv/WSU_faculty/pubupdate.rss">
Linking Back to OPAC
o Use
Permanent
links
e.g. http://libcat.wichita.edu/cgi-bin/Pwebrecon.cgi?BBID=1359301
Identify Other Specialized
Collections at WSU
o Leisure Reading books: based on location
(LOCATION_ID=99)
o Wichita Art Museum items: based on
location (LOCATION_ID=122)
o New Books: based on date
o Goldbarth poems: based on uniform title
(730 Albert Goldbarth Collection.)
o Women Studies’ Video Resources: based
on local notes (590)
Project 2: Women’s Studies Video
Resources Website
Women’s Studies Video Resources Website
o Data selected by Women's Studies Library Liaison;
o Used local notes field to identify these resources in
Voyager;
o Created a separate interface for the resources;
o Based on the same model for Faculty Author Website:
o Data drawn from ODBC blob query;
o Applied a different CSS style sheet;
o Browse and keyword search written in ASP;
o Added RSS feed, local and Syndetic covers;
o Every record linked back to OPAC;
o Considered compliance to web standards (e.g. CSS, xhtml and Section
508);
o Collection description and help documentation available.
o Website created as a supplemental tool for women
studies source guide and library instruction.
Alternative Approaches to Create
Interfaces for Datasets
o Approach 1: (ODBC query results, or other datasets),
XML file, XQuery interface
o Approach 2: (ODBC query results, or other datasets),
XML file, implement WebLucene
o Lucene search engine XML interface;
o SAX based indexing, XML output;
o Use ASP/JSP/PHP/XSLT to display data.
o One more big step: make data OAI-PMH compliant and
become a data provider.
o Transform data to OAI_DC formats;
o Data can be transformed to OAI qualified DC (if definitely
necessary);
o Is it necessary to make sets of data from traditional library
catalog database harvestable in OAI_DC? Maybe for some
cases. E.g. local e-books, ETDs;
o Implement an OAI interface (e.g. U of Michigan’s OAI Toolkit; or
use a system with a built-in OAI interface).
Test 1: Marc to DC Mapping
o MARC (in Voyager table) to DC mapping
o
o
o
o
o
o
o
o
o
o
o
Marc field
Simple DC
001 BIB_ID
not mapped
020 ISBN
Identifier
100 AUTHOR
Contributor
245 TITLE
Title
250 EDITION
Description
260$a$b IMPRINT
Publisher
260$c PUBLISHER_DATE
Date
852$b LOCATION
Relation
590 notes (Expr1 in query)
Description
700 other author (Expr 2 in query) Contributor
Qualified DC
Date.issued
Relation.isPartOf (housing at)
o Additional fields added:
o Link to OPAC/library catalog
o Cover image link
Source
Relation
Relation.hasPart (*contained item)
Test 1: Notes
o 700 (other authors) is combined with 100 (author) in the
database. It is for better display in “Browse by author”
since many 100 fields are blank and many local authors
are in 700 (e.g. editor…);
o localCover field is added to the database (use Bib_ID to
link it) and converted to Relation.haspart;
o OPAC records permanent link (based on Bib_ID) added;
o Cleaned data in Access table, e.g. deleted half bracket
“]” in publisher date field;
o Used ASP.net to transform query results (saved as xml,
but it is not in MarcXML format) to DCXML;
o Dealt with special reserved character (e.g. &, “”) in XML
transformation.
Test 1: OAI Qualified DC XML Record
Sample
o
<?xml version="1.0" encoding="UTF-8"?>
<qualifieddc
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://www.dublincore.org/schemas/xmls/qdc/2008/0
2/11/qualifieddc.xsd">
<dc:identifier>9780805856224</dc:identifier>
<dc:contributor>Coleman, Hardin L. K. Yeh, Christine J.</dc:contributor>
<dc:title>Handbook of school counseling / edited by Hardin L.K.
Coleman, Christine Yeh.</dc:title>
<dc:description/>
<dc:publisher>London : Routledge, c2008.</dc:publisher>
<dcterms:issued>2008.</dcterms:issued>
<dcterms:isPartOf>WSU Stacks.</dcterms:isPartOf>
<dc:description>WSU faculty author.</dc:description>
<dc:source>http://libcat.wichita.edu/cgibin/Pwebrecon.cgi?BBID=1344456</dc:source>
<dcterms:hasPart/>
</qualifieddc>
o Record sample reviewed by Timothy Cole at UIUC.
o Records transformed from query results saved in xml.
Test 2: OAI_DC XML Record Sample
o <?xml version="1.0" encoding="UTF-8"?>
<oai_dc:dc
xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/
http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
<dc:identifier>9780805856224</dc:identifier>
<dc:contributor>Coleman, Hardin L. K. Yeh, Christine J.</dc:contributor>
<dc:title>Handbook of school counseling / edited by Hardin L.K.
Coleman, Christine Yeh.</dc:title>
<dc:description/>
<dc:publisher>London : Routledge, c2008.</dc:publisher>
<dc:date>2008.</dc:date>
<dc:relation>WSU Stacks.</dc:relation>
<dc:description>WSU faculty author.</dc:description>
<dc:source>http://libcat.wichita.edu/cgibin/Pwebrecon.cgi?BBID=1344456</dc:source>
<dc:relation/>
</oai_dc:dc>
Possible Next Steps
o Creating other featuring sites based on
our current model (the easiest
approach);
o Adding local covers to Voyager directly;
o Transform datasets to xml and create
XQuery interface;
o Implement OAI interface for some very
important datasets (e.g. special
collections)? This is different from our
current DSpace IR services.
Final Thoughts: (Dis)Integration of
Library Data and Services
o Integration of library data and services
o Centralized interface (e.g. Federated search);
o Unified user experience (information discovery and delivery from a
single place);
o Slower or less reliable?
o Overwhelming results?
o Disintegration of library data and services
o Supplemental discovery applications;
o Transferring/migrating sets of data to other environment for better
presentation, discovery and user interest;
o Can be tailored by languages, user types or library types;
o Can be multiple OPAC interfaces, or multiple specialized data
representations;
o Fragmental? Can be linked to other applications though.
o Lack of uniformality?
Final Thoughts: Beyond the OPAC
o Beyond the OPAC
o New ways in data aggregation
o Specialized collections retrieval and representation
o WSU cases: Faculty research showcase, Women’s Studies
Video Resources
o Data transformation, harvesting, FRBRizing…
o Add new discovery layers
o AquaBrower, Endeca, Encore, Primo…
o Optimize OPAC interaction and add miscellaneous services
o Syndetic and Amazon covers, spell checker, LibraryThing…
o Another special case: WSU dynamic 3D shelving maps
o More to think about : DLF ILS Discovery Interface
Recommendations
o Four levels of interoperability to provide discovery outside
the ILS
o Basic discovery interfaces; Elementary OPAC supplement;
Elementary OPAC alternative; Robust/domain-aware discovery
platform
Contacts and Acknowledgements
o Sai Deng, Metadata Catalog Librarian, Wichita State University
Libraries, Sai.Deng@wichita.edu
o Nancy Deyoe, Assistant Dean for Technical Services, Wichita State
University Libraries, Nancy.Deyoe@wichita.edu
o Gemma Blackburn, Systems Developer, Wichita State University
Libraries, Gemma.Blackburn@wichita.edu
o Susan Matveyeva, Catalog and Institutional Repository Librarian,
Wichita State University Libraries, Susan.Matveyeva@wichita.edu
o Tse-Min Wang, Graduate Student in Computer Science, Wichita
State University Libraries, txwang@wichita.edu
o Special thanks to Timothy W. Cole, Mathematics Librarian, Interim
Head, Digital Services and Development, University of Illinois at
Urbana-Champaign.
References
o
o
o
o
o
o
o
o
DSpace Wiki. “DSpace XMLUI: Manakin Project”. Available at:
http://wiki.dspace.org/index.php//Manakin
Dublin Core Metadata Initiative. “Guidelines for implementing Dublin Core in XML”.
Available at: http://dublincore.org/documents/dc-xml-guidelines/
Ex Libris Group. “Voyager® 7.0 WebVoyáge Architecture Overview and
Configuration Models”. December 2008. SupportWeb. Available at:
https://support.endinfosys.com/
ILS-DI Task Group Members. “DLF ILS Discovery Interface Task Group (ILS-DI)
Technical Recommendation: An API for effective interoperation between integrated
library systems and external discovery Applications”. Revision 1.1. December 8,
2008. Available at: http://diglib.org/architectures/ilsdi/DLF_ILS_Discovery_1.1.pdf
Library of Congress. Development and MARC Standards Office. “MARC to Dublin
Core Crosswalk”. Available at: http://www.loc.gov/marc/marc2dc.html
The OAI Executive and the OAI Technical Committee. “The Open Archives
Initiative Protocol for Metadata Harvesting”. Available at:
http://www.openarchives.org/OAI/openarchivesprotocol.html
WSU Libraries. Faculty research showcase. 2009. Available at:
http://library.wichita.edu/techserv/WSU_faculty/
WSU Libraries. Women’s Studies Video Resources. 2009. Available at:
http://library.wichita.edu/techserv/Women'sStudies/
Thank you!
Questions?