I have a background job that wakes up every night and screen scrapes my
reading history and lists into a local database, and updates cached
availability information -- so I don't have to worry about the problem that
However, this is not a solution that scales to Minuteman's 600K+
On Tue, Oct 15, 2013 at 9:35 AM, Harper, Cynthia <[log in to unmask]> wrote:
> Perhaps if you exported data from lists that re likely to have items/bibs
> deleted after you have collected them, you could keep an archive of data.
> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
> don warner saklad
> Sent: Friday, October 11, 2013 10:23 AM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] What can be done to stop deleting of records
> belonging to users of our Minuteman Library Network in Massachusetts?
> a) Forensics studies deal with how to retrieve "deleted" "unarchived"
> data. So called "deleted" data is actually available.
> b) Setup the system not to delete records belonging to users. Let users
> keep their information saved for followup. Or at the very least notify
> users beforehand.
> Example. Title wrongfully deleted. Title replaced by 8 places Record
> number, lower case letter with 7 numbers.
> | >"You are logged in
> My Lists > organize130808 ( 29 )
> Mark Title Author Date Added
> [_] Record b2491348 is not available 03-12-2013 [_] Record b2522793 is not
> available 03-12-2013
> [_] Record b2926646 is not available 10-29-2011 [_] Record b2948837 is not
> available 10-25-2011