Re: [Koha] Staff login problems after upgrading from Koha 3.18 to 19.11

[Jason Boyer]

Replies inline below

> On May 15, 2020, at 12:48 PM, Quỳnh Vũ Đỗ  wrote:
> 
> Hi,
> 
> 
> Vào Th 6, 15 thg 5, 2020 vào lúc 22:25 Jason Boyer 
> mailto:jbo...@equinoxinitiative.org>> đã viết:
> Hi, this sounds similar to a problem I ran into recently upgrading a 3.20 
> database to 19.11. You’ll probably have to do the drop/re-import procedure at 
> least 2 more times to fix this, but doing this should help:
> 
> By this I understand I should try to do incremental drop/re-import, i.e. once 
> one drop-reimport cycle is successful, I would mysqldump the "upgraded" 19.11 
> database containing the 3.18 values and then drop again the database to 
> reload it with the new dump of the 19.11. Is this interpretation of mine 
> correct?

Not quite. Because an error early on can cause additional failures later, the 
process I’m referring to is this:
1. Load the 3.18 database
2. Try to upgrade it to 19.11, and save all of the output
3. Drop the 19.11 database
4. Load the 3.18 database again
5. Fix the issues from the 19.11 upgrade output
6. Try to upgrade to 19.11 again, saving the output again just in case
7. If there are additional errors at this point, make note of them, then go to 
step 4 and try again, fixing the old issues and these new ones.

When you are able to load the 3.18 database, make a few specific data / 
constraint changes, run the schema upgrade with no errors, then you’re done and 
your database will be in good shape. (This is a great time for a fresh backup 
:-) )

>  
> Instead of using the web interface, after re-importing the 3.18 database use 
> koha-upgrade-schema  at a terminal and capture the output in 
> whatever way is convenient to refer to later. At some point there will most 
> likely be some kind of error that will cause an update to fail, though the 
> upgrade script will continue on. In my case it was an invalid default value 
> for the created_on timestamp (-00-00 :00) on the virtualshelves 
> table, but it could be any number of things depending on past/present mysql 
> versions and data consistency. 
> 
> Collect all of the errors in the koha-upgrade-schema output and find out how 
> to address them, then re-import the 3.18 db once more and fix them before 
> running koha-upgrade-schema. If you need help solving the problems I believe 
> the output of koha-upgrade-schema is safe to post publicly if you’d like to 
> attach a text file or share a link to a paste with the list (but you may want 
> to double-check before doing so).
> 
> 
> Do you think that it would be safe enough to fix values leading to fault by 
> doing phpmyadmin edition directly in tables ? like replacing value 
> "-00-00" by "NULL" for instance?
> 
> Quynh

If you’re more comfortable with phpmyadmin that should be fine. The most 
important thing is to make all of the required changes before starting the 
schema upgrade.

Jason

-- 
Jason Boyer
Senior System Administrator
Equinox Open Library Initiative
phone:  +1 (877) Open-ILS (673-6457)
email:  jbo...@equinoxinitiative.org
web:  https://EquinoxInitiative.org/

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Opac not searchable after upgrading database from Koha 3.18 to 19.11

[Quỳnh Vũ Đỗ]

Hello everyone

After upgrading a Koha database from version 3.18 to 19.11, I was not able
to log in in the staff/administration of Koha as I obtained a "Software
Error" message. However, I was able to get to the OPAC page (at
http://localhost:8000/) but any search returned nothing.
I checked with Phpmyadmin that the biblio table of koha_library was
effectively filled with the data of the 3.18 database (which it was), but
the search of strings that were present returned nothing.

Does someone have encountered that problem and knows the solution?
I am thinking of running in a terminal the command "koha-rebuild-zebra" but
I prefer to listen to some sound advice first.

Thanks for reading
Quynh
=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Staff login problems after upgrading from Koha 3.18 to 19.11

[Quỳnh Vũ Đỗ]

Hi,


Vào Th 6, 15 thg 5, 2020 vào lúc 22:25 Jason Boyer <
jbo...@equinoxinitiative.org> đã viết:

