Create RestAPI with a Patron Validate role that updates the “last circ activity date” in patron record
Our library wants to provide the patron validate role to our vendors.
But, we do not want to give the vendors any read or write roles.
We do this now with several vendors, but the authentication does not update the "last circ activity" field in the patron record.
Is it possible to add a new permission that would only allow authentication but update the "last circ activity" field in the patron record.
Why add this feature?
Our library purges patron that don't circulate for X number of years. We don't want to delete patrons that are actively using our eVendor content.
We want to give our eVendors as little read/write permissions as possible.
Thank you.
Elizabeth Wright
shared this idea
-
Nicole Castellano
commented
Not just as a librarian, but as a patron who is mostly/solely and online-only user, it would be beneficial to have my circ activity updated so that I wouldn't lose all of my data (including my reading history) if my card is accidentally purged.
-
Nicole Turzillo
commented
Our consortium's policy includes purging patron records with no circulation activity over a specified period. Given that several vendors use the REST API to authenticate patrons, and many libraries have patrons who primarily use online services, there is a need for the Patron Validate process to update the CIRCACTIVE field. This would ensure that these online-only users are correctly identified as active.
-
AdminAlex Vancina
(Admin, Innovative)
commented
Could this be accomplished by adding a new parameter to the existing /patrons/validate endpoint? For example:
PatronValidation {
barcode (string): User barcode,
pin (string): User PIN,
caseSensitivity (boolean, optional): Case sensitivity,
updateCircActive (boolean, optional): Update last circ activity
}