On 03/03/2021 09:38, Joonas Kylmälä wrote:
> Downtime, removal of odd maintenance hours and shorter feedback loop are
> the main benefits I see here.
ahah, one more thing I was thinking: I hate to spend time on doing
releases so I wanted to automate so far as just pushing to production
git branch
Hi,
On 03/03/2021 00:47, dc...@prosentient.com.au wrote:
> It seems to me that we would have to train every developer on how to write
> their Perl code and database changes to work with this conceptual model.
Yeah, that's correct if there is DB changes.
> That being said, I am intrigued. I h
I am also skeptical.
It seems to me that we would have to train every developer on how to write
their Perl code and database changes to work with this conceptual model.
That being said, I am intrigued. I hate downtime as much as the next person.
But how do you propose that the Koha community
Hi Magnus,
a slightly different approach I use when I need to filter on $2, below
an example for 084. It has an advantage if you need to add separators
between the fields as the for-each only has the nodes matching your
criteria:
MSC:
q=nlc,phr:
msc
|
Hope that makes sense,
Katrin
Le 02/03/2021 à 16:00, Joonas Kylmälä a écrit :
With rolling upgrade we would first create another
column with the new name and write & read data to both columns during
the 1st step of upgrade, then in 2nd step when all web server nodes are
using latest version we could upgrade again to newer ver
try this :
Le 02/03/2021 à 13:22, Magnus Enger a écrit :
Kia ora!
I want to display most keywords as usual, but with an exception for
those from the 650 field. Specifically, I want to display only those
keywords that has the value "x" or "y" in subfield $2, and hide the
other
Correction: "create another
column with the same name" -> create another
column with the *new* name"
On 02/03/2021 17:00, Joonas Kylmälä wrote:
> Hi,
>
> for example if we rename a DB column in Koha now we need to stop all the
> koha web server instances (or they stop responding because because k
Hi,
for example if we rename a DB column in Koha now we need to stop all the
koha web server instances (or they stop responding because because koha
checks that db revision is correct), do DB upgrade, start all Koha web
server instances. With rolling upgrade we would first create another
column wi
Den 02.03.2021 15:33, skrev Joonas Kylmälä:
Hi,
I opened a bug report for introducing rolling DB upgrade support for
Koha. I would like to hear if you have anything to object to that or
should we just go ahead and develop that? :)
I must confess I am not 100% certain what you mean by rolling u
Hi,
I opened a bug report for introducing rolling DB upgrade support for
Koha. I would like to hear if you have anything to object to that or
should we just go ahead and develop that? :)
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27832
--
Joonas Kylmälä
Tietojärjestelmäasiantunti
Hi Magnus,
Give the following a try:
http://www.loc.gov/MARC21/slim";
xmlns:xsl="http://www.w3.org/1999/XSL/Transform";>
Kia ora!
I want to display most keywords as usual, but with an exception for
those from the 650 field. Specifically, I want to display only those
keywords that has the value "x" or "y" in subfield $2, and hide the
other 650-keywords. Any hints on how to this in XSLT would be infinitely
apprec
12 matches
Mail list logo
