https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16826
--- Comment #6 from Lari Taskula <[email protected]> --- How about something like this for general/anonymous availability? GET /availability/items?itemnumber=2225 returns for example: [{ "barcode":"TEST000002", "biblioitemnumber":"629", "biblionumber":"629", "checkout": { "available":false, "description":["notforloan","reserved"], "expected_available":null }, "hold_queue_length":1, "holdingbranch":"CPL", "homebranch":"FFL", "itemcallnumber":"782.42166092", "itemnumber":"2225", "local_use": { "available":false, "description":["reserved"], "expected_available":null }, "location":"some_location", "onsite_checkout": { "available":false, "description":["onsite_checkouts_disabled"], "expected_available":null } }] ((+add hold-availability) In this example local_use = checkout with ignoring notforloan, and onsite_checkout = OnSiteCheckouts syspref ? (local_use ? true:false):false) Anyway, what about when checking availability for a specific patron? Is it better to use the same route or use a completely different route? The reason I consider separation between anonymous availability and logged-in availability is my fear that this endpoint will be super busy, and availability for a specific patron is probably a heavy operation. On the other hand, if I used this route, I think I would just want one route with always giving me the correct availability status (checkout, hold, local_use, onsite_checkout etc) for an item, regardless of me being logged-in or not. Opinions are welcome. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
