[Koha-bugs] [Bug 12590] Support deletion of biblio in svc API

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12590

--- Comment #4 from Petter Goksøyr Åsen <boutrosboutrosboutros at gmail.com> ---
You're right Tomás, PUT would be the appropriate HTTP verb to use when updating
a resource. So a better layout of the /svc endpoint could be:

  GET  /svc/biblio/{biblionr}  -> fetch record
  POST /svc/biblio             -> create record
  PUT  /svc/biblio/{biblionr}  -> update record

However, that would be a breaking change for people allready using POST
/svc/new_bib for creating records, and POST /svc/biblio/{biblionr} for updating
records.

Do you know how many actually are using the svc API, and how? Cait mentioned on
IRC they use it for ILL.

Incidentaly, if there is a momentum for expanding Koha's HTTP APIs, I think
Biblibres koha-restfull is a much better basis to build on:
http://git.biblibre.com/biblibre/koha-restful/tree/master

It's well structured, easily extendable, has clean code and tests. I asked
Joubo about their plans for it, and he said they don't plan for it to get
included into Koha master (but they use it themselves and will continue to
maintain it)

IMO it would be an interesting direction for Koha to go if it would expose most
of the functionality through REST APIs, and make the templates use the APIs,
instead of calling functions directly before rendering, or even worse, custom
raw sql queries..
The benefits of this apprach would be:
* More content could be fetched asynchronously (we allready see a push in this
  direction, with recent ajax+datatables enhancements)
* Because of this, pages would load faster (even if not all data is populated
  immideatly) and, more importantly, the browser could cache many of the 
  requests, resulting in less trips to the database.
* I also think that this approach makes sense from an architectural point of
  view, and could lead to better structured and more maintainable code.

-- 
You are receiving this mail because:
You are watching all bug changes.