Create a GET API endpoint for circulation transactions
This idea came from a discussion at the IUG2025 Sierra Reporting Forum.
It would be very useful to provide an endpoint to assist with gathering/generating the sorts of circulations statistics that would normally require SQL access. However, the all or nothing nature of SQL permissions is a barrier that prevents many users from being permitted to access those features. With the API on the other hand a user could be limited to simply having read access to an endpoint such as this, along with likely the bib and item endpoints so that they may craft reports without also having to have access to tables that should remain secured.
Jeremy Goldstein
shared this idea
The product team will review this idea for consideration for a future release.
-
Jeremy Goldstein
commented
Oh yes, I agree with Ray's comment fully it would be amazing to have an anonymized form of this data available.
-
Ray Voelker
commented
It would be an amazing resource to have a more "direct" way to retrieve this data on a regular basis for automation and vendor related tasks. It would be nice to have a query parameter to exclude or obfuscate the patron number with this as well.
-
Victor Zuniga
commented
I think this would address the issue of permissions to generate reports for internal or external use (vendors). As Jeremy mentioned, there is no viable way to provide access to the circulation transactions without exposing the entire database. This proposal finds a compromise for this particular scenario.
-
Jesse Phillips
commented
This would be of great use for ease of reporting.