@Matt Connolly can you please list the types of joins/aggregation that we are currently performing in the UI and that would benefit from being performed on the server side?
The biggest aggregation being done now starts with the item ID and user ID from a request record and combines metadata for:
the user (name, barcode, patron group name, address)
the item (title, barcode, status, location)
the item's loan record (borrower/user details)
We also have to start with an item barcode and retrieve:
the item record
a loan record for that item
the number of requests (request records) open on the item
If GraphQL pans out, it might alleviate the performance issues without backend work. But if doing this aggregation on the backend wouldn't be too onerous, it's probably worth doing.
@Matt Connolly can you please list the types of joins/aggregation that we are currently performing in the UI and that would benefit from being performed on the server side?
@Niels Erik Nielsen @Jason Skomorowski