> Hi, this sounds similar to a problem I ran into recently upgrading a 3.20
> database to 19.11. You’ll probably have to do the drop/re-import procedure
> at least 2 more times to fix this, but doing this should help:
>
> By this I understand I should try to do incremental drop/re-import, i.e.
once one drop-reimport cycle is successful, I would mysqldump the
"upgraded" 19.11 database containing the 3.18 values and then drop again
the database to reload it with the new dump of the 19.11. Is this
interpretation of mine correct?



> Instead of using the web interface, after re-importing the 3.18 database
> use koha-upgrade-schema  at a terminal and capture the output
> in whatever way is convenient to refer to later. At some point there will
> most likely be some kind of error that will cause an update to fail, though
> the upgrade script will continue on. In my case it was an invalid default
> value for the created_on timestamp (-00-00 :00) on the
> virtualshelves table, but it could be any number of things depending on
> past/present mysql versions and data consistency.
>
> Collect all of the errors in the koha-upgrade-schema output and find out
> how to address them, then re-import the 3.18 db once more and fix them
> before running koha-upgrade-schema. If you need help solving the problems I
> believe the output of koha-upgrade-schema is safe to post publicly if you’d
> like to attach a text file or share a link to a paste with the list (but
> you may want to double-check before doing so).
>
>
Do you think that it would be safe enough to fix values leading to fault by
doing phpmyadmin edition directly in tables ? like replacing value
"-00-00" by "NULL" for instance?

Quynh
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Staff login problems after upgrading from Koha 3.18 to 19.11

[Jason Boyer]

Hi, this sounds similar to a problem I ran into recently upgrading a 3.20 
database to 19.11. You’ll probably have to do the drop/re-import procedure at 
least 2 more times to fix this, but doing this should help:

Instead of using the web interface, after re-importing the 3.18 database use 
koha-upgrade-schema  at a terminal and capture the output in 
whatever way is convenient to refer to later. At some point there will most 
likely be some kind of error that will cause an update to fail, though the 
upgrade script will continue on. In my case it was an invalid default value for 
the created_on timestamp (-00-00 :00) on the virtualshelves table, but 
it could be any number of things depending on past/present mysql versions and 
data consistency. 

Collect all of the errors in the koha-upgrade-schema output and find out how to 
address them, then re-import the 3.18 db once more and fix them before running 
koha-upgrade-schema. If you need help solving the problems I believe the output 
of koha-upgrade-schema is safe to post publicly if you’d like to attach a text 
file or share a link to a paste with the list (but you may want to double-check 
before doing so).

Jason

-- 
Jason Boyer
Senior System Administrator
Equinox Open Library Initiative
phone:  +1 (877) Open-ILS (673-6457)
email:  jbo...@equinoxinitiative.org
web:  https://EquinoxInitiative.org/

