Hi again, Dave!
In our latest exchange, on 9 July 2021 at 10:36 [JST], you wrote:
No worries. I wish you well with your cloud migration.
>
>
Thank you, David.
The migration is a few months hence, but we're preparing now.
Thanks again.
--
気を付けて。 /ki wo tukete/ = Take care
Hi Charles,
No worries. I wish you well with your cloud migration.
David Cook
Software Engineer
Prosentient Systems
Suite 7.03
6a Glen St
Milsons Point NSW 2061
Australia
Office: 02 9212 0899
Online: 02 8005 0595
From: Charles Kelley
Sent: Friday, 9 July 2021 11:33 AM
To: d
Hi, David!
In our latest exchange, on 9 July 2021 at 9:42 [JST], I received from
you:
Koha uses the "The ever popular do-nothing-approach".
>
> In theory, this is problematic and certainly bothers me, but in practice I
> think it's fairly rare that two staff members are working on the same
>
Hi Charles,
Koha uses the "The ever popular do-nothing-approach".
In theory, this is problematic and certainly bothers me, but in practice I
think it's fairly rare that two staff members are working on the same record at
the same time. Locking and lock timeouts come with a lot of complexity, an
Hi, all!
My library is preparing to migrate our Koha ILSA to the cloud. For
reasons I shan't bore everyone with, I have a question about simultaneous
and concurrent use of records: What happens if two or more parties try to
access a bib. record or patron record at the same time?
In my exp
Amazing!
It worked like a charm.
merci beaucoup Caroline.
On Wed, 30 Jun 2021 at 19:33, Caroline Cyr-La-Rose <
caroline.cyr-la-r...@inlibro.com> wrote:
> Hi Javi,
>
> Sounds like the subfield is missing or hidden in the framework. You can
> check in Administration > MARC bibliographic framework
6 matches
Mail list logo