tication work is not the code,
>> but rather getting community support for moving developments along, so
>> let’s pair up and get some AuthN work done!)
>>
>>
>>
>> David Cook
>>
>> Senior Software Engineer
>>
>> Prosentient Systems
>>
&
Sorry for the delay. I already responded to your points. But here are a few
points from me. Note that a list like this is just like a photograph.
I need help on the following bugs (signoffs):
Without advertizing them, some even very small patches unfortunately may be in
the NSO queue for months.
ving developments along, so
> let’s pair up and get some AuthN work done!)
>
>
>
> David Cook
>
> Senior Software Engineer
>
> Prosentient Systems
>
> Suite 7.03
>
> 6a Glen St
>
> Milsons Point NSW 2061
>
> Australia
>
>
>
> Offic
-devel On Behalf Of
Nick Clemens
Sent: Wednesday, 8 December 2021 11:37 PM
To: Owen Leonard
Cc: koha-devel
Subject: Re: [Koha-devel] My dev list for 22.05
Currently I am working on moving the OverDrive code into a plugin to update for
changes in their API, and to make it easier to adapt in
Currently I am working on moving the OverDrive code into a plugin to update
for changes in their API, and to make it easier to adapt in the future
I hope to continue working this cycle on performance in searching and
loading pages throughout Koha
ByWater at large is going to be working on improvi
> And also, what's on your list for 22.05?
Some larger things I'm working on:
- Upgrading jQuery in the OPAC and staff client. This depends on
upgrading jQueryUI which depends on getting the last of the Flatpickr
patches in.
- Continue to replace jQueryUI widgets with alternatives, starting
with
Bonjour!
Den 03.12.2021 11:00, skrev Paul Poulain:
Hello all,
Regarding this topic : why not also investigate the new data models that
will replace MARC ?
We store the data in original form (marcxml) and move to
biblio/biblioitems a part of the data that is useful for basic operation
(like
El mié, 1 dic 2021 a las 12:24, Jonathan Druart (<
jonathan.dru...@bugs.koha-community.org>) escribió:
> Hello everybody,
>
> I have been listing some tasks I would like to work on during the next
> development cycle.
> I suggest a give and take approach. Help me on one or more of those
> topics a
Hello,
Le 03/12/2021 à 12:03, Arthur a écrit :
Friday's stone in the pond :)
Were you thinking like what is done today for MARC / UNIMARC / NORMAC,
choosing upon installation and then using one model?
nope
Or more as "mixing different data-models in one Koha"?
yes
--
Paul Poulain, Associé
Friday's stone in the pond :)
Were you thinking like what is done today for MARC / UNIMARC / NORMAC,
choosing upon installation and then using one model?
Or more as "mixing different data-models in one Koha"?
That would need a column for storing the data model ID for each record
and somewher
Hello all,
Regarding this topic : why not also investigate the new data models that
will replace MARC ?
We store the data in original form (marcxml) and move to
biblio/biblioitems a part of the data that is useful for basic operation
(like getting the title and the author).
We could import
A first reply on the points you mention. I would like to add a few on my
second reply ;)
> 2. Remove item-level_itype
I agree. Happy to support that one.
> 3. Merge biblio and biblioitem
I understand that you want that. But just feeling that it might be harder
to swallow..
The other points are
Hey Jonathan,
Thanks for reaching out.
We recently did a phpBB to Discourse move that's been live about a week now, so
I'm happy to share my recent knowledge and experience for the
"mailman2discourse" task.
Other than that, I'm not sure how much help I have to give. I have a small
interest i
13 matches
Mail list logo
