[Koha-bugs] [Bug 26170] Create "system" patrons that cannot be (easily) deleted via the web UI

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26170

--- Comment #13 from David Cook <dcook at prosentient.com.au> ---
(In reply to Magnus Enger from comment #12)
> As a start, I'd be happy if we just made it harder to delete some patrons.
> We are seeing some cases where users related to things like SIP2 and SCO get
> deleted, and it would be a big gain if we could just make that happen less
> often. So maybe we could start there and do the other protections later? 

Yeah I'd be happy with that too. I've had some cases where they've changed the
passwords for those users, but the more common scenario has been deleted ones.

> But even "make it hard to delete" could mean different things: 
> - Just a popup saying "are you really sure you want to delete this patron"
> - Make it impossible to delete protected patrons, but make it easy to remove
> the "protected" flag (so an extra step to delete)
> - Make it really hard to remove the "protected" flag and delete the patron

Yeah I was thinking all those could make some sense hehe.

> And we need to think about what happens when someone tries to delete a
> protected patron. A "direct" delete on one patron is probably not too hard,
> but what should happen when a protected patron is included in a batch
> delete? Should the batch delete stop, or should we just report in some way
> that the protected patron was not deleted? Or should we just ignore it?

I've been wondering about that as well. I imagine the batch delete must already
have some capacity for showing errors but I haven't checked.

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.