Hi Marcel and Christopher,
maybe to explain this a bit more, Koha will already display all the
information from 260 and 264 in the detail view and result lists,
because in those views the full MARC record is used as the source for
the displayed information.
There are other, brief views,
> Thank you for seeking input from the Koha Community before making this
> decision.
Thanks for responding :)
> If I understand your message correctly, you are saying that if the "Default"
> MARC framework has kohafield mappings which are configured to pull copyright
> date from MARC 260$c
Hi All,
My apologies for late reminder, we have a Developers meeting in IRC
scheduled for today at 22 UTC (in ~1hour)
Local time/date conversion here:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+IRC+Meeting=20170809T22
The agenda is here:
Hi Jonathan,
I have tested the solution from
https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix.
A restart of the MySQL Server with a large Koha Database (several
hundred thousand biblio) or a large number of Koha Sites can take a long
time. This is mainly because the ALTER TABLE
Marcel,
Thank you for clarifying my understanding. It sounds like Koha will
simultaneously pull and display copyright date information from more than
one MARC subfield and that's great. What would happen if a MARC record only
has, for example, a 264$c and no 260$c? Will Koha throw an error if it
> Thank you for clarifying my understanding. It sounds like Koha will
> simultaneously pull and display copyright date information from more than one
> MARC subfield and that's great. What would happen if a MARC record only has,
> for example, a 264$c and no 260$c? Will Koha throw an error if
> As written in it, without an agreement we will find all together, no new
> enhancements are going
> to be pushed.
I am not sure which 'agreement' you are seeking here. The time for a critical
bug to become part of master, just depends on involvement of people and the
publicity made for it
