Jonathan and Mark,
All very interesting ideas. Could anyone share with me some code or
pseudocode for QAD parsing of LC call numbers? Thanks in advance,
Hunter
L. Hunter Kevil
Collection Development Librarian
University of Missouri-Columbia
Columbia, MO 65201
573-884-8760
kevill_at_missouri.edu
-----Original Message-----
From: Next generation catalogs for libraries
[mailto:NGC4LIB_at_listserv.nd.edu] On Behalf Of Jonathan Rochkind
Sent: Thursday, August 09, 2007 9:30 AM
To: NGC4LIB_at_listserv.nd.edu
Subject: Re: [NGC4LIB] dynamic stacks maps?
Mark, that sounds interesting. Does it deliver an actual graphical map
to the user, or just textual directions?
Many of those 'experimental' services you talk about are in fact similar
(or identical) to services included in Ross Singer's Umlaut link
resolver front end, which I am now working on too for adoption here at
Hopkins. (http://umlaut.library.gatech.edu/umlaut ; and
http://www.oclc.org/research/announcements/features/umlaut-about.htm )
To me, it makes some intuitive sense to house these functions inside the
link resolver, as the link resolver can be thought of as the list of
'what can I do with/about this known citation'. It is increasingly the
first point-of-contact a user has with library systems, from the outside
world, for a known citation. For instance, Google Scholar and
worldcat.org will both direct users to your link resolver for citations
for known item _books_ (ie monographs), not just article citations.
Regardless of where the functionality is housed in a technical sense, I
think those kind of services need to be available both from the link
resolver menu AND from the catalog. The way I hope to do this is
essentially by putting parts of the Umlaut link resolver menu on catalog
pages.
Ross Singer did a great job with starting up Umlaut, I'm trying to help
lay some good foundations to make Umlaut something which can be easily
adopted by other libraries, with somewhat lower tech expertise/resources
than the 'early adopters' (or Ross, the original inventer!) needed.
Jonathan
Mark Dehmlow wrote:
> At Notre Dame, we've managed to link people to the floor level - it's
> a start, at least they don't have to go to another URL to find the
floor.
> Doing this at the shelf level is a bit of a different creature. We
> hope to go live with this in a couple of weeks. It's tied to a
> service we are calling "Get It" at the moment. It includes links that
> pre-fill document delivery requests for faculty, and some experimental
> services with reviews from Amazon and looking up the author in Open
WorldCat.
>
> The Map/LC parsing had some nuances, but was manageable. Essentially
> we're just looking at a simple MySQL database and some PERL scripts.
> The trickiest part was incorporating all of our different locations,
> such as branch libraries. So the script can just take a call number
> and find something in the main library or it can take a call number
> and a separate library location. We also had to accommodate the
> situation where a single item might be available from multiple
libraries (e.g.
> main library, engineering, etc.) This happens often enough. So the
> script can take multiple queries in a single URL.
>
> I am happy to share what we've done offline if anyone is interested.
>
> Regards,
>
> Mark Dehmlow
> Electronic Services Librarian
>
> Electronic Resources and Serials
> Access Department
>
> 115A Hesburgh Library | mdehmlow_at_nd.edu
> University of Notre Dame | voice: (574) 631-3092
> Notre Dame, IN 46556 | fax: (574) 631-6772
>
>
>
>
>
>
> Joe Ryan wrote:
>> Hello,
>>
>> We are considering building a dynamic book stack map application,
>> linked to our catalog, that would show a color-coded map of what
>> region of the stacks a given book is in.
>>
>> I am writing to see if anyone here has seen or developed any dynamic
>> map applications used for library stacks. I'd like to see some
>> examples for some inspiration, and I'd like to hear about any
>> experiences that you've all had when building these applications.
>>
>> Thank you,
>> Joe
>>
>> --
>> Joseph Ryan
>> Digital Projects Librarian
>> NCSU Libraries
>> (919) 513-0346
>> joseph_ryan_at_ncsu.edu
>>
>
--
Jonathan Rochkind
Digital Services Software Engineer
The Sheridan Libraries
Johns Hopkins University
410.516.8886
rochkind (at) jhu.edu
Received on Thu Aug 09 2007 - 09:20:39 EDT