Hi all,
With regards to
https://issues.folio.org/browse/UIU-1255 - Cate Boerema mentions in a comment that she thinks that part of the buggy behavior is because we are trying to allow both things – manually setting it, and having it controlled by the expiration date. She may be
getting developer feedback in that, I don’t know.
Because we have decided that an expired account should not be allowed to be active (which makes sense, logically) there needs to be some sort of code that connects the two features.
Cate mentions a use case where FOLIO active / inactive controls the ability to log in. I know that Jana has also mentioned that too many password errors flips a user to inactive as well.
So, we have use cases (from this and from
https://wiki.folio.org/display/UM/Active+and+Inactive+Status)
1)
If a user record exists, but they should not be allowed to log in, you would flip the patron to inactive.
a.
Presumably you could also do this by removing all permissions from the record.
b.
This is a manual use case.
2)
If a user tries a bad password too many times, they become inactive.
a.
This is a basic need – if we removed it, it would have to be compensated for somewhere else.
b.
This is an automated use case.
3)
Patron has lost their card, or access to their account needs to be temporarily suspended.
a.
This falls under the category of “temporary suspension of patron privs” as opposed to temporary suspension of operator privs.
b.
This could potentially be handled through user blocks.
c.
This is a manual use case.
-Erin
From: user-mgmt@ole-lists.openlibraryfoundation.org <user-mgmt@ole-lists.openlibraryfoundation.org>
On Behalf Of Björn Muschall
Sent: Tuesday, October 8, 2019 7:21 AM
To: user-mgmt@ole-lists.openlibraryfoundation.org
Subject: Re: Agenda for meeting Oct. 9
Hello, all.
I can't attend tomorrow's meeting due to a Library excursion. Regarding Statistical fields, Leipzig would use Custom fields for that. Regarding Active/Inactive vs. Expiration date I think Active/Inactive should be able to be set manually at any time and Inactive
should also be triggered by Expiration date. An error message that the expiration date must be set (as stated in UIU-1255 screenshots) is not a good option for us.
I am also not able to attend next two meetings due to vacation.
Best, Björn
Am 07.10.2019 um 23:30 schrieb Maura Byrne:
Hello, all.
I’m sticking to my resolution to have an agenda out a full day before our meeting, so here is the proposed agenda:
1. Additional fields. While talking about implementing Users, some RA folks said that there were some things, like Statistical fields, that are essential to our functioning. We were going to use custom fields for that, but I was asked whether other libraries needed Statistical fields. If there were enough of us who needed statistical fields, we could advocate for them as additional fields instead of custom fields. The discussion has begun in Jira ticket UXPROD-1295, and I’d like to have some discussion at our meeting. Wayne Schneider from Index Data will be joining us for this part of the meeting, so I’m putting it first.
2. Patron Notes: We had this on the agenda last week, but we postponed.
3. Active/Inactive vs. Expiration date. Patty has updated UIU-1255. Patty wants to discuss what we think would be the requirements to get this to work the way we want it to.
I hope that we can devote no more than 20 minutes to each item. If we have time left over, we can catch up on some action items that we set in previous weeks.
Maura Byrne
Integrated Library Systems
University of Chicago Library
To unsubscribe from this list please go to http://archives.simplelists.com
--
Björn Muschall
stellv. Bereichsleiter Digitale Dienste
Leiter AG Anwendungsmanagement