[Wactclc-alma] User role to edit patron role expiry date

Tue Oct 8 07:38:06 PDT 2019

Wade, BBCC will miss this call. I have an apt. Will read notes.

From: Wactclc-alma <wactclc-alma-bounces at lists.ctc.edu> On Behalf Of Guidry, Wade
Sent: Monday, October 7, 2019 4:39 PM
To: 'WACTCLC Alma Discussion' <wactclc-alma at lists.ctc.edu>
Subject: Re: [Wactclc-alma] User role to edit patron role expiry date

ATTENTION: This email contains links. Please follow best practices before clicking on links
We will discuss this in tomorrow’s call.

There does appear to be a change in behavior recently related to the ‘Patron Registration’ terms of use and the renewal period setting.

Since the issue just started being reported, my guess is that the behavior changed in a recent Alma update.

You actually want to set patron renewal period in terms of use to 1 year (or something greater than 0), rather than no renewal period.

Setting that value to ‘no renewal period’ has the effect of setting the expiration date of the patron role to current day.

(It might be seen as a security tightening effort, to prevent users from being granted library privileges in perpetuity by default.

We will discuss this in tomorrow’s call.

The TLDR is – You probably want to create a renewal period policy that matches how long you would like your internal users to be active by default, and set the default policy accordingly.

Wade Guidry
WACTCLC
Library Consortium Services Manager
wadeg at bigbend.edu<mailto:wadeg at bigbend.edu>
http://www.wactclc.org<http://www.wactclc.org/>
509.760.4474

From: Wactclc-alma [mailto:wactclc-alma-bounces at lists.ctc.edu] On Behalf Of Thomas, Kirsti
Sent: Monday, October 7, 2019 1:51 PM
To: 'WACTCLC Alma Discussion' <wactclc-alma at lists.ctc.edu<mailto:wactclc-alma at lists.ctc.edu>>
Subject: Re: [Wactclc-alma] User role to edit patron role expiry date

ATTENTION: This email contains links. Please follow best practices before clicking on links
After Lesley reported patron roles with Expiry Dates at Pierce, I ran a report to see if we had any in our system and it turned out we did.

While digging into this, I discovered that there was some profile setting thingy buried deep in Alma config that was automatically setting specific Expiry dates on patron roles.   I’m convinced that this setting didn’t exist when we migrated to Alma.

As far as I could figure out, this profile only affected internal users that we create manually.

In Alma config >> Fullfillment >>  Terms of Use and Policies

Filter for Terms of Use Type: User Registration

Check the Default terms of use

It had the Patron Role Renewal Period set as:  1 Year Patron Renewal
And the User Renewal Period set as: 1 Year User Renewal

[cid:image001.png at 01D57DAB.52908420]

I created a new User Registration Terms of Use policy that I called Internal User Registration and set the Patron Role Renewal Period as: No Role Renewal Period (I had to create the No Role Renewal Period on the spot as I was filling in that line).
I set the User Renewal Period as: 1 Year User Renewal

[cid:image002.png at 01D57DAB.52908420]

Then I had to go into Configuration Menu > User Management > Roles and Registration > User Registration Rules to add my new Internal User Registration rule to the table.  See this Alma help page for more info:
https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/050Administration/040Configuring_User_Management/020Roles_and_Registration_Configuration#Configuring_User_Registration_Rules

I *think* having done that, expiry dates aren’t being set on Patron Roles for the new community patron accounts we create any more.

You’ll want to create an Analytics report of user records that have an Expiry Date in the Patron Role.  I put a copy of the report I created here:
/shared/Community/Reports/Consortia/WACTCLC/Seattle/Patron Role has Expiry Date

Unfortunately, it doesn’t look like you can run a job to change Role expiry dates. ☹

It would probably be worth filing a case with Ex Libris to ask why your circraymond account can’t edit the Patron Role Expiry Date when it has “User Manager” permissions.  (Did you remember to log out and log back in after you added the “User Manager” role?)

It will be ok!

Kirsti S. Thomas
Library Technical Services Manager
Seattle Colleges
kirsti.thomas at seattlecolleges.edu<mailto:kirsti.thomas at seattlecolleges.edu>

From: Wactclc-alma <wactclc-alma-bounces at lists.ctc.edu<mailto:wactclc-alma-bounces at lists.ctc.edu>> On Behalf Of Guidry, Wade
Sent: Saturday, October 5, 2019 11:16
To: 'WACTCLC Alma Discussion' <wactclc-alma at lists.ctc.edu<mailto:wactclc-alma at lists.ctc.edu>>
Subject: Re: [Wactclc-alma] User role to edit patron role expiry date

Tammy,

The Alma role required to edit the role expiry date is ‘User Manager’.

Meanwhile, your report sounds identical to the issue Lesley posted about on 9/25.

This may be a case of browser autofill behavior. That is, the browser is auto-filling a field value based on a saved entry in the browser.

But that’s just a guess. You could check to see if auto-fill in the browser being used is enabled, and disable it. (On any kind of shared-use computer, you would want autofill disabled anyway.) Procedure varies by browser. Here’s a page explaining the process for each:

https://www.computerhope.com/issues/ch001377.htm<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.computerhope.com%2Fissues%2Fch001377.htm&data=02%7C01%7C%7Cff7c28dc9f694f39a58108d749c00dbb%7C02d8ff38d7114e31a9156cb5cff788df%7C0%7C0%7C637058961523762368&sdata=ji6orceidhXTXVCsSlTQFopgZTJlLkmk9LrF7W5YwIA%3D&reserved=0>

If / when this happens again to anyone, please leave the record as-is, and let me know. I’d like to take a look at the record.

Wade Guidry
WACTCLC
Library Consortium Services Manager
wadeg at bigbend.edu<mailto:wadeg at bigbend.edu>
http://www.wactclc.org<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.wactclc.org%2F&data=02%7C01%7C%7Cff7c28dc9f694f39a58108d749c00dbb%7C02d8ff38d7114e31a9156cb5cff788df%7C0%7C0%7C637058961523772366&sdata=JDjh50QEEO1GB0BLiAwQEJXbjisIvexrHRuSNU49aZ4%3D&reserved=0>
509.760.4474

From: Wactclc-alma [mailto:wactclc-alma-bounces at lists.ctc.edu] On Behalf Of Tammy Siebenberg
Sent: Friday, October 4, 2019 5:36 PM
To: WACTCLC Alma Discussion <wactclc-alma at lists.ctc.edu<mailto:wactclc-alma at lists.ctc.edu>>
Subject: [Wactclc-alma] User role to edit patron role expiry date

ATTENTION: This email contains links. Please follow best practices before clicking on links
For our circulation desk I have created an internal patron called Raymond Circdesk (ID: circraymond) as the login and have given that user the following roles: Circulation Desk Manager, Circulation Desk Operator, Patron, and Requests Operator.

Today using that computer one of my staff members created a new internal patron for a community member and then tried to check out a book to her.  The book would not check out because there was a problem with the customer’s patron role.  I determined that the patron role has status date of today (which it should be cause it was created today) and an expiry date of today, even though we set the customer’s expiry and purge dates for one year in advance.  Using the circdesk login, we could not edit the patron role to remove the expiry date.

I finally went to my computer with all my admin roles and was able to change the expiry date and check out the book.

I then edited the Raymond Circdesk recorded and added the User Manager role, but when I tested it at the circulation desk, I still could not edit the customer’s patron role.

·         Why did Alma set the patron role expiry date to the date the patron record was created?  I would prefer it left the expiry date blank or, if necessary, set it to the patron’s expiry date.

·         What role do I need to give my circulation desk login so my staff can remove the expiry date from the patron role if this continues to happen?  I don’t remember this problem occurring in the past when we made new internal user records.

Tammy

Tammy R. Siebenberg, MLIS
Director – Library & Media Services
Yakima Valley College
509.574.4984
tsiebenberg at yvcc.edu<mailto:tsiebenberg at yvcc.edu>
yvcc.edu<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fyvcc.edu%2F&data=02%7C01%7C%7Cff7c28dc9f694f39a58108d749c00dbb%7C02d8ff38d7114e31a9156cb5cff788df%7C0%7C0%7C637058961523772366&sdata=PiiOQx88oqUxchCc%2BGXCT8t62l%2F4qcbgE52w%2B9hjCNo%3D&reserved=0>
Hispanic-Serving Institution

CAUTION: This email originated outside of the Seattle Colleges’ email system. Do not click links or open attachments unless you recognize the sender and know the content is safe. Questions? Contact IT Services at x6333 (Central), x3630 (North), x5844 (South) or email ITHelp at seattlecolleges.edu<mailto:ITHelp at seattlecolleges.edu>.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20191008/f32118fb/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 54847 bytes
Desc: image001.png
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20191008/f32118fb/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 58110 bytes
Desc: image002.png
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20191008/f32118fb/attachment-0005.png>