[Koha] Zebra reindexing issue
Hello all! After enabling search for non-Roman scripts in our instances, as detailed at https://wiki.koha-community.org/wiki/ICU_chains_configuration, I needed to rebuild the index. Our production and test systems run Koha 22.05.10 on Debian 11. As the process was running, the following message was displayed 6 times: "Use of uninitialized value $sub6 in pattern match (m//) at /usr/share/koha/lib/Koha/Filter/MARC/Index880InZebra.pm line 77." - What does this indicate? (I mean, beyond the obvious.) - Is it something that we should track down and correct? - How can we identify the bibliographic records that trigger the notice? There are no log entries that I can find with details about the records causing the message. Thank you in advance for your attention and help! David Liddle IT Manager david.lid...@wycliff.de (just not for this list) Wycliff e.V., https://wycliff.de Seminar für Sprache und Kultur, https://spracheundkultur.org Internationales Tagungszentrum Karimu, https://karimu.de ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Linking bibliographic records to the Wikipedia
Dear list, We are using Koha 21.05.19 and using JS to link 1xx fields in the bibliographic records to the Wikipedia relevant authors entry. We are cataloging in different scripts, e.g. Armenian books in Armenian (1xx is in Armenian), books in Cyrillic in Cyrillic script (e.g. 1xx is in Cyrillic), Persian books also are cataloged (e.g. 1xx is in Farsi), and Latin. Depending on the 1xx script (in each bibl. record only one script is present for 1xx), when pressing in Koha on Wikipedia icon next to the authors name we will be happy to be redirected to the different Wikipedia repositories, e.g. - for Armenian authors to be redirected to the hy.wikipedia.org - for Russian authors to be redirected to the ru.wikipedia.org - for English authors to be redirected to the en.wikipedia.org etc How to solve this problem? many thanks, Erlanda ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Koha Out of Memory
Hi everyone,
I have an issue with the db-dumps created by Koha into the /var/spool/koha
{instance name} . It finishes my memory. I was wondering whether running a
CRON tab to auto delete these files will cause any harm. We run our own
backups every 24 hours, thus we do not need these files. And does the
database depend on these caches and dumps?
Our koha is used to preserve African indigenous literature, and
pre-colonial publications from the museum.
Thank you so much in advance.
Sincerely,
Russel Shihepo
Notitia Systems cc
Namibia - Africa
+264813223143
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha Out of Memory
Memory and storage are not the same thing. The error sounds like a memory
issue, but deleting the files would only help for storage.
Where I am, the Koha server runs as a VM, and we backup the entire VM
nightly, so we are in a similar place regarding separate backups. However,
these files can sometimes still be useful as a way to speed up recovery
times. IIRC, there is a parameter somewhere, perhaps as an argument to the
cron script, that tells it how many of these history files to keep. You
might try reducing the number down to just 1 or 2, which is what we did.
*Joel Coehoorn*
Director of Information Technology
*York University*
Office: 402-363-5603 | jcoeho...@york.edu | york.edu
On Wed, Mar 22, 2023 at 8:39 AM Russel G. P. Shihepo
wrote:
> Hi everyone,
>
> I have an issue with the db-dumps created by Koha into the /var/spool/koha
> {instance name} . It finishes my memory. I was wondering whether running a
> CRON tab to auto delete these files will cause any harm. We run our own
> backups every 24 hours, thus we do not need these files. And does the
> database depend on these caches and dumps?
>
> Our koha is used to preserve African indigenous literature, and
> pre-colonial publications from the museum.
>
> Thank you so much in advance.
>
> Sincerely,
> Russel Shihepo
> Notitia Systems cc
> Namibia - Africa
> +264813223143
> ___
>
> 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] Linking bibliographic records to the Wikipedia
Hi Erlanda,
You could customize your JS to 1) detect which script is being used on the
record and 2) adjust the Wikipedia domain accordingly. Language is in the
041 MARC field https://www.oclc.org/bibformats/en/0xx/041.html but you need
to have that field or else there's no straightforward way, from looking at
a record, to know what language it's in.
Then your JS would be adjusted roughly like this (not knowing what it
currently looks like):
// map of language names to Wikipedia subdomains
// I think the 041 will always display in English? But you would want to
check
const map = { 'Armenian': 'hy', 'English': 'eng', 'Russian': 'ru'}
const lang = $('.language span[class^="lang_code]').text()
const wsubdomain = map[lang]
Then where you link to Wikipedia, use the variable wsubdomain, e.g.
`${wsubdomain}.wikipedia.org/...`.
Interesting customization! Both the Wikipedia link and the fact that it's
multilingual.
Best,
ERIC PHETTEPLACE Systems Librarian, Libraries (he/him)
ephettepl...@cca.edu
*CCA is situated on the traditional unceded lands of the **Chochenyo and
Ramaytush Ohlone** peoples.*
Black-owned bookstores in Oakland: Ashay by the Bay
[Koha] Modifying Koha for a citation database, or, Hey folks, try this at home!
Esteemed Colleagues, Some of you may be familiar with the MedStar Authors catalog, a Koha instance where I took citations from Medline, the database of medical journal citations run by the US National Library of Medicine and converted them to a format that could be seen and searched in Koha. I was new to Koha when I designed it, I didn't know what I was doing, and there were a lot of rough edges I wanted to polish in a future version. After much longer than I thought it would take, it's now available at http://www.medstarauthors.org. So who would want to set up a Koha instance of local authors from Medline citations other than me? >crickets< Thought so. However, doing this project involved: Deciding which Medline fields I wanted for the Authors Catalog. Converting Medline citations in Reference Manager format to MARC records. Adding new, non-standard MARC fields to the Koha framework. Editing the OpacResults and OpacDetail xsl files to display the fields I wanted. There are a lot more than in the standard OpacDetail xsl! Adding the new fields to Elasticsearch, and assigning them to indexes so they're searchable. Editing masthead.inc to add more basic search options. (Institution 651$a, Department 656$a, etc.) Editing opac-advsearch.tt to add more search options, and (when you click on "more options") even more search options. Editing opac-facets.inc to modify the left column in the detail view. Making it possible (and easy!) to add PDFs and other files to the Koha server itself. Adding a page to the News function so I can display links to most of the files I've mentioned so far. (needs 22.11) Putting a lot of data into a spreadsheet to keep track of what field is associated with what MARC tag, Elasticsearch index, etc. Anyone working on, and being frustrated by, any of the above? Then you may find some of what I've done worth harvesting, at least to look at to see what I've done. It isn't necessarily pretty--XSLT programmers might need their fainting couches--but it works. At least for this installation. Unfortunately, the site is blocked in some places outside the US, possibly in the EU because our IS department hasn't vetted it for GDPR compliance. (Thanks to David for suggesting the reason.) I think I can put the page with the files on a different server without running afoul of GDPR; I'll do it if anyone's interested. --Fred Fred King, MSLS, AHIP Medical Librarian, MedStar Washington Hospital Center fred.k...@medstar.net 202-877-6670 ORCID -0001-5266-0279 MedStar Authors Catalog: http://medstarauthors.org You know it's cold outside when you go outside and it's cold. --NPS Twitter -- MedStar Health is a not-for-profit, integrated healthcare delivery system, the largest in Maryland and the Washington, D.C., region. Nationally recognized for clinical quality in heart, orthopedics, cancer and GI. IMPORTANT: This e-mail (including any attachments) may contain information that is private, confidential, or protected by attorney-client or other privilege. If you received this e-mail in error, please delete it from your system without copying it and notify sender by reply e-mail, so that our records can be corrected... Thank you. Help conserve valuable resources - only print this email if necessary. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] [koha-US Mailing List] Modifying Koha for a citation database, or, Hey folks, try this at home!
Fred was not alone--and congratulations to him for getting this operational, taking it to levels and adding details that make this an incredibly useful resource! *[optional reading below!]* I did something incredibly similar at my old job, continuing a resource that I had developed as a "proof of concept" within Millennium and transitioning it to a "proof of concept" within Koha. Under both, it was called "Faculty Scholarship". I gave a presentation on it at the Ohio Valley Group of Technical Services Librarians in 2018 (*holy cow that was a long time ago now * https://wayback.archive-it.org/11102/20180927174532/https://events.library.nd.edu/ovgtsl2018/talk/sterbenz.shtml ) The big difference between the two implementations (as I did them) was in how they were kept. Millennium only supported one database, so location scoping was used. In Koha, it ran in its own database and under its own ports (both public and staff side), but also supported its own style sheets for the WebPAC (and bibliographic frameworks, too). For the record, both efforts died on the vine and never moved any further than what was reported in the 2018 presentation. My departure in 2020 would have killed it anyway, so I'm glad I didn't spend the considerable effort it would have taken to keep it going. As an unsupported site (like Fred), I just went ahead and "did things", not needing to work with anyone except myself on making the changes I needed to the system architecture. John _ John E. Sterbenz, Jr. *Executive Director* *DALNET - Detroit Area Library Network* Wayne State University 5150 Anthony Wayne Drive Detroit, MI 48202 +1 (313) 577-6789 http://www.dalnet.org On Wed, Mar 22, 2023 at 2:12 PM King, Fred wrote: > Esteemed Colleagues, > > > > Some of you may be familiar with the MedStar Authors catalog, a Koha > instance where I took citations from Medline, the database of medical > journal citations run by the US National Library of Medicine and converted > them to a format that could be seen and searched in Koha. I was new to Koha > when I designed it, I didn’t know what I was doing, and there were a lot of > rough edges I wanted to polish in a future version. After much longer than > I thought it would take, it's now available at > http://www.medstarauthors.org. > > > > So who would want to set up a Koha instance of local authors from Medline > citations other than me? > > > > >crickets< > > > > Thought so. However, doing this project involved: > > > > Deciding which Medline fields I wanted for the Authors Catalog. > > Converting Medline citations in Reference Manager format to MARC records. > > Adding new, non-standard MARC fields to the Koha framework. > > Editing the OpacResults and OpacDetail xsl files to display the fields I > wanted. There are a lot more than in the standard OpacDetail xsl! > > Adding the new fields to Elasticsearch, and assigning them to indexes so > they're searchable. > > Editing masthead.inc to add more basic search options. (Institution 651$a, > Department 656$a, etc.) > > Editing opac-advsearch.tt to add more search options, and (when you click > on "more options") even more search options. > > Editing opac-facets.inc to modify the left column in the detail view. > > Making it possible (and easy!) to add PDFs and other files to the Koha > server itself. > > Adding a page to the News function so I can display links to most of the > files I've mentioned so far. (needs 22.11) > > Putting a lot of data into a spreadsheet to keep track of what field is > associated with what MARC tag, Elasticsearch index, etc. > > > > Anyone working on, and being frustrated by, any of the above? Then you may > find some of what I've done worth harvesting, at least to look at to see > what I've done. It isn't necessarily pretty--XSLT programmers might need > their fainting couches--but it works. At least for this installation. > > > > Unfortunately, the site is blocked in some places outside the US, possibly > in the EU because our IS department hasn't vetted it for GDPR compliance. > (Thanks to David for suggesting the reason.) I think I can put the page > with the files on a different server without running afoul of GDPR; I'll do > it if anyone's interested. > > > > --Fred > > > > Fred King, MSLS, AHIP > > Medical Librarian, MedStar Washington Hospital Center > > fred.k...@medstar.net > > 202-877-6670 > > ORCID -0001-5266-0279 > > MedStar Authors Catalog: http://medstarauthors.org > > > > You know it's cold outside when you go outside and it's cold. > > --NPS Twitter > > > -- > MedStar Health is a not-for-profit, integrated healthcare delivery system, > the largest in Maryland and the Washington, D.C., region. Nationally > recognized for clinical quality in heart, orthopedics, cancer and GI. > > > IMPORTANT: This e-mail (including any attachments) may contain information > that is private, confidential, or protected by attorney-
Re: [Koha] Koha mysql DBMS fix
You need to add a line to one of mysql's configuration files, you may create one just for this, the complete file would look like: [mysqld] init-file = /var/lib/mysql/init-file_library.sql you may change "library" with your own libraries name. And you must create that file, with the sql from the wiki. from the error message, my guess is your sysadmin put this line outside the scope of a [mysqld] section. [mysql] is not good enough, as it refers to mysql's CLIENT program, not your database server. On 3/21/23 20:59, Decka David wrote: Dear Koha Community, Here is a problem that someone here in this community might come across or know to share how to solve this problem; I talked with my ICT administrator to solve this issue to have access to the koha mysql but was unable to do so to fix the DBMS auto increment problem. The issue of the "unknown variable" in the script is; *mysql: [ERROR] unknown variable 'init-file=/var/lib/mysql/init-file_koha_library.sql'* I can do the mysqldump and run the backup on the test server but on the production server, I have no access at all. Looking into the past forum emails, wikis there is not much help. Thanking everyone here in advance for their invaluable insight and pointing me towards solving the problem. Kind regards *Decka David* Matheson Librarian | PNG University of Technology | PMB | Lae, 411 | Morobe Province | PAPUA NEW GUINEA Alternate E: decka.da...@gmail.com | P: 657 4734353 <%28657%29%20473-4353> | F: 675 4374363 ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha -- Hector Gonzalez ca...@genac.org ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Zebra reindexing issue
Hi David, Firstly, /usr/share/koha/lib/Koha/Filter/MARC/Index880InZebra.pm has been removed from the Koha master branch and Koha 22.11.x as it was superseded by BZ 31532. It should've been removed from Koha 22.05.x as well, but it looks like it wasn't. That's an oversight. I'll ask the 22.05.x maintainer to look at that. That error message means that you have 6 bad 880 entries though. To find those records, look through https://wiki.koha-community.org/wiki/SQL_Reports_Library for examples to "Query MARC". You'll want to use the ExtractValue function to use Xpath to query the MARCXML to find the problematic entries. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -Original Message- Date: Wed, 22 Mar 2023 12:13:19 +0100 From: David Liddle To: koha Subject: [Koha] Zebra reindexing issue Message-ID: Content-Type: text/plain; charset="UTF-8" Hello all! After enabling search for non-Roman scripts in our instances, as detailed at https://wiki.koha-community.org/wiki/ICU_chains_configuration, I needed to rebuild the index. Our production and test systems run Koha 22.05.10 on Debian 11. As the process was running, the following message was displayed 6 times: "Use of uninitialized value $sub6 in pattern match (m//) at /usr/share/koha/lib/Koha/Filter/MARC/Index880InZebra.pm line 77." - What does this indicate? (I mean, beyond the obvious.) - Is it something that we should track down and correct? - How can we identify the bibliographic records that trigger the notice? There are no log entries that I can find with details about the records causing the message. Thank you in advance for your attention and help! David Liddle IT Manager david.lid...@wycliff.de (just not for this list) Wycliff e.V., https://wycliff.de Seminar für Sprache und Kultur, https://spracheundkultur.org Internationales Tagungszentrum Karimu, https://karimu.de ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Uploading files
I successfully uploaded a file in tag 856$u but when I checked it out in OPAC, I'm getting Error 404 (Sorry, the requested page is not available). I already choose "upload.pl" in plugin in the bibliographic framework. What should I do? Thanks. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
