Anonymous
My feedback
17 results found
-
168 votes
-
24 votes
-
130 votes
-
58 votes
-
11 votes
-
134 votes
-
33 votes
-
29 votes
-
135 votes
An error occurred while saving the comment -
30 votes
-
31 votes
-
272 votes
-
59 votes
-
82 votes
-
47 votes
-
91 votes
-
328 votes
Our library system includes many libraries, some of which are academic libraries, some are public libraries, and some are specialized libraries. Very often the users are users of both the university and, for example, public libraries. For each library to which users are enrolled, there is a Patron type role in Alma with scope that specific library.
As prescribed by the GDPR, the library system must provide for the deletion of user data when users no longer use library services. Therefore, about twice a year, we need to find the users whose data need to be deleted. As for university users (usually students), we need to delete the data of users who are no longer students, for example, because they have graduated. After getting the list of users who are no longer students, we delete via API all the Patron type roles for all the university libraries. We cannot directly delete the data of these users because if a student has also become a user of one of the public libraries, his or her Patron role at that library(s) should not be deleted.
After this deletion of roles via API, we can delete ONLY those users who have no role left.
The fact that it is not possible to delete all of a user's roles via API complicates quite a bit this whole workflow that is already complex, because we need to obtain a list of users without roles.
Thank you
Vera Dean