[Koha] Update for Demo page
Hi, I’m Jason Boyer with the Equinox Open Library Initiative. I was hoping have our information updated on the Koha Demo server page at https://koha-community.org/demo/ <https://koha-community.org/demo/> . The current information for our demo server is now: MARC Flavor: MARC21 Version: 19.05 OPAC: opac-kohademo.equinoxinitiative.org <http://opac-kohademo.equinoxinitiative.org/> Staff Interface: staff-kohademo.equinoxinitiative.org <http://staff-kohademo.equinoxinitiative.org/> Staff login: demo / demo Provider: Equinox Open Library Initiative (USA) In other words, everything changes except MARC flavor and login. :) Thanks 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 https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Demo page update
I’ve got another update for the Equinox Koha demo server on the demos page at https://koha-community.org/demo/ <https://koha-community.org/demo/> . The server at (opac|staff)-kohademo.equinoxinitiative.org <http://kohademo.equinoxinitiative.org/> is now instead: OPAC: demo.kohacatalog.com Staff: demo-staff.kohacatalog.com <http://demo-staff.kohacatalog.com/> User demo Pass demo Version 19.11 Thanks! 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
Re: [Koha] Staff login problems after upgrading from Koha 3.18 to 19.11
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] Staff login problems after upgrading from Koha 3.18 to 19.11
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
Re: [Koha] Title search works, but Library catalog search fails in OPAC
Hi Tasha, in yaml using a - like that makes the entry part of a list / array of
values.
This is easier to see with a yaml -> json example
analyzer_phrase:
tokenizer: keyword
filter:
- icu_folding
char_filter:
- punctuation
Becomes something like this in json:
{ “analyzer_phrases": { “tokenizer": “keyword” }, “filter”: [“icu_folding”],
“char_filter”: [“punctuation”] }
So adding additional ‘-‘-prefixed entries below filter or char_filter would add
additional entries to those arrays. Just having the bare word punctuation below
char_filter would be a syntax error.
This means that there should be a definition for the punctuation char_filter
*somewhere*, but possibly not in that file.
Jason
--
Jason Boyer
Senior System Administrator
Equinox Open Library Initiative
jbo...@equinoxoli.org
+1 (877) Open-ILS (673-6457)
https://equinoxOLI.org/
> On Jun 24, 2021, at 5:55 PM, Bales (US), Tasha R
> wrote:
>
> Follow-up to my problem searching the OPAC for phrases containing punctuation
> (i.e., Electroactive polymer (EAP) actuators). This Bywater
> Solutions<https://bywatersolutions.com/education/elastic-searching> article
> suggests that the problem is a feature of Elasticsearch.
>
>
>
> FYI, we are using Elasticsearch 6.1.1 on its own dedicated server, and I
> don’t believe we’ve installed the ICU Analysis plug-in (looks like it’s
> required for Zebra, but I can’t tell if it’s required for Elasticsearch),
> which could be a factor. I couldn’t replicate all aspects of my experience
> in a sandbox, although searches for phrases containing punctuation still
> failed in an OPAC “Library Catalog” sandbox search. I concluded that I
> needed to review our configuration.
>
>
>
> I’ve been reviewing the Koha Wiki and elastic.co documentation, and comparing
> to our index_config.yaml.
>
> By chance does anyone know how to interpret the syntax below? The
> documentation describes the parameters below, but I don’t see any usage of
> “-“ before options. Does the option “- punctuation“ mean “yes, remove
> punctuation”, or “no, don’t remove punctuation”, or does the phrase refer to
> some additional configuration file, or perhaps it’s commented out?
>
>
>
> analyzer_phrase:
>
>tokenizer: keyword
>
>filter:
>
> - icu_folding
>
>char_filter:
>
> - punctuation
>
>
>
> Thanks for your time and consideration,
>
>
>
>
>
> Tasha Bales
>
> Business Support Team | Information Services
>
> Enterprise Services | Enterprise Operations, Finance and Sustainability
>
>
>
>
>
> -Original Message-
>
> From: Bales (US), Tasha R
>
> Sent: Tuesday, June 22, 2021 7:54 AM
>
> To: 'Jonathan Druart'
>
> Cc: Discussion Group Koha
>
> Subject: RE: [EXTERNAL] Re: [Koha] Title search works, but Library catalog
> search fails in OPAC
>
>
>
> Jonathan, thank you!
>
>
>
> It does work without the parentheses.
>
>
>
> I would suspect an encoding problem, but for that the problem only manifests
> in the OPAC, and not the intranet.
>
>
>
> I came across this issue while testing after migrating from MariaDB to
> Percona MySQL. Your reply prompted me to check the encoding of the new
> database, and it's unfortunately Latin-1. Since these are parentheses and
> not diacritics, I’m not sure what my expectations should be, but changing to
> UTF-8 is a place to start. Httpd.conf does have UTF-8 set as the default.
>
>
>
> FWIW, my source records were encoded in MARC-8. I used MarcEdit to convert
> them to UTF-8, and it appears that Koha automatically converts anyway on
> import. When I loaded these records into Koha, I used bulkmarcimport.pl on
> the command line.
>
>
>
> I'll ask that the default character set of the database be changed, and see
> if that helps. Thanks again. I'm embarrassed that I didn't think to omit
> the parentheses, or rather was belligerently insisting to myself that they
> should not have been a problem,
>
>
>
>
>
> Tasha Bales
>
> Business Support Team | Information Services Enterprise Services | Enterprise
> Operations, Finance and Sustainability
>
> (480) 509-5415
>
> https://is.web.boeing.com
>
>
>
>
>
> -Original Message-
>
> From: Jonathan Druart [mailto:jonathan.dru...@bugs.koha-community.org]
>
> Sent: Tuesday, June 22, 2021 12:01 AM
>
> To: Bales (US), Tasha R
>
> Cc: Discussion Group Koha
>
> Subject: [EXTERNAL] Re: [Koha] Title sea
[Koha] Update for Demo page on https://koha-community.org/demo/
Hi, can the version for the Equinox Open Library Initiative demo server be updated to 21.05 on the Demo page at https://koha-community.org/demo/ <https://koha-community.org/demo/> ? Thanks Jason -- Jason Boyer Senior System Administrator Equinox Open Library Initiative jbo...@equinoxoli.org +1 (877) Open-ILS (673-6457) https://equinoxOLI.org/ ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Upgrading from 17.05.00.00 to "current"
Hi Steve, koha-common and associated packages won’t be upgraded on regular apt-get (dist-)upgrade. Once your regular OS packages are up to date you can upgrade koha with 'apt-get install koha-common' to install the version pointed to by your koha.list file. I’m not sure what the latest supported version on Jessie is, but you likely should specify a specific version in your koha.list rather than using “current". Jason -- Jason Boyer Senior System Administrator Equinox Open Library Initiative jbo...@equinoxoli.org +1 (877) Open-ILS (673-6457) https://equinoxOLI.org/ > On Sep 14, 2021, at 2:28 PM, Steve Nickerson > wrote: > > Does anyone have any tips on how to successfully go from Koha 17.05 to > anything more current on Debian 8 (Jessie) package install? I've tried the > process I've used in the past and the other OS packages upgrade but Koha > keeps getting "held back" no matter what I've tried (various 'koha.list' > sources, apt-get full-upgrade, apt-get dist-upgrade, etc.). What is the > latest version that will run on Debian 8 and what should I put in my > koha.list source file? > > > > Thanks! > > Steve > > ___ > > 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] More problems with Google security upgrade
Recently Google has started treating all SPF failures as hard failures and throwing away those messages. So, if your notices have a From: of u...@example.com <mailto:u...@example.com> and example.com’s SPF record doesn’t say that you’re allowed to send email from that domain Gmail trashes it. We’ve had a lot of customers lately either add our servers to their SPF records and that fixed the issue for them. You can find out more at http://www.open-spf.org/ <http://www.open-spf.org/> Also setting up DKIM support would make it even more likely that they be delivered, but a properly setup SPF record for all domains email is coming “from” is enough for now. Jason -- Jason Boyer Senior System Administrator Equinox Open Library Initiative jbo...@equinoxoli.org +1 (877) Open-ILS (673-6457) https://equinoxOLI.org/ > On Jun 13, 2022, at 3:43 PM, Tim McMahon wrote: > > We're using our Koha server as the SMTP server, so we're not having the same > problems as I've been reading from others. Our problem is we started having > trouble sending to Gmail accounts. This started around the time people > started posting about their problems sending from Gmail accounts. > > Does anyone know of any changes we'd need to make to our settings to get > Gmail to accept notices from Koha? > > -- > *Tim McMahon* > West Liberty Public Library > ___ > > 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] 500 internal server error - only in one category
Something I've seen recently is accidentally using a category name in sql where it should be a code, for instance setting a user's category code to Adult instead of AD (or whatever is appropriate in your db). If you run this sql in your database and one category code stands out that may help you track it down: select count(borrowernumber), categorycode from borrowers group by 2; Jason -- Jason Boyer Senior System Administrator Equinox Open Library Initiative jbo...@equinoxoli.org +1 (877) Open-ILS (673-6457) https://equinoxOLI.org/ > On Jun 11, 2024, at 1:40 PM, Scott Owen wrote: > > Hi All, > > I just upgraded to Koha > Koha version: 22.05.21.000 > and imported sql data from a older system ( 20.05.15.001 ) > > The catalog looks fine, as well as my "Board" "Staff" and "Teacher" > categories. > > However, whenever I select my "Student" category, and try a search in the > left leaving the "search" blank and just searching for the Student Category > , I get a "Something went wrong loading the table 500 internal Server > error" > > Trying to browse by last names gives the same "500 internal Server error" > error. > > If I try typing in a last name, it seems to work, and will bring up a list > of names. > > I already tried exporting a 2nd DB dump and importing it clean...same issue. > > Any idea where to start ?? It seems like the data is good, it seems like > it's all there. but it's not being sorted / indexed correctly ? > I tried looking in log files, but I really didn't see much . > > -S > ___ > > 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] Problems with the facebook web crawler
While they do ignore robots.txt they do at least supply a recognizable
user agent that you can just block:
RewriteEngine on
RewriteCond %{HTTP_USER_AGENT} "facebookexternalhit|other|bots|here"
RewriteCond %{REQUEST_URI} "!403\.pl" [NC]
RewriteRule "^.*" "-" [F]
Note that second RewriteCond is required or you'll end up with a
redirect loop. They will still be sending you requests but at least
they won't tie up a plack backend doing useless work. I haven't tried
returning 5xx errors to see if that causes them to back off but I doubt
they would take much notice.
Jason
--
Jason Boyer
Senior System Administrator
Equinox Open Library Initiative
jbo...@equinoxoli.org
+1 (877) Open-ILS (673-6457)
https://equinoxOLI.org/ <https://equinoxoli.org/>
On Thu, Jul 25 2024 at 01:45:56 PM +0100, Nigel Titley
wrote:
Dear Michael
On 25/07/2024 13:28, Michael Kuhn wrote:
Hi Nigel
In such a case I would advise to create a sitemap - unfortunately
this Koha feature seems not so well documented, but the following
may give you a start:
* <https://lists.katipo.co.nz/public/koha/2020-November/055401.html>
*
<https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_packages#koha-sitemap>
*
<https://koha-community.org/manual/24.05/en/html/cron_jobs.html#sitemap>
Thanks for this. I'll give it a go and see what happens, although if
Facebook is ignoring the robots.txt file I suspect it will ignore the
sitemap too.
There's been a great deal of annoyance about this on the facebook
developers forums.
I'll let you know how it goes
Nigel
___
Koha mailing list http://koha-community.org
<http://koha-community.org/>
Koha@lists.katipo.co.nz <mailto: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] Update for Demo Servers page on koha-community.org
Hello, can someone update the version for the Equinox demo server on https://koha-community.org/demo/ to 24.05? Thank you! Jason -- Jason Boyer Senior System Administrator Equinox Open Library Initiative jbo...@equinoxoli.org +1 (877) Open-ILS (673-6457) https://equinoxOLI.org/ ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