> On May 15, 2020, at 10:55 AM, Quỳnh Vũ Đỗ  wrote:
> 
> Hello everyone,
> Our library has been using a Vietnamized version of Koha 3.18 since mid
> 2014, running on Ubuntu server 14.04 LTS. No upgrade of the system has been
> made since and the server had a hardware problem (mainboard) last February.
> In an attempt to restore the Koha 3.18 database (a dump sql file of 1.8
> Gb), I installed Koha 19.11 on an Ubuntu 16.04.6 LTS Desktop with a LAMP
> stack.
> 
> After consulting with the mailing list yesterday, I followed the steps that
> were indicated, i.e Drop the 19.11 koha_library database, recreate it empty
> and then import the Koha 3.18 database sql dump file.
> Then I went to the staff login page http://localhost:8080 where I was
> welcomed by the login window for the web installation. I followed all the
> steps with success although at the crucial one (starting upgrading from
> 3.18 to 19.11) I had a Server timeout after 10-15 minutes waiting. I
> repeated the start upgrade procedure and was met again with a server
> Timeout. Then I had to go to work.
> 
> At my office, I used the Easykoha Live DVD to install Koha 16.05 along with
> Ubuntu 14.04 LTS on an experimental partition. I then followed the same
> procedure as described a bove to do an upgrade of our Koha 3.18 database
> towards Koha 16.05. This, because the structure between the two database
> versions did not seem too differ too much (only two more tables in the
> 16.05 version). The upgrade from 3.18 to 16.05 was not successful though
> and I had a full web page filled with the errors that were met.
> 
> When I came back home, I had the nice surprise to see that the upgrade from
> 3.18 to 19.11 had succeeded as I was welcomed by this message: "Updating
> database structure: Everything went OK. Update Done" and a blue button
> telling "Continue to log in to Koha". After clicking the button, I had a
> display of "Software error" that said:
> 
> DBIx::Class::Storage::DBI::_dbh_execute(): Unknown column 'me.anonymized'
> in 'field list' at /usr/share/koha/lib/Koha/Objects.pm line 93
> 
> The line 93 (in bold below) is part of a subroutine as follows:
> 
> sub find {
>my ( $self, @pars ) = @_;
> 
>my $object;
> 
>unless (!@pars || none { defined($_) } @pars) {
>*my $result = $self->_resultset()->find(@pars);*
>if ($result) {
>$object = $self->object_class()->_new_from_dbic($result);
>}
>}
> 
>return $object;
> }
> 
> Any hints on how to solve this problem would be greatly appreciated.
> 
> 
> Thanks for your attention and help.
> Quynh
> 
> =
> M. Vũ Đỗ Quỳnh (Ph.D)
> Trường Đại học Thăng Long - Université de Thang Long - Thang Long
> University (Hanoi, Vietnam)
> Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
> internationale - Vice-Rector in charge of International Cooperation
> Web: http://thanglong.edu.vn/
> ___
> 
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] tiny bit of help needed with report

[vikram zadgaonkar]

Hello Lisa,
You may try following:

SELECT YEAR(statistics.datetime) AS Year, MONTH(statistics.datetime) AS
Month, DAY(statistics.datetime) AS Day, HOUR(statistics.datetime) AS Hour,
count(*) AS Checkouts
FROM statistics
left join items on statistics.itemnumber=items.itemnumber
WHERE statistics.datetime BETWEEN <> AND <>
AND statistics.type = 'issue' and items.holdingbranch=<>
GROUP BY Year, Month, Day, Hour
Vikram Zadgaonkar


On Fri, May 15, 2020 at 7:18 PM Lisa Peel  wrote:

