Re: [IUG] Record history feature

["Adam Lenarczyk" <a dot lenarczyk at bn dot org dot pl>]

We have it also and yes, it caused problems - after a few weeeks of running 
it started to crash the client. When you tried to check the history, the 
client was frozen, the crashed with "Contact Innovative" message, then the 
record you tred to check was busied. We made a call from this, it was "given 
to Software Eninering", suprisedly solved in a few days (but we had the 
history only from the date of solving), then crashed again after a few weeks 
and currently is back to SE. The only reason we were told was a "corrupted 
file".
As for patron records - we would like it, too. Asked about the possibility. 
At first we were denied, but asked again and now waiting for reconsidering 
the answer.
Adam Lenarczyk
National Library of Poland
----- Original Message ----- 
From: "Ann Kebabian" <akebabian at colgate dot edu>
To: "IUG INNOPAC List" <innopac at innovativeusers dot org>
Sent: Wednesday, January 20, 2010 12:27 AM
Subject: Re: [IUG] Record history feature


> At Colgate, we've had the record history feature turned on since it was 
> made
> available.
>
> The record history tracking only applies to bibliographic records, and can
> only identify people who have changed a record while logged in to MilCat.
> So, for example, interactive downloads from OCLC cannot be tracked through
> record history because they all go through the same gateway, without any
> login on the III end.  However, batch downloads can be identified, since
> those start at the III end, with a person logged in to the system.
>
>                         Record History for b3168614x
> Action       Initials           Date
> UPDATED ark      January 19 2010 at 18:05
> UPDATED ark      January 19 2010 at 18:05
> UPDATED ark      January 19 2010 at 18:04
> UPDATED twatson  January 04 2010 at 14:31
> CREATED twatson  December 14 2009 at 10:58
>
> A line is added to the record history each time the bibliographic record 
> is
> changed.  In the example above, the last (oldest) line represents the
> batchloading of a set of WorldCat Cataloging Partners records.  I'm not 
> sure
> what happened on Jan. 4, since there's no clue in the record history.  I 
> can
> determine that the order record was not attached then, but that's about 
> it.
> All the Jan. 19 entries represent work I did to the record -- it would 
> have
> registered any 'saves' I made while editing the bibliographic record, as
> well as the linking that occurred when I attached an Item record.
>
> We've found it useful, but not in the way we expected.  I had thought it
> would be useful for training, but it turns out that it's *really* useful
> when we're trying to track down some book that's desperately needed for a
> patron, or reserves, or whatever.  Knowing who last touched it and when
> gives us really good information to track it down.
>
> The record histories are stored separately from the main database and are
> not searchable in any way.
>
> There has been at least one suggestion that this feature be applied to at
> least some other record types in the latest round of enhancements.
>
> Ann Kebabian, Head of Cataloging
> Colgate University Libraries
> 13 Oak Drive, Hamilton, NY 13346
> Phone: 315-228-7309
> Fax:  315-228-7943
> Email: akebabian at colgate dot edu
>
>
>
> >
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
>
> --- StripMime Report -- processed MIME parts ---
> multipart/alternative
>  text/plain (text body -- kept)
>  text/html
> ---
> --
> This message was distributed through the Innovative Users Group INNOPAC 
> list
> Public replies:  INNOPAC at innovativeusers dot org
> Update your subscription options: 
> http://innovativeusers.org/iug-discussion-list 


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.