ExLibrisGroup / alma-csv-user-load

Load users to Ex Libris Alma from CSV files
2 stars 0 forks source link

User role assignment - Internal Roles #75

Closed SWITCHconsortium closed 2 years ago

SWITCHconsortium commented 2 years ago

Our Automatic Role Assignment rules for imported users are based on Job Category with a default rule to create a Patron role in the absence of a job category. When I loaded a set of internal users with no job category, they were assigned all of the enabled roles. If I make all of the enabled roles inactive, only the patron role is created? Is this perhaps some sort of bug?

I tried adding job category as a field and making the default empty.

mgobat commented 2 years ago

@SWITCHconsortium, I'm unable to replicate that behavior. Can you confirm that my test matches your scenario?

  1. I have 15 roles in my "Automatic Role Assignment Rules" with two Acquisitions roles enabled. One has a "Job Category" parameter of "Acquisitions Manager", the other "Acquisitions Operator".
  2. I have a "Default Rule" that only assigns my "Patron Test" profile (my "Profile 1" in the "Output Parameters" section).
  3. I have an import file with a single user that DOES NOT contain "Job Category" in the list of fields being imported.
  4. After importing the user via the Alma CSV User Load Cloud App, the user has only the "Patron" role associated with the "Patron Test" profile.

Does that somewhat parallel your scenario?

Thanks...

SWITCHconsortium commented 2 years ago

Thanks for following up! You helped me figure out what was wrong – our role assignment rules did not have any parameters! To be fair, we do not assign roles by job category so we have never needed to worry about it being wrong. In any event, problem solved!

Thanks for creating and sharing this Cloud App!

Katie

From: mgobat @.> Sent: Thursday, June 30, 2022 1:42 PM To: ExLibrisGroup/alma-csv-user-load @.> Cc: Katie Utschig @.>; Mention @.> Subject: Re: [ExLibrisGroup/alma-csv-user-load] User role assignment - Internal Roles (Issue #75)

@SWITCHconsortiumhttps://github.com/SWITCHconsortium, I'm unable to replicate that behavior. Can you confirm that my test matches your scenario?

  1. I have 15 roles in my "Automatic Role Assignment Rules" with two Acquisitions roles enabled. One has a "Job Category" parameter of "Acquisitions Manager", the other "Acquisitions Operator".
  2. I have a "Default Rule" that only assigns my "Patron Test" profile (my "Profile 1" in the "Output Parameters" section).
  3. I have an import file with a single user that DOES NOT contain "Job Category" in the list of fields being imported.
  4. After importing the user via the Alma CSV User Load Cloud App, the user has only the "Patron" role associated with the "Patron Test" profile.

Does that somewhat parallel your scenario?

Thanks...

— Reply to this email directly, view it on GitHubhttps://github.com/ExLibrisGroup/alma-csv-user-load/issues/75#issuecomment-1171553806, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUBGRR6O3MIODET3ASJUK33VRXS6TANCNFSM5Z67EKTQ. You are receiving this because you were mentioned.Message ID: @.***>

mgobat commented 2 years ago

@SWITCHconsortium, glad you are back in business. Be on a lookout for an update adding the "Job Description" field soon (#74).

SWITCHconsortium commented 2 years ago

Many thanks!!!

From: mgobat @.> Sent: Thursday, June 30, 2022 3:06 PM To: ExLibrisGroup/alma-csv-user-load @.> Cc: Katie Utschig @.>; Mention @.> Subject: Re: [ExLibrisGroup/alma-csv-user-load] User role assignment - Internal Roles (Issue #75)

@SWITCHconsortiumhttps://github.com/SWITCHconsortium, glad you are back in business. Be on a lookout for an update adding the "Job Description" field soon (#74https://github.com/ExLibrisGroup/alma-csv-user-load/issues/74).

— Reply to this email directly, view it on GitHubhttps://github.com/ExLibrisGroup/alma-csv-user-load/issues/75#issuecomment-1171627083, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUBGRR3LCGVE6E62776TDO3VRX43TANCNFSM5Z67EKTQ. You are receiving this because you were mentioned.Message ID: @.***>