We found a few other intranet places as well (thx Katrin). The first comes from
bug 8030, august 2016.
root@master:/usr/share/koha/koha-tmpl/intranet-tmpl/prog# git grep -l "/api/v1/"
[Bug 15496 12-04-19] en/modules/cataloguing/moveitem.tt
[Bug 23710 01-10-19] en/modules/reserve/request.tt
[FIRST
I'm going to go out on a limb and say it will indeed require javascript.
There are a number of OPAC features ( though non-essential ) that don't
function without javascript. Is this still a requirement for the OPAC?
Kyle
---
http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com
for the record:
The mariaDB was on a separate server. We re-internalized the DB in the
Koha VM, and no more problem ! So the problem is not centOS specific
probably.
Le 18/07/2019 à 11:37, Paul Poulain a écrit :
Hello,
We have a library running Koha (17.11) on his own centOS (virtual)
ser
Yeah I guess we reached the point that we just need javascript in OPAC ?
Museumstraat 1
Postbus 74888
1070 DN Amsterdam
Rijksmuseum.nl
Nu te zien:
Louise Bourgeois in de Rijksmuseumtuinen
Operatie Nachtwacht
Verwacht:
Rembrandt-Velázquez. Nederlandse & Spaanse meesters
T/m 18 j
I think it's pretty practical at this point in time to agree that if we are
to continue making a modern web app, we need to require javascript.
---
http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County
Hi, with the HAL introduction in mind I plan to (at least) provide a sample
implementation of the following:
- Add a 'to_api' method to Koha::Object and Koha::Objects that can be
overloaded if needed (trivial, WIP 23770)
- Pick a sample endpoint (probably /cities) and make sure the
implementation
If we decide to require JavaScript for the OPAC we should be careful to
do it in a way that is accessible. Accessibility can even be a legal
requirement in some countries for websites of public institutions like
libraries.
Katrin
On 07.10.19 13:28, Kyle Hall wrote:
I think it's pretty practical
I agree with Katrin. I think we need to be careful to think as developers in
the open source GLAM space rather than the less accountable corporate space.
While I’m a few years out of date when it comes to accessibility, I do still
have some friends who are experts in that area and could get thei
One but not least issue with JavaScript, how do we test this?
I mean it's easy to test the API itself, making requests to it and monitoring
the change in the koha db or mock objects.
It's also easy to check if the Intranet or Opac page returned by the server
contains some strings in the html co
Hi Tomas,
I'd say both parameters shall be sent in the body of the request (just like
when sending a new password using the API).
In that case you could have a parameter called "depth" and a parameter called
"relations" with a json array of keys?
This way the url called doesn't change much and ev
Testing is always an interesting one.
I’d say unit tests for the API functions and unit tests for the controller
functions. You could mock the API for the latter. For integration tests, you
could use selenium to test the integration between the two. Alternatively,
manual integration tests.
Hi all,
How do you (temporarily) turn on DEBUG mode for Koha Plack? I looked inside
and out and nothing I tried seemed to work?
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St
Ultimo, NSW 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
signature.as
12 matches
Mail list logo
