[OPEN-ILS-GENERAL] retrieving deleted records

[Hardy, Elaine]

For PINES libraries, it really isn't practical to search both the local
catalog and OCLC in the Z39.50 interface. Given the size of and problems
with our database, we search the two separately.

I like the configurability of the summary. We would not designate record
ownership. But I could see where other consortium might.

Have better collision detection in the Z39.50 is important for us since we
do not batchload records at this point.

Elaine
 

J. Elaine Hardy
PINES Bibliographic Projects and Metadata Manager
Georgia Public Library Service,
A Unit of the University System of Georgia
1800 Century Place, Suite 150
Atlanta, Ga. 30345-4304
404.235-7128
404.235-7201, fax

ehardy at georgialibraries.org
www.georgialibraries.org
http://www.georgialibraries.org/pines/


-----Original Message-----
From: open-ils-general-bounces at list.georgialibraries.org
[mailto:open-ils-general-bounces at list.georgialibraries.org] On Behalf Of
Jason Etheridge
Sent: Friday, December 17, 2010 11:52 AM
To: Evergreen Discussion Group
Subject: Re: [OPEN-ILS-GENERAL] retrieving deleted records

On Fri, Dec 17, 2010 at 11:35 AM, Hardy, Elaine
<ehardy at georgialibraries.org> wrote:
> Much better display for the record ID. What is meant by record owner?

I'm not sure how far along in development it is, but it's an optional
feature where specific libraries can have ownership of these records.
I'd expect for editing permissions to tie into it, but I'm not sure
what the plan is with OPAC visibility, holdings, etc.

> Can we suppress the Bib call# locally?

Yes.  You can hide or style any of those fields with custom CSS.

> What about record collision detection? Since it is solely on the TCN,
what
> happens if a lib sets the TCN to the record ID?

Collision detection (via Z39.50) is negatively impacted if you use
record id's for TCN.  The batch loader is more configurable.  The
z39.50 client does allow you to search the native Evergreen catalog at
the same time as you search 3rd party Z39.50 servers, however, so
maybe this is mitigated a bit when searching?

> Or is collision detection more robust in later releases?

Not currently for Z39.50.  I'm not sure if anyone is working on improving
that.

--
Jason Etheridge
 | VP, Tactical Development
 | Equinox Software, Inc. / Your Library's Guide to Open Source
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  jason at esilibrary.com
 | web:  http://www.esilibrary.com