> Hello
>
> I apologise for the simplicity of this question but could really use some
> help.
>
> I want to use the Hourly report in the KOHA wiki for ‘Checkouts by Hour in
> Selected Date Range’ as below
>
> SELECT YEAR(statistics.datetime) AS Year, MONTH(statistics.datetime) AS
> Month, DAY(statistics.datetime) AS Day, HOUR(statistics.datetime) AS Hour,
> count(*) AS Checkouts
> FROM statistics
> WHERE statistics.datetime BETWEEN '2014-01-06 13:00:59' AND '2014-01-09
> 16:59:59'
> AND statistics.type = 'issue'
> GROUP BY Year, Month, Day, Hour
>
> However, I also need to add branch code as well so I can determine the
> number of checkouts by library but I am struggling to know what extra code
> to add? My knowledge of SQL is very, very limited and any help would be
> really appreciated
>
> Regards
>
> Lisa
>
> Mrs Lisa Peel
> Head of Learning Resources, SEG Services
> Swiss Education Group
> 
> Avenue des Alpes 62
> CH-1820 Montreux, Switzerland
> Mobile: +41 (0)79 228 0151
> Skype: biblio1897
> www.swisseducation.com
> Facebook | Instagram<
> https://www.instagram.com/swisseducationgroup/> | Linkedin<
> https://www.linkedin.com/company/seg-swiss-education-group>
>
> [http://signature.swisseducation.com/SEG2019.jpg]<
> https://www.swisseducation.com/en/>
>
> Confidentiality and Disclaimer:
> This message contains confidential information and is intended only for
> the individual named.
> Email messages are provided for informational purposes, therefore the
> sender does not accept
> liability for any errors or omissions in the contents of this message.
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Staff login problems after upgrading from Koha 3.18 to 19.11

[Quỳnh Vũ Đỗ]

Hello everyone,
Our library has been using a Vietnamized version of Koha 3.18 since mid
2014, running on Ubuntu server 14.04 LTS. No upgrade of the system has been
made since and the server had a hardware problem (mainboard) last February.
In an attempt to restore the Koha 3.18 database (a dump sql file of 1.8
Gb), I installed Koha 19.11 on an Ubuntu 16.04.6 LTS Desktop with a LAMP
stack.

After consulting with the mailing list yesterday, I followed the steps that
were indicated, i.e Drop the 19.11 koha_library database, recreate it empty
and then import the Koha 3.18 database sql dump file.
Then I went to the staff login page http://localhost:8080 where I was
welcomed by the login window for the web installation. I followed all the
steps with success although at the crucial one (starting upgrading from
3.18 to 19.11) I had a Server timeout after 10-15 minutes waiting. I
repeated the start upgrade procedure and was met again with a server
Timeout. Then I had to go to work.

At my office, I used the Easykoha Live DVD to install Koha 16.05 along with
Ubuntu 14.04 LTS on an experimental partition. I then followed the same
procedure as described a bove to do an upgrade of our Koha 3.18 database
towards Koha 16.05. This, because the structure between the two database
versions did not seem too differ too much (only two more tables in the
16.05 version). The upgrade from 3.18 to 16.05 was not successful though
and I had a full web page filled with the errors that were met.

When I came back home, I had the nice surprise to see that the upgrade from
3.18 to 19.11 had succeeded as I was welcomed by this message: "Updating
database structure: Everything went OK. Update Done" and a blue button
telling "Continue to log in to Koha". After clicking the button, I had a
display of "Software error" that said:

DBIx::Class::Storage::DBI::_dbh_execute(): Unknown column 'me.anonymized'
in 'field list' at /usr/share/koha/lib/Koha/Objects.pm line 93

The line 93 (in bold below) is part of a subroutine as follows:

sub find {
my ( $self, @pars ) = @_;

my $object;

unless (!@pars || none { defined($_) } @pars) {
*my $result = $self->_resultset()->find(@pars);*
if ($result) {
$object = $self->object_class()->_new_from_dbic($result);
}
}

return $object;
}

Any hints on how to solve this problem would be greatly appreciated.


Thanks for your attention and help.
Quynh

=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] tiny bit of help needed with report

[Lisa Peel]

Thanks Rogan, that was perfect!!

Lisa

Mrs Lisa Peel
Head of Learning Resources, SEG Services
Swiss Education Group

Avenue des Alpes 62
CH-1820 Montreux, Switzerland
Mobile: +41 (0)79 228 0151
Skype: biblio1897
www.swisseducation.com
Facebook | 
Instagram | 
Linkedin

[http://signature.swisseducation.com/SEG2019.jpg]

Confidentiality and Disclaimer:
This message contains confidential information and is intended only for the 
individual named.
Email messages are provided for informational purposes, therefore the sender 
does not accept
liability for any errors or omissions in the contents of this message.

From: "rogan.ha...@gmail.com" 
Date: Friday, 15 May 2020 at 16:13
To: Lisa Peel 
Cc: "koha@lists.katipo.co.nz" 
Subject: Re: [Koha] tiny bit of help needed with report

Hi Lisa,

If you're just looking to use the branch column in statistics you can add it to 
your select list and then to the group by.  So the select line would become 
something like this:

SELECT YEAR(statistics.datetime) AS Year, MONTH(statistics.datetime) AS Month, 
DAY(statistics.datetime) AS Day, HOUR(statistics.datetime) AS Hour,
branch, count(*) AS Checkouts
FROM statistics
WHERE statistics.datetime BETWEEN '2014-01-06 13:00:59' AND '2014-01-09 
16:59:59'
AND statistics.type = 'issue'
GROUP BY 1, 2, 3, 4;



On Fri, May 15, 2020 at 9:48 AM Lisa Peel 
mailto:lp...@swisseducation.com>> wrote:
Hello

I apologise for the simplicity of this question but could really use some help.

I want to use the Hourly report in the KOHA wiki for ‘Checkouts by Hour in 
Selected Date Range’ as below

SELECT YEAR(statistics.datetime) AS Year, MONTH(statistics.datetime) AS Month, 
DAY(statistics.datetime) AS Day, HOUR(statistics.datetime) AS Hour,
count(*) AS Checkouts
FROM statistics
WHERE statistics.datetime BETWEEN '2014-01-06 13:00:59' AND '2014-01-09 
16:59:59'
AND statistics.type = 'issue'
GROUP BY Year, Month, Day, Hour

However, I also need to add branch code as well so I can determine the number 
of checkouts by library but I am struggling to know what extra code to add? My 
knowledge of SQL is very, very limited and any help would be really appreciated

Regards

Lisa

Mrs Lisa Peel
Head of Learning Resources, SEG Services
Swiss Education Group

Avenue des Alpes 62
CH-1820 Montreux, Switzerland
Mobile: +41 (0)79 228 0151
Skype: biblio1897
www.swisseducation.com
Facebook | 
Instagram | 
Linkedin

[http://signature.swisseducation.com/SEG2019.jpg]

Confidentiality and Disclaimer:
This message contains confidential information and is intended only for the 
individual named.
Email messages are provided for informational purposes, therefore the sender 
does not accept
liability for any errors or omissions in the contents of this message.
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] tiny bit of help needed with report

[rogan . hamby]

Hi Lisa,

If you're just looking to use the branch column in statistics you can add
it to your select list and then to the group by.  So the select line
would become something like this:

SELECT YEAR(statistics.datetime) AS Year, MONTH(statistics.datetime) AS
Month, DAY(statistics.datetime) AS Day, HOUR(statistics.datetime) AS Hour,
branch, count(*) AS Checkouts
FROM statistics
WHERE statistics.datetime BETWEEN '2014-01-06 13:00:59' AND '2014-01-09
16:59:59'
AND statistics.type = 'issue'
GROUP BY 1, 2, 3, 4;



On Fri, May 15, 2020 at 9:48 AM Lisa Peel  wrote:

> Hello
>
> I apologise for the simplicity of this question but could really use some
> help.
>
> I want to use the Hourly report in the KOHA wiki for ‘Checkouts by Hour in
> Selected Date Range’ as below
>
> SELECT YEAR(statistics.datetime) AS Year, MONTH(statistics.datetime) AS
> Month, DAY(statistics.datetime) AS Day, HOUR(statistics.datetime) AS Hour,
> count(*) AS Checkouts
> FROM statistics
> WHERE statistics.datetime BETWEEN '2014-01-06 13:00:59' AND '2014-01-09
> 16:59:59'
> AND statistics.type = 'issue'
> GROUP BY Year, Month, Day, Hour
>
> However, I also need to add branch code as well so I can determine the
> number of checkouts by library but I am struggling to know what extra code
> to add? My knowledge of SQL is very, very limited and any help would be
> really appreciated
>
> Regards
>
> Lisa
>
> Mrs Lisa Peel
> Head of Learning Resources, SEG Services
> Swiss Education Group
> 
> Avenue des Alpes 62
> CH-1820 Montreux, Switzerland
> Mobile: +41 (0)79 228 0151
> Skype: biblio1897
> www.swisseducation.com
> Facebook | Instagram<
> https://www.instagram.com/swisseducationgroup/> | Linkedin<
> https://www.linkedin.com/company/seg-swiss-education-group>
>
> [http://signature.swisseducation.com/SEG2019.jpg]<
> https://www.swisseducation.com/en/>
>
> Confidentiality and Disclaimer:
> This message contains confidential information and is intended only for
> the individual named.
> Email messages are provided for informational purposes, therefore the
> sender does not accept
> liability for any errors or omissions in the contents of this message.
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] tiny bit of help needed with report

[Lisa Peel]

Hello

I apologise for the simplicity of this question but could really use some help.

I want to use the Hourly report in the KOHA wiki for ‘Checkouts by Hour in 
Selected Date Range’ as below

SELECT YEAR(statistics.datetime) AS Year, MONTH(statistics.datetime) AS Month, 
DAY(statistics.datetime) AS Day, HOUR(statistics.datetime) AS Hour,
count(*) AS Checkouts
FROM statistics
WHERE statistics.datetime BETWEEN '2014-01-06 13:00:59' AND '2014-01-09 
16:59:59'
AND statistics.type = 'issue'
GROUP BY Year, Month, Day, Hour

However, I also need to add branch code as well so I can determine the number 
of checkouts by library but I am struggling to know what extra code to add? My 
knowledge of SQL is very, very limited and any help would be really appreciated

Regards

Lisa

Mrs Lisa Peel
Head of Learning Resources, SEG Services
Swiss Education Group

Avenue des Alpes 62
CH-1820 Montreux, Switzerland
Mobile: +41 (0)79 228 0151
Skype: biblio1897
www.swisseducation.com
Facebook | 
Instagram | 
Linkedin

[http://signature.swisseducation.com/SEG2019.jpg]

Confidentiality and Disclaimer:
This message contains confidential information and is intended only for the 
individual named.
Email messages are provided for informational purposes, therefore the sender 
does not accept
liability for any errors or omissions in the contents of this message.
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] invalid marcxml

[Bernardo Gonzalez Kriegel]

Bug 21708 fix is not available in this case unless the file is changed
manually, or the version upgraded.
It's not included in 18.11.

On Fri, May 15, 2020 at 3:41 AM Marcel de Rooy  wrote:

> When you open and save a record again in Koha having patch 21708, the MARC
> record will be fixed.
> There is no conversion tool. You could open up a new report for that?
> Sponsor its development?
> Running touch_all_biblios will not do the job, as far as I can see.
>
> Op do 14 mei 2020 om 18:27 schreef tuxflow.de :
>
> > Ah, wonderful, very nice. Do existing entries need to be repaired?
> >
> > Or is there a converter? Thanks for the info!
> >
> > Am 14.05.20 um 13:28 schrieb Marcel de Rooy:
> > > Please have a look at bug 21708.
> > >
> > > Op do 14 mei 2020 om 12:52 schreef :
> > >
> > >> Hi Joy,
> > >>
> > >> there is no direct error message from Koha, the error is only in the
> > >> data structure. We only noticed this error because we're sending the
> > >> data to a company so that it can be entered into the Discovery Service
> > >> (search engine). This company pointed us to the wrong data structure.
> We
> > >> need the corrected data to fully set up the Discovery Service.
> > >>
> > >> Koha-Version:   18.11.04.000
> > >>
> > >> greetings,
> > >> tunix
> > >>
> > >> Am 13.05.20 um 19:41 schrieb Joy Nelson:
> > >>> Hello-
> > >>> Can you elaborate a bit more on this?  Is the order of the tags
> causing
> > >>> errors in Koha?  Or is it just 'wrong' per the standard?
> > >>>
> > >>> I am unable to recreate the order you show in your example via the
> > basic
> > >>> editor or the advanced cataloging editor.  Can you explain what your
> > >>> process is that creates this order?  Also what version of Koha are
> you
> > >>> using currently?
> > >>>
> > >>> Thanks
> > >>> joy
> > >>>
> > >>>
> > >>> On Wed, May 13, 2020 at 10:25 AM  wrote:
> > >>>
> >  We have a problem with our MARCXML data in KOHA. The order of the
> > fields
> >  must be changed for many records. The problem affects all records
> that
> >  are newly created or changed by us. All  elements must
> > appear
> >  after the  elements. So far the  element
> with
> >  the unique ID of the record (MARC field 999 $c) is placed before the
> >   elements. The wrong order violates the MARCXML
> > >> guidelines.
> > 
> > 
> >  before editing:
> > 
> >  00996xxx x22002417x 4200
> >  23330
> >  DE-1278
> >  t|
> >  161220s2002 xxu|  00| 0 ger
> >  d
> >  
> >  3-89012-956-0
> >  51,00 
> >  
> > 
> >  after editing:
> > 
> >  01059xxx x2200265x 4200
> >  
> >  9911
> >  9911
> >  
> >  23330
> >  DE-1278
> >  20190604142304.0
> >  t|
> >  161220s2002 xxu|  00| 0 ger
> >  d
> >  
> >  3-89012-956-0
> >  51,00 
> >  
> >  ___
> > 
> >  Koha mailing list  http://koha-community.org
> >  Koha@lists.katipo.co.nz
> >  Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
> > 
> > >>>
> > >>>
> > >>
> > >> --
> > >> tuxflow.de, das andere Hosting!
> > >> ___
> > >>
> > >> Koha mailing list  http://koha-community.org
> > >> Koha@lists.katipo.co.nz
> > >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
> > >>
> > >
> >
> > ___
> >
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
> >
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] invalid marcxml

