[ List Archives Home ] [ Thread index for 2008 ] [ Date index for 2008 ] [ Author index for 2008 ]


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Our bib and item locations are different as well -- attached record codes
are generally more specific.  I would definitely support an enhancement that
made it clear which codes should be used with bib records and which should
be used with attached records.  It's frustrating to have a system where
there's a difference between the way the system uses bib and attached record
locations and to have no way to indicate which is which in the Branch code
listing.  If you have very many codes at all it's easy to understand when
staff make mistakes on which code to use.

By the way -- I also agree that the correlation between attached record and
bib location codes should automatically happen and, if that's not possible
it should not be a product that must be purchased.  The correlation should
be an integral part of the system.

Debbie Hackleman
Oregon State University
debbie.hackleman@xxxxxxxxxx
-----Original Message-----
From: Claudia Chester [mailto:cchester@xxxxxxxxxx]
Sent: Thursday, December 20, 2001 10:57 AM
To: innopac@xxxxxxxxxx
Subject: Re: Record link maintenance


In addition, at our library the bib location (in our case for branch) is
what displays in extended display and enables users to limit their search
by branch.

What I don't understand is why the bib and item locations weren't
coordinated in the system from the git-go. This should be a feature of the
system, not an expensive extra. While I'm griping, the bib and item
locations should appear in separate lists in the system. The fact that they
pop up in the same menus (like when you're creating an item record) is a
big reason we have so many errors in the first place.

Would anyone support an enhancement request to at least fix the lists?

At 04:06 PM 12/19/2001 -0800, you wrote:
>One answer as to why there are location codes in Bib and also in Item 
>record:  at our library, the bib.
>location is more generic, e.g. sp stands for special collection in Bib and 
>this can have 10-20 specific sub-locations in the Item record, like spovr 
>(sp oversize), spscz (sp Santa Cruz) spphd (sp disserations). The 
>comprehensive bib location code is very useful in functions like Create 
>List, even though it means more maintenance efforts are needed and there 
>may be discrepancies between Bib and Item locations for one bib. record
>
>At 03:23 PM 12/19/01 -0700, you wrote:
>>We are a metro-public library with 6 branches and overflow storage.  We
use
>>Link Maintenance to ensure the Bib record locations match the actual
>>attached Item records.  If we don't run this, we get a lot of Bib records
>>with location codes where there are no attached items anymore (lost or
>>stolen items not replaced, or weeded items), which impacts Create Lists of
>>Bib records by location.  This also supposedly makes the "Limit to Where
an
>>Item is located" function in OPAC searches work more accurately.  I guess
>>the OPAC Search searches the Bib record location codes instead of the Item
>>record location codes.
>>
>>Don't ask me why there are location codes in a Bib record and an Item
>>record, I've never had a satisfactory answer as to why there are Bib
>>location codes and Item location codes too, when they contain the same
>>data.
>>
>>Hope this helps,
>>
>>Ruel J. Eskelsen
>
>Lai-Ying Hsiung

>Electronic Resources/Serials Librarian		
>McHenry Library 				
>University of California, Santa Cruz		
>Santa Cruz, Calif. 95064
>Phone: (831) 459-5166     Fax: (831) 459-2473    lhsiung@xxxxxxxxxx
>
>--
>This message was distributed through the Innovative Users Group INNOPAC
list
>Public replies:  INNOPAC@xxxxxxxxxx
>Update your subscription options:
http://innopacusers.org/list/listinfo/innopac
>
***********************************************************
Claudia Chester
Technical Services Librarian
Fisher Library
John F. Kennedy University
12 Altarinda Rd.
Orinda, CA 94563

phone: 925-258-2362
fax:   925-254-8136
cchester@xxxxxxxxxx
***********************************************************
--
This message was distributed through the Innovative Users Group INNOPAC list
Public replies:  INNOPAC@xxxxxxxxxx
Update your subscription options:
http://innopacusers.org/list/listinfo/innopac