Hi Waylon,
did you set $KOHA_CONF to /etc/koha/sites//koha-conf.xml ?
All in all, you need $KOHA_CONF $KOHA_HOME $KOHA_PATH and $PERL5LIB, of which
only $KOHA_CONF might differ according to which Koha instance you are working
on at a given moment (if there are > 1 Koha instances on you
How did you modify .env?
Keep those as it:
KOHA_INSTANCE=kohadev
KOHA_CONF=/etc/koha/sites/kohadev/koha-conf.xml
Le jeu. 20 juil. 2023 à 07:19, Waylon Robertson
a écrit :
>
> after doing ktd up, after configuring the database info etc in .env, I am
> getting
> koha-koha-1 | Running
> [P
Furthur on this and reading a bit more into MARC it looks like the
information would go into MARC Field 024 with a source of 8. If there
was a defined Standard Identifier for Openlibrary then the source would
be 7 with the defined Standard Identifier for Openlibrary, but there isn't.
I'm stray
Looks like it's only using the ISBN. The code is in
koha-tmpl/opac-tmpl/bootstrap/js/openlibrary.js
https://gitlab.com/koha-community/Koha/-/blob/master/koha-tmpl/opac-tmpl/bootstrap/js/openlibrary.js#L19
and opac-results:
899 [% IF OpenLibraryCovers
%]KOHA.OpenLibrary.GetCoverFromIsb
Thanks for the response... makes sense to use the ISBN and it explains
the observed behaviour.
I've had a look at the code. One of these days I'll blow the dust off my
JS manuals and see if I can do something to extend the code (JS isn't my
favourite language and I've probably not written any
No idea, I'm really just a programmer ;)
Le ven. 21 juil. 2023 à 14:06, Nigel Titley a écrit :
>
> Thanks for the response... makes sense to use the ISBN and it explains
> the observed behaviour.
>
> I've had a look at the code. One of these days I'll blow the dust off my
> JS manuals and see if
Understood.
I'm sure that a Real Librarian (tm) will answer at some point.
Thanks anyway
Nigel
On 21/07/2023 13:20, Jonathan Druart wrote:
No idea, I'm really just a programmer ;)
Le ven. 21 juil. 2023 à 14:06, Nigel Titley a écrit :
Thanks for the response... makes sense to use the ISBN
yes, turns out, the ktd scripts don't create a proper koha config directory,
so.. ktd can't be used for multiple libraries, and that the koha start script
does setup every time it starts, means it can't be used for a docker image for
production use.need to build koha-koha-1 myself i guess.
Wayl
