Re: [Koha] Bulk patron anonymize/delete tool
Hi Tom, you have to create a patron record to use as anonymous patron. Then you enter the borrowernumber of this user into the system preference AnonymousPatron. http://manual.koha-community.org/3.8/en/administration.html#AnonymousPatron Hope that helps, Katrin -----Ursprüngliche Nachricht----- Von: Tom Hanstra [mailto:tom@nd.edu] Gesendet: Mo 16.04.2012 22:26 An: Fischer, Katrin Betreff: Re: AW: [Koha] Bulk patron anonymize/delete tool We are seeing similar results to what you mention, in that the tool says information is deleted but nothing changes. Your bugzilla post mentions that things work "With an anonymous patron set up correctly". Can you tell me what settings are involved in setting that up "correctly". Because we evidently do not. Thanks, Tom On 04/15/2012 01:20 PM, Fischer, Katrin wrote:
Hi Tom,
I filed a bug a while ago about how the tool reports success, although nothing has happened in the database when the system preference is not configured correctly:
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6756
Could this be the reason for the problems you had using the tool?
Hope that helps,
Katrin
-----Ursprüngliche Nachricht----- Von: koha-bounces@lists.katipo.co.nz im Auftrag von Tom Hanstra Gesendet: Do 12.04.2012 19:48 An: Koha@lists.katipo.co.nz Betreff: [Koha] Bulk patron anonymize/delete tool
I asked this once before and got no response. But hope springs eternal...
Has anyone successfully used the "Patrons (anonymize, bulk-delete)" tool available in Koha? We have found neither to work as expected. It acts as if it *thinks* it is anonymizing and/or deleting but does not actually do it.
Alternately, if that is known not to work, what might it take to bulk delete patrons at the database level? What kind of a mess will I leave behind if I simply delete patrons from the borrowers table? I assume a normal delete would check to make sure the patron does not have outstanding fines, checked out books, etc. Just whacking the borrowers table won't check those things. So what all else do I need to check before deletion?
Thanks, Tom
--
------------------------------------------------------------------------ Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 213 Hesburgh Library Email: tom@nd.edu Notre Dame, IN 46556
"Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" Lewis Carroll - Through the Looking Glass ------------------------------------------------------------------------
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- ------------------------------------------------------------------------ Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 213 Hesburgh Library Email: tom@nd.edu Notre Dame, IN 46556 "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" Lewis Carroll - Through the Looking Glass ------------------------------------------------------------------------
Well, that is what we have been doing. We have such a patron and we run the tool with that patron number in the System Preferences. The tool reports what it thinks should happen, which reflects what we expect to happen. But then, when run, no changes are actually made to the database and re-running the tool again reports that the same changes will be made. If it did what it says it plans to do, we would be fine. It just does not actually make the changes to the database as it says it will. Is there some other login/authentication that happens with the tool which might be failing? Thanks, Tom On 04/16/2012 04:37 PM, Fischer, Katrin wrote:
Hi Tom,
you have to create a patron record to use as anonymous patron. Then you enter the borrowernumber of this user into the system preference AnonymousPatron.
http://manual.koha-community.org/3.8/en/administration.html#AnonymousPatron
Hope that helps,
Katrin
-----Ursprüngliche Nachricht----- Von: Tom Hanstra [mailto:tom@nd.edu] Gesendet: Mo 16.04.2012 22:26 An: Fischer, Katrin Betreff: Re: AW: [Koha] Bulk patron anonymize/delete tool
We are seeing similar results to what you mention, in that the tool says information is deleted but nothing changes.
Your bugzilla post mentions that things work "With an anonymous patron set up correctly". Can you tell me what settings are involved in setting that up "correctly". Because we evidently do not.
Thanks, Tom
On 04/15/2012 01:20 PM, Fischer, Katrin wrote:
Hi Tom,
I filed a bug a while ago about how the tool reports success, although nothing has happened in the database when the system preference is not configured correctly:
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6756
Could this be the reason for the problems you had using the tool?
Hope that helps,
Katrin
-----Ursprüngliche Nachricht----- Von: koha-bounces@lists.katipo.co.nz im Auftrag von Tom Hanstra Gesendet: Do 12.04.2012 19:48 An: Koha@lists.katipo.co.nz Betreff: [Koha] Bulk patron anonymize/delete tool
I asked this once before and got no response. But hope springs
eternal...
Has anyone successfully used the "Patrons (anonymize, bulk-delete)" tool available in Koha? We have found neither to work as expected. It acts as if it *thinks* it is anonymizing and/or deleting but does not actually do it.
Alternately, if that is known not to work, what might it take to bulk delete patrons at the database level? What kind of a mess will I leave behind if I simply delete patrons from the borrowers table? I assume a normal delete would check to make sure the patron does not have outstanding fines, checked out books, etc. Just whacking the borrowers table won't check those things. So what all else do I need to check before deletion?
Thanks, Tom
--
------------------------------------------------------------------------ Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 213 Hesburgh Library Email: tom@nd.edu Notre Dame, IN 46556
"Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" Lewis Carroll - Through the Looking Glass ------------------------------------------------------------------------
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
--
------------------------------------------------------------------------ Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 213 Hesburgh Library Email: tom@nd.edu Notre Dame, IN 46556
"Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" Lewis Carroll - Through the Looking Glass ------------------------------------------------------------------------
-- ------------------------------------------------------------------------ Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 213 Hesburgh Library Email: tom@nd.edu Notre Dame, IN 46556 "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" Lewis Carroll - Through the Looking Glass ------------------------------------------------------------------------
On 17 April 2012 09:04, Tom Hanstra <tom@nd.edu> wrote:
Well, that is what we have been doing. We have such a patron and we run the tool with that patron number in the System Preferences. The tool reports what it thinks should happen, which reflects what we expect to happen. But then, when run, no changes are actually made to the database and re-running the tool again reports that the same changes will be made.
Hi Tom You have the borrowernumber right? Not the cardnumber? (Just checking) Chris
Yes. Good thing to check, but yes, I'm using the borrower number. Tom On 04/16/2012 05:07 PM, Chris Cormack wrote:
On 17 April 2012 09:04, Tom Hanstra<tom@nd.edu> wrote:
Well, that is what we have been doing. We have such a patron and we run the tool with that patron number in the System Preferences. The tool reports what it thinks should happen, which reflects what we expect to happen. But then, when run, no changes are actually made to the database and re-running the tool again reports that the same changes will be made.
Hi Tom
You have the borrowernumber right? Not the cardnumber?
(Just checking)
Chris
-- ------------------------------------------------------------------------ Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 213 Hesburgh Library Email: tom@nd.edu Notre Dame, IN 46556 "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" Lewis Carroll - Through the Looking Glass ------------------------------------------------------------------------
On 17 April 2012 09:19, Tom Hanstra <tom@nd.edu> wrote:
Yes. Good thing to check, but yes, I'm using the borrower number.
Ok I'll try to recreate your issue tonight, just so we are comparing apples with apples, what version are you running? Chris
3.6.4 Thanks! Tom On 04/16/2012 05:18 PM, Chris Cormack wrote:
On 17 April 2012 09:19, Tom Hanstra<tom@nd.edu> wrote:
Yes. Good thing to check, but yes, I'm using the borrower number.
Ok I'll try to recreate your issue tonight, just so we are comparing apples with apples, what version are you running?
Chris
-- ------------------------------------------------------------------------ Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 213 Hesburgh Library Email: tom@nd.edu Notre Dame, IN 46556 "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" Lewis Carroll - Through the Looking Glass ------------------------------------------------------------------------
On 17 April 2012 09:41, Tom Hanstra <tom@nd.edu> wrote:
3.6.4
Thanks!
Tom
Hi Tom So I checked out 3.6.4 set up a borrower to use, and put that borrowernumber (17) into the anonymous patron syspref I then ran the anonymise feature and now select * from old_issues limit 3; +----------------+------------+------------+------------+---------------+------------+-----------------+--------+----------+---------------------+------------+ | borrowernumber | itemnumber | date_due | branchcode | issuingbranch | returndate | lastreneweddate | return | renewals | timestamp | issuedate | +----------------+------------+------------+------------+---------------+------------+-----------------+--------+----------+---------------------+------------+ | 17 | 6 | 2009-01-24 | WORK | NULL | 2009-01-03 | NULL | NULL | NULL | 2012-04-17 19:52:30 | 2009-01-03 | | 17 | 2 | 2008-07-23 | WORK | NULL | 2009-04-19 | NULL | NULL | NULL | 2012-04-17 19:52:30 | 2008-07-02 | | 17 | 4 | 2009-05-10 | OFFICE | NULL | 2009-04-19 | NULL | NULL | NULL | 2012-04-17 19:52:30 | 2009-04-19 | +----------------+------------+------------+------------+---------------+------------+-----------------+--------+----------+---------------------+------------+ They have all been changed to borrower 17, so it seems to be working fine for me I'm not sure what we are doing differently. Chris
What are your other system preference values with regard to Privacy? Perhaps we have a different combination of options in place? We have: Don't Allow AnonSuggestions Keep for EnableOpacSearchHistory Don't allow OPAC Privacy Allow opacreadinghistory Thanks, Tom On 04/17/2012 03:55 AM, Chris Cormack wrote:
On 17 April 2012 09:41, Tom Hanstra<tom@nd.edu> wrote:
3.6.4
Thanks!
Tom Hi Tom
So I checked out 3.6.4 set up a borrower to use, and put that borrowernumber (17) into the anonymous patron syspref
I then ran the anonymise feature and now
select * from old_issues limit 3; +----------------+------------+------------+------------+---------------+------------+-----------------+--------+----------+---------------------+------------+ | borrowernumber | itemnumber | date_due | branchcode | issuingbranch | returndate | lastreneweddate | return | renewals | timestamp | issuedate | +----------------+------------+------------+------------+---------------+------------+-----------------+--------+----------+---------------------+------------+ | 17 | 6 | 2009-01-24 | WORK | NULL | 2009-01-03 | NULL | NULL | NULL | 2012-04-17 19:52:30 | 2009-01-03 | | 17 | 2 | 2008-07-23 | WORK | NULL | 2009-04-19 | NULL | NULL | NULL | 2012-04-17 19:52:30 | 2008-07-02 | | 17 | 4 | 2009-05-10 | OFFICE | NULL | 2009-04-19 | NULL | NULL | NULL | 2012-04-17 19:52:30 | 2009-04-19 | +----------------+------------+------------+------------+---------------+------------+-----------------+--------+----------+---------------------+------------+
They have all been changed to borrower 17, so it seems to be working fine for me
I'm not sure what we are doing differently.
Chris
-- ------------------------------------------------------------------------ Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 213 Hesburgh Library Email: tom@nd.edu Notre Dame, IN 46556 "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" Lewis Carroll - Through the Looking Glass ------------------------------------------------------------------------
OK, I think I found the problem. We have a number of patrons who were created (or somehow set) the privacy setting on their accounts. This was not readily visible and not taken into account when we were trying to perform the anonymizing. Where on the OPAC can a patron set their privacy flag? I've not seen where that option can be set. Thanks, Tom On 04/17/2012 10:16 AM, Tom Hanstra wrote:
What are your other system preference values with regard to Privacy? Perhaps we have a different combination of options in place?
We have: Don't Allow AnonSuggestions Keep for EnableOpacSearchHistory Don't allow OPAC Privacy Allow opacreadinghistory
Thanks, Tom
On 04/17/2012 03:55 AM, Chris Cormack wrote:
On 17 April 2012 09:41, Tom Hanstra<tom@nd.edu> wrote:
3.6.4
Thanks!
Tom Hi Tom
So I checked out 3.6.4 set up a borrower to use, and put that borrowernumber (17) into the anonymous patron syspref
I then ran the anonymise feature and now
select * from old_issues limit 3; +----------------+------------+------------+------------+---------------+------------+-----------------+--------+----------+---------------------+------------+ | borrowernumber | itemnumber | date_due | branchcode | issuingbranch | returndate | lastreneweddate | return | renewals | timestamp | issuedate | +----------------+------------+------------+------------+---------------+------------+-----------------+--------+----------+---------------------+------------+ | 17 | 6 | 2009-01-24 | WORK | NULL | 2009-01-03 | NULL | NULL | NULL | 2012-04-17 19:52:30 | 2009-01-03 | | 17 | 2 | 2008-07-23 | WORK | NULL | 2009-04-19 | NULL | NULL | NULL | 2012-04-17 19:52:30 | 2008-07-02 | | 17 | 4 | 2009-05-10 | OFFICE | NULL | 2009-04-19 | NULL | NULL | NULL | 2012-04-17 19:52:30 | 2009-04-19 | +----------------+------------+------------+------------+---------------+------------+-----------------+--------+----------+---------------------+------------+
They have all been changed to borrower 17, so it seems to be working fine for me
I'm not sure what we are doing differently.
Chris
-- ------------------------------------------------------------------------ Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 213 Hesburgh Library Email: tom@nd.edu Notre Dame, IN 46556 "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" Lewis Carroll - Through the Looking Glass ------------------------------------------------------------------------
On 20 April 2012 06:48, Tom Hanstra <tom@nd.edu> wrote:
OK, I think I found the problem. We have a number of patrons who were created (or somehow set) the privacy setting on their accounts. This was not readily visible and not taken into account when we were trying to perform the anonymizing.
Where on the OPAC can a patron set their privacy flag? I've not seen where that option can be set.
Thanks, Tom
Hi Tom If in systempreferences you have OpacPrivacy switched to allow, then on the opac-user.pl page, the borrower will see a link to my privacy That is where they can change their privacy settings Chris
On 04/17/2012 10:16 AM, Tom Hanstra wrote:
What are your other system preference values with regard to Privacy? Perhaps we have a different combination of options in place?
We have: Don't Allow AnonSuggestions Keep for EnableOpacSearchHistory Don't allow OPAC Privacy Allow opacreadinghistory
Thanks, Tom
On 04/17/2012 03:55 AM, Chris Cormack wrote:
On 17 April 2012 09:41, Tom Hanstra<tom@nd.edu> wrote:
3.6.4
Thanks!
Tom
Hi Tom
So I checked out 3.6.4 set up a borrower to use, and put that borrowernumber (17) into the anonymous patron syspref
I then ran the anonymise feature and now
select * from old_issues limit 3;
+----------------+------------+------------+------------+---------------+------------+-----------------+--------+----------+---------------------+------------+ | borrowernumber | itemnumber | date_due | branchcode | issuingbranch | returndate | lastreneweddate | return | renewals | timestamp | issuedate |
+----------------+------------+------------+------------+---------------+------------+-----------------+--------+----------+---------------------+------------+ | 17 | 6 | 2009-01-24 | WORK | NULL | 2009-01-03 | NULL | NULL | NULL | 2012-04-17 19:52:30 | 2009-01-03 | | 17 | 2 | 2008-07-23 | WORK | NULL | 2009-04-19 | NULL | NULL | NULL | 2012-04-17 19:52:30 | 2008-07-02 | | 17 | 4 | 2009-05-10 | OFFICE | NULL | 2009-04-19 | NULL | NULL | NULL | 2012-04-17 19:52:30 | 2009-04-19 |
+----------------+------------+------------+------------+---------------+------------+-----------------+--------+----------+---------------------+------------+
They have all been changed to borrower 17, so it seems to be working fine for me
I'm not sure what we are doing differently.
Chris
--
------------------------------------------------------------------------ Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 213 Hesburgh Library Email: tom@nd.edu Notre Dame, IN 46556
"Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" Lewis Carroll - Through the Looking Glass ------------------------------------------------------------------------
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
participants (3)
-
Chris Cormack -
Fischer, Katrin -
Tom Hanstra