LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  October 2008

CODE4LIB October 2008

Subject:

Re: creating call number browse

From:

Naomi Dushay <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Wed, 1 Oct 2008 17:34:17 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (189 lines)

I know I'm coming late to this discussion, but here are a few thoughts:

I also would LOVE to have what Emily asks for:  given an item, show me  
co-located items ... virtually.  Improve on the physical world  
limitations, if we can.  Present the information well:  familiar /  
easy to learn / usefully.  I'm not in love with call numbers, per  
se ... but the "colocation by subject" is useful.  Bookstores don't  
use call numbers, but they still shelve books by subject, and then by  
author within subject, generally.

I did some thinking about this 5 years ago:  both the meaning of call  
numbers and how to present things visually.  I don't pretend to have  
any answers, but I think I might have touched on a few of the key  
questions:

http://infoviz.comm.nsdl.org/cgi-bin/wiki.pl?VizChallenges

Why Bibliographic Metadata poses Visualization Challenges
     * there are large quantities of textual information
     * it is hard to represent all the information in a full bookcase  
onto a single monitor screen.
           o bookspine info
           o organizational info (binned and linear sorts from  
classifications ...)
     * single items can be associated with multiple parts of a  
hierarchy.
     * tree hierarchies can have vastly uneven leaf levels
     * trees can be sparsely populated
           o there may be incomplete or missing information to  
associate metadata records with hierarchies
     * controlled vocabulary problems
           o hierarchies associated with bibliographic metadata values  
more or less implicity refer to controlled vocabularies.
           o Controlled vocabularies are often too limited or too  
broad for the task at hand

1.  The user is not broken. Our faculty are very vocal in desiring a  
"virtual shelf list" that will allow them to, given a specific item,  
look for "closely located" items.  Call numbers have facilitated co- 
location of (some) related physical materials, which facilitates a  
browsing experience that users enjoy.  Maybe it's nostalgia, maybe  
it's something else ... but they enjoy it and find it useful. They are  
used to call numbers, and by god, they want call numbers.   Who are we  
to naysay?

This has been implemented already in some systems.  My local public  
library catalog has this, but Stanford does not:
go to:   http://plsiii.plsinfo.org
do a search
select a record
click on the call number link

It's not beautiful, but it's there ... more than I can say about our  
ILS or about our OSS discovery interface.

2.  Call numbers must be unique for circulation purposes.  For a  
virtual shelf list, we do not need to display multiple copies on the  
shelf.   http://infoviz.comm.nsdl.org/cgi-bin/wiki.pl?CallNumbers     
Call numbers

3.  Giving the user a new paradigm is a good thing, but it may not  
alleviate the need for the familiar.  Plus, the new paradigm has to be  
sufficiently useful / familiar / easy to learn.   Have you seen  
Aquabrowser?  The graph thingy on the left is neat looking ... but is  
it used? Perhaps it is - I don't know.

I like the concept of a coverflow ... but how much can you see at a  
glance?  Do users want to see more at a glance, or want to see  
covers?   I have no idea - let's get a usability expert out there with  
some prototypes (thanks for the prototypes everyone!)

Let's not throw the baby out with the bath water:  information on book  
spines has had decades to evolve into what is considered useful.  In a  
bookstore.  In a home library.   Do we "know better"?  Let's  
experiment knowledgeably, get user feedback and iterate!

4.  call numbers use classifications that define a (subject) hierarchy  
that is not a strict tree structure.  There has always been a tension  
between the linear shelving and the hierarchy of classification  
schemes.  http://infoviz.comm.nsdl.org/cgi-bin/wiki.pl?ClassVizReq    
Can we resolve this successfully with a virtual browse?

5.  items often fit more than one classification (more than one  
subject).  There is no reason why we can't have MULTIPLE linear  
orderings, based on various subjects / fictitious call numbers.   I'd  
love to get away from linear, but I haven't yet found a replacement  
that is familiar enough and easy enough to learn.  See http://infoviz.comm.nsdl.org/cgi-bin/wiki.pl?VizChallenges 
.

6.  can we combine subject searching (text searches, even) with these  
virtual shelves?  Imagine a treemap of resources, and as you type your  
search strings, matching areas of the tree map are highlighted.  As it  
gets down to a single area, the UI zooms in ...

For the record,  we have at least THREE distinct call number systems  
here:  LC, Dewey, and SUDOC.   It's ugly ... and it's our reality.   
What should be combined?  How should the software facilitate this?

Count me in for working on a solution.

- Naomi

On Oct 1, 2008, at 9:16 AM, Stephens, Owen wrote:

> I agree with this in general - and this was my point about the  
> 'Coverflow' in iTunes, that it allows a variety of sorting methods -  
> although it is still limited.
>
> I think there are perhaps some other factors as well. Shelf-browsing  
> allows users to wander into 'their' part of the library and look at  
> stuff - but I don't think most OPACs have the equivalent. With a  
> bookstore (physically and virtually) we might see genre sections we  
> can browse. This might also work for public libraries? In research  
> libraries we tend to just present the classification without further  
> glossing I think - perhaps this is something we ought to consider  
> online?
>
> The other thing that occurs to me about browsing by class mark is  
> that it presents a 'spectrum' view of a kind. This could be easily  
> lost in the type of 'search and sort' system you suggest (although I  
> still think this is a good idea btw). At the same time I'm a bit  
> reluctant to stop at providing a classification browse, as it seems  
> inherently limited.
>
> I agree with the point about browsing the shelves and exploring the  
> material in more depth are related - which suggests integration with  
> other content-rich services are needed (Google Books, e-books, other  
> providers)
>
> Owen Stephens
> Assistant Director: eStrategy and Information Resources
> Central Library
> Imperial College London
> South Kensington Campus
> London
> SW7 2AZ
>
> t: +44 (0)20 7594 8829
> e: [log in to unmask]
>
>> -----Original Message-----
>> From: Code for Libraries [mailto:[log in to unmask]] On  
>> Behalf Of
>> Keith Jenkins
>> Sent: 01 October 2008 13:22
>> To: [log in to unmask]
>> Subject: Re: [CODE4LIB] creating call number browse
>>
>> I think that one advantage of browsing a physical shelf is that the
>> shelf is linear, so it's very easy to methodically browse from the
>> left end of the shelf to the right, and have a sense that you haven't
>> accidentally missed anything.  (Ignore, for the moment, all the books
>> that happen to be checked out and not on the shelf...)
>>
>> Online, linearity is no longer a constraint, which is a very good
>> thing, but it does have some drawbacks as well.  There is usually no
>> clear way to follow a series of "more like this" links and get a  
>> sense
>> that you have seen all the books that the library has on a given
>> subject.  Yes, you might get lucky and discover some great things,  
>> but
>> it usually involves a lot of aimless wandering, coming back to the
>> same highly-related items again and again, while missing some
>> slightly-more-distantly-related items.
>>
>> Ideally, the user should be able to run a query, retrieve a set of
>> items, sort them however he wants (by author, date, call number, some
>> kind of dynamic clustering algorithm, whatever), and be able to
>> methodically browse from one end of that sort order to the other
>> without any fear of missing something.
>>
>> Keith
>>
>>
>> On Tue, Sep 30, 2008 at 6:08 PM, Stephens, Owen
>> <[log in to unmask]> wrote:
>>> I think we need to understand the
>>> way people use browse to navigate resources if we are to  
>>> successfully
>> bring
>>> the concept of collection browsing to our navigation tools. David
>> suggests
>>> that we should think of a shelf browse as a type of 'show me more
>> like this'
>>> which is definitely one reason to browse - but is it the only  
>>> reason?

Naomi Dushay
[log in to unmask]

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager