Make this upstream? about koha-plugin-rest-di HOT 15 OPEN

Let's do that. I will talk tomorrow (EEST work daytime Wednesday) with @EreMaijala to figure out who's part where can be.

from koha-plugin-rest-di.

@tomascohen That'd be great. I think some of the functionality may already be possible with x-koha-embed, but a lot isn't. However, I would use the opportunity to streamline some of the code. Particularly the biblio/item availability checks are quite complex. E.g. in most cases it would be enough to get one reason for something being unavailable, but currently you usually get all the ones that apply.

I think it might make sense to document what we really need and is missing from Koha at the moment, then see what's the most sensible way to accomplish that.

from koha-plugin-rest-di.

Yeah, my interest is particularly on adding such classes for checkoutability and holadability and routes for that.

from koha-plugin-rest-di.

I think that one way to proceed would be to describe what endpoints there would be and what they would return. For our use case it's important to be able to retrieve all relevant information for a biblio or an item with a single request. Otherwise there's easily too much overhead on each end.

Most of the logic around availability information is indeed about checkoutability and holadability, but item statuses are important as well, and there can be several relevant ones at the same time (e.g. "Checked out" and "On hold").

Have you already thought about possible routes or would you like me to draft something for a base?

from koha-plugin-rest-di.