[Marcel de Rooy]

When you open and save a record again in Koha having patch 21708, the MARC
record will be fixed.
There is no conversion tool. You could open up a new report for that?
Sponsor its development?
Running touch_all_biblios will not do the job, as far as I can see.

Op do 14 mei 2020 om 18:27 schreef tuxflow.de :

> Ah, wonderful, very nice. Do existing entries need to be repaired?
>
> Or is there a converter? Thanks for the info!
>
> Am 14.05.20 um 13:28 schrieb Marcel de Rooy:
> > Please have a look at bug 21708.
> >
> > Op do 14 mei 2020 om 12:52 schreef :
> >
> >> Hi Joy,
> >>
> >> there is no direct error message from Koha, the error is only in the
> >> data structure. We only noticed this error because we're sending the
> >> data to a company so that it can be entered into the Discovery Service
> >> (search engine). This company pointed us to the wrong data structure. We
> >> need the corrected data to fully set up the Discovery Service.
> >>
> >> Koha-Version:   18.11.04.000
> >>
> >> greetings,
> >> tunix
> >>
> >> Am 13.05.20 um 19:41 schrieb Joy Nelson:
> >>> Hello-
> >>> Can you elaborate a bit more on this?  Is the order of the tags causing
> >>> errors in Koha?  Or is it just 'wrong' per the standard?
> >>>
> >>> I am unable to recreate the order you show in your example via the
> basic
> >>> editor or the advanced cataloging editor.  Can you explain what your
> >>> process is that creates this order?  Also what version of Koha are you
> >>> using currently?
> >>>
> >>> Thanks
> >>> joy
> >>>
> >>>
> >>> On Wed, May 13, 2020 at 10:25 AM  wrote:
> >>>
>  We have a problem with our MARCXML data in KOHA. The order of the
> fields
>  must be changed for many records. The problem affects all records that
>  are newly created or changed by us. All  elements must
> appear
>  after the  elements. So far the  element with
>  the unique ID of the record (MARC field 999 $c) is placed before the
>   elements. The wrong order violates the MARCXML
> >> guidelines.
> 
> 
>  before editing:
> 
>  00996xxx x22002417x 4200
>  23330
>  DE-1278
>  t|
>  161220s2002 xxu|  00| 0 ger
>  d
>  
>  3-89012-956-0
>  51,00 
>  
> 
>  after editing:
> 
>  01059xxx x2200265x 4200
>  
>  9911
>  9911
>  
>  23330
>  DE-1278
>  20190604142304.0
>  t|
>  161220s2002 xxu|  00| 0 ger
>  d
>  
>  3-89012-956-0
>  51,00 
>  
>  ___
> 
>  Koha mailing list  http://koha-community.org
>  Koha@lists.katipo.co.nz
>  Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
> 
> >>>
> >>>
> >>
> >> --
> >> tuxflow.de, das andere Hosting!
> >> ___
> >>
> >> Koha mailing list  http://koha-community.org
> >> Koha@lists.katipo.co.nz
> >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
> >>
> >
>
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha