- Koha - lists.katipo.co.nz

koha-US October 2024 Events & Meetings
by Kristi Krueger 23 Sep '24

23 Sep '24

Hello! koha-US online meetings and events are free and open to all. See our calendar for a full list: http://koha-us.org/calendar/. For Google Calendar users, add our events calendar to your list for easy access to meeting times and links: https://calendar.google.com/calendar/u/1?cid=a29oYS11cy5vcmdfZG1xb2pkczE5Zn… *Meetings* General Meeting - Wednesday, October 02 @ 8:30a PT / 11:30a ET / 15:30 UTC Board Meeting - Wednesday, October 09 @ 8:30a PT / 11:30a ET / 15:30 UTC *Special Interest Groups* Cataloging - Thursday, October 03 @ 8:00a PT / 11:00a ET / 15:00 UTC System Administration - Tuesday, October 08 @ 8:00a PT / 11:00a ET / 15:00 UTC *** Note the new time for the Circulation SIG: 4th Wednesday of the month*** Circulation - *Wednesday, October 23* @ 10:30 PT / 1:30 ET / 17:30 UTC Acquisitions - Tuesday, October 15 @ 9:00a PT / 12:00p ET / 16:00 UTC Web Development - Thursday, October 17 @ 10:00a PT / 1:00p ET / 17:00 UTC Consortia - Thursday, October 24 @ 9:00a PT / 12:00p ET / 16:00 UTC Visit http://koha-us.org/special-interest-groups/ to learn more and sign up for topic-specific mailing lists. Most meetings and events are recorded and made available at https://www.youtube.com/kohaus Kristi Krueger koha-US Secretary secretary(a)koha-US.org

1 0

Reindex ElasticSearch
by Marcos René Álvarez Moreno 21 Sep '24

21 Sep '24

Hi. Two questions: 1) Is it possible to index only one updated record in the Koha DB with elasticsearch? 2) can elasticsearch index only an updated document already defined in the elastic index? greetings -- Mtro. Marcos Rene Álvarez Moreno Departamento de Producción Subdirección de Informática Dirección General de Bibliotecas y Servicios Digitales de Información Universidad Nacional Autónoma de México Tels. (+52 55) 5622 1650, (+52 55) 5622 1606 mralvarezm(a)dgb.unam.mx

2 1

Documentation - Automated screenshots can still be the way to go!
by Charillon, Aude 20 Sep '24

20 Sep '24

Hello, I know some lucky people are on their way to KohaCon - but for the rest of us, it's just any other Friday! And now sounds as good a time as any for the Documentation team to share an update on the automated screenshots project. Read on for more information - and a cute animal as a reward! ### Automated what? A year and a half ago, the Documentation team and Jonathan Druart started looking into the possibility to automate the update of the screenshots used in the Koha Manual. The benefits would be: - a more up-to-date Manual for library teams. Currently, among our 1,600+ screenshots we still have many from pre-22.11 Koha (before the staff interface became green); - a gain of time for the Documentation team; - the possibility to have screenshots in the language of the Manual. Currently, the text of the Manual is translated but the screenshots are the same, making them less useful for librarians who don't speak English. ### What's happened so far Skip this section if you're not interested in the full project history! Spring 2023: Jonathan Druart starts looking at (new) ways to automate updating screenshots - see bug 24076 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34076 August 2023: Jonathan presents his work so far at KohaCon23 (talk recording https://youtu.be/16uDrqulL5E) September 2023: Caroline Cyr La Rose emails this list to ask for help with analysing screenshots (https://lists.katipo.co.nz/pipermail/koha/2023-September/060003.html) We wanted to find out what steps are needed in Koha before the screenshot can be taken - information which the scripts that generate screenshots need. Big thanks to everyone who helped! We analysed 187 images over the next few months. April 2024: at the Marseille Hackfest, Jonathan presents the new website he created for the Documentation team to analyse screenshots. The website allows him to more easily create scripts to generate the screenshots. The Documentation team can check on the website what the generated screenshots look like. Today: I am writing again asking for help to analyse more screenshots! ### Next steps We have been experimenting, but we still need to experiment more before we can go ahead and use automatically-generated screenshots in the manual. We have been targeting screenshots that would be easy to generate automatically. We need more of those to be analysed - and we need your help! If you are interested in participating, please read the guidelines on how to analyse screenshots at: https://link.infini.fr/_Nzb3p-w The steps summarised: - Make sure you have a login to Jonathan's website (request one if not). - Pick a screenshot to analyse. - Find on your Koha system what the screenshot shows. - Add the details (page, element selector, workflow) to the screenshot page on Jonathan's website. - Assess the difficulty, as explained in the guidelines. - Save. Pick another screenshot to analyse! If you have any questions, please feel free to contact me - either by email or, even better, on the Koha community Mattermost chat. You can also drop a line in the Mattermost Documentation channel :-) If there is interest, we could organise an online workshop to get started with analysing screenshots together. Thanks, Aude On behalf of the Koha Documentation team ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡠⠔⠚⠋⢉⣉⣉⣍⣉⠉⠙⠒⠦⢄⡀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡠⠊⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣀⠤⠖⠛⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⡰⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢠⠞⠁⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢰⠃⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⢰⠚⠓⡎⠑⢦⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠸⡤⠚⡇⠀⠈⣧⣼⡄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠳⣄⠀⠀⠀⠀⠀⠀ ⠀⢀⠎⠀⠀⠀⠀⠀⠈⠀⠙⣄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠈⠓⢄⠀⠀⠀⠀ ⠀⢸⠀⠠⣶⡄⠀⠀⠀⠀⠀⠈⠉⠉⠒⠢⢤⣀⠀⠀⠀⠀⠀⠀⠀⠑⣄⠀⠀ ⠀⡿⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠢⢄⠈⠓⢄⠀⠀⠀⠀⠀⠀⠈⣆⠀ ⠀⢿⣤⡀⣀⣤⣀⡤⠀⠀⠀⠀⠀⠀⠀⠀⠀⠙⢆⠈⢧⠀⠀⠀⠀⠀⠀⠸⡀ ⡴⠚⢻⣍⣡⠤⠚⠁⠀⠀⠀⠀⢀⡴⠊⠀⠀⠀⠈⠆⠈⡇⠀⠀⠀⠀⠀⠀⡇ ⡇⠀⢻⣀⠤⠤⠤⣀⣀⣠⠞⢠⠋⠀⠀⠀⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠇ ⠹⣄⠔⠁⠀⠀⠀⠀⢠⠛⠦⡎⠀⠀⠀⠀⠀⠀⠀⠀⢰⠇⠀⠀⠀⠀⠀⡸⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠘⡄⠀⢳⠀⠀⠀⠀⠀⠀⠀⢠⠏⠀⠀⠀⠀⠀⡰⠁⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠘⢆⠈⠳⣄⠀⠀⠀⠀⡰⠃⠀⠀⠀⠀⣠⠞⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⣀⣀⣀⣑⣄⣈⣣⡀⠀⡞⠀⠀⢀⣠⠴⠊⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠰⠥⠤⢴⣉⣁⣀⣀⡤⠤⠼⠒⠉⠁⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ (Totally copying Caroline's tricks! ^^) Aude Charillon Librarian | Customer Services Consultant PTFS Europe aude.charillon(a)ptfs-europe.com

1 0

Re: [Koha] Integrating Vision AI / GPT for cataloging in Koha
by Karam Qubsi 19 Sep '24

19 Sep '24

Hi Himanshu, I am working on integrating chatgpt with koha too..but it didn't work for me Not sure what didn't work for you, share some details and I'll try to help, but if the public ChatGPT, ( not the API ) then I noticed that it may add marc data that you never provided, but using OpenAI API you can configure temperature to 0 or 0.x , and with proper prompting this can help making it "less creative" so it only use the provided data in cataloging, and it should try not create other information that is not provided. On Thu, Sep 19, 2024 at 11:03 PM Himanshu Aggarwal <rtr.himanshu(a)gmail.com> wrote: > I am working on integrating chatgpt with koha too..but it didn't work for > me > > On Thu, Sep 19, 2024 at 6:40 PM Karam Qubsi <karamqubsi(a)gmail.com> wrote: > >> Hello Koha community, >> >> I’ve been working on a side project experimenting with AI, and I’ve built >> something that looks interesting to me. I’d love to see if other members >> of >> the Koha community are interested in something similar. >> >> You can watch this 35-second demo I recorded: >> >> https://youtu.be/vnvxmjTUmGQ?si=-YHqLoyp0VeqRL6L >> >> If you have any questions, feel free to ask. >> >> Thanks! >> >> -- >> *Karam Qubsi* >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha(a)lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> > > > -- > Assistant Librarian, > Confucius Institute Scholar 13-14, > R.D. National College, > Bandra (W.) > -- *Karam Qubsi*

1 0

Re: [Koha] Integrating Vision AI / GPT for cataloging in Koha
by Karam Qubsi 19 Sep '24

19 Sep '24

Hi Victor, > The idea could become a plugin? I think they way it looks now ( in the demo) can indeed be inside Koha as a plugin, but if we look at the bigger picture of AI integration with library services, and the need of vector stores to build RAG based systems, for that benefits I found it more efficient to build this as a separate tool and integrate with Koha through Rest API , The main limitation here is Mysql /MariaDB with Vector stores, I'm not aware of any good stable implementation of vector stores in any of those 2 DBs servers, or at least I'm not familiar with that if it exists. Vector stores can help us build things like ( Which I think I will build in later phases if librarians found this useful ) - Chatbot, for both librarians and patrons, can be aware of library collections and rules. and what is available now ( live ) in the library and what is checked out. ( we should have a plugin here to update vector DB with every update of bib or item status ) - Smart Search all library content in any language, you can ask the AI search assistant to find something using your own words / language, and because of storing data as vector embeddings, your query will be converted into an embeddings first, then matched with library content, and you will get results of everything related even if you didn't use the words used in that language in your search!. but it is relevant to your search term. - Authority control ( authors, subjects ..) , if these records are stored as vector embeddings, then the cataloger ( or the AI cataloger) can easily find all relevant controlled authority records related to the material being cataloged now in library catalog history, so selection of new subject heading will be more consistent. On Thu, Sep 19, 2024 at 10:44 PM Victor Barroso Oliveira < vbovictor(a)gmail.com> wrote: > The idea could become a plugin? > > Em qui., 19 de set. de 2024 às 11:32, Karam Qubsi <karamqubsi(a)gmail.com> > escreveu: > >> Hi Victor, >> >> The process is like this: >> >> 1. Cataloger will upload a group of images for the book. >> 2. in backend MarcAI ( what I call it for now) will use some >> predefined prompts along with the provided images as prompts. >> 3. All those prompts are submitted to either OpenAI or Google >> Gemini. For Arabic books, I use both together, but for English and >> Latin-based languages, I think OpenAI alone is sufficient. >> 4. The responses from the AI models are restricted to follow some >> JSON schema defined in MarcAI. >> 5. AI Models will reply following the defined json schema, which will >> be a valid Marc21 record in custom json format. >> 6. then back to UI, cataloger now can see and edit the marc21 record >> if needed. >> 7. Cataloger can click add to Koha, which uses Koha RestAPI with >> OAuth2.0 . ( this will require cataloger to fill in client_id and >> client_secret, only one time) >> 8. Book is added to Koha, ( if duplicate the AddBiblio endpoint will >> return an error of duplicate title with bib id ) >> >> >> Actually this is the current flow, few librarians friends suggested other >> interesting idea, where they can scan ISBN using barcode scanner, ( so a >> 100 books can be scanned in minutes ) or upload a file of ISBNs, and then >> MarcAI will do web search, and group data from z39.50 or other sources, >> then we pass that to AI model, and generate marc21 records based on all >> those information, I will try to explore this scenario next weekend. >> >> Thanks for asking. >> Karam. >> >> >> On Thu, Sep 19, 2024 at 9:48 PM Victor Barroso Oliveira < >> vbovictor(a)gmail.com> wrote: >> >>> Could you detail the process? >>> >>> Em qui., 19 de set. de 2024 às 10:10, Karam Qubsi <karamqubsi(a)gmail.com> >>> escreveu: >>> >>>> Hello Koha community, >>>> >>>> I’ve been working on a side project experimenting with AI, and I’ve >>>> built >>>> something that looks interesting to me. I’d love to see if other >>>> members of >>>> the Koha community are interested in something similar. >>>> >>>> You can watch this 35-second demo I recorded: >>>> >>>> https://youtu.be/vnvxmjTUmGQ?si=-YHqLoyp0VeqRL6L >>>> >>>> If you have any questions, feel free to ask. >>>> >>>> Thanks! >>>> >>>> -- >>>> *Karam Qubsi* >>>> _______________________________________________ >>>> >>>> Koha mailing list http://koha-community.org >>>> Koha(a)lists.katipo.co.nz >>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >>>> >>> >> >> -- >> *Karam Qubsi* >> >> -- *Karam Qubsi*

1 0

Re: [Koha] Integrating Vision AI / GPT for cataloging in Koha
by Karam Qubsi 19 Sep '24

19 Sep '24

Hi Victor, The process is like this: 1. Cataloger will upload a group of images for the book. 2. in backend MarcAI ( what I call it for now) will use some predefined prompts along with the provided images as prompts. 3. All those prompts are submitted to either OpenAI or Google Gemini. For Arabic books, I use both together, but for English and Latin-based languages, I think OpenAI alone is sufficient. 4. The responses from the AI models are restricted to follow some JSON schema defined in MarcAI. 5. AI Models will reply following the defined json schema, which will be a valid Marc21 record in custom json format. 6. then back to UI, cataloger now can see and edit the marc21 record if needed. 7. Cataloger can click add to Koha, which uses Koha RestAPI with OAuth2.0 . ( this will require cataloger to fill in client_id and client_secret, only one time) 8. Book is added to Koha, ( if duplicate the AddBiblio endpoint will return an error of duplicate title with bib id ) Actually this is the current flow, few librarians friends suggested other interesting idea, where they can scan ISBN using barcode scanner, ( so a 100 books can be scanned in minutes ) or upload a file of ISBNs, and then MarcAI will do web search, and group data from z39.50 or other sources, then we pass that to AI model, and generate marc21 records based on all those information, I will try to explore this scenario next weekend. Thanks for asking. Karam. On Thu, Sep 19, 2024 at 9:48 PM Victor Barroso Oliveira <vbovictor(a)gmail.com> wrote: > Could you detail the process? > > Em qui., 19 de set. de 2024 às 10:10, Karam Qubsi <karamqubsi(a)gmail.com> > escreveu: > >> Hello Koha community, >> >> I’ve been working on a side project experimenting with AI, and I’ve built >> something that looks interesting to me. I’d love to see if other members >> of >> the Koha community are interested in something similar. >> >> You can watch this 35-second demo I recorded: >> >> https://youtu.be/vnvxmjTUmGQ?si=-YHqLoyp0VeqRL6L >> >> If you have any questions, feel free to ask. >> >> Thanks! >> >> -- >> *Karam Qubsi* >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha(a)lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> > -- *Karam Qubsi*

1 0

Remove 952$x from search index
by Polonec Viliam, Ing. 17 Sep '24

17 Sep '24

I need to disable searching in non public note field in OPAC. I check settings in /etc/koha/zebradb/marc_defs/marc21/biblios/biblio-koha-indexdefs.xml but there is no 952$x setting. How can I disable searching in 952$x thanks Viliam

2 2

Enquiry
by Himanshu Aggarwal 17 Sep '24

17 Sep '24

Is it possible to see the google book preview in Koha? -- Assistant Librarian, Confucius Institute Scholar 13-14, R.D. National College, Bandra (W.)

1 0

Can´t install plugins - no upload button
by Alvaro Cornejo 14 Sep '24

14 Sep '24

Hi I´m installing a new 24.05 Koha version onto Ubuntu 24.4 and have uploaded a db from my old Koha 19.11 When going to the plugin page, I got a table with errors saying plugin unavailable. This is correct since plugins were not installed on the new 24.05. There are no buttons for uploading the plugins, only the one for filtering by class. I´ve deleted content of tables plugin_data and plugin_methods and now I have a message that no plugin is installed but still there is no button to upload plugins. Also I can´t find the plugin preference in 24.05. Has it been removed? Any idea of what could be wrong? Regards, Alvaro |----------------------------------------------------------------------------------------| Stay safe / Cuídate/ Reste sécurisé 7 Switch off as you go / Apaga lo que no usas / Débranchez au fur et à mesure. q Recycle always / Recicla siempre / Recyclez toujours P Print only if absolutely necessary / Imprime solo si es necesario / Imprimez seulement si nécessaire

2 4

Re: [Koha] ElasticSearch Not Runningf
by Nick Clemens 13 Sep '24

13 Sep '24

Hi Peter, On the server itself if you curl the ES server do you get a response: curl -XGET http://es:9200/ if the server is there, you can run compare_es_to_db.pl to identify missing records, sometimes they are records with problems in the MARC: /usr/share/koha/bin/maintenance/compare_es_to_db.pl You can also check that the indexer is running: sudo koha-es-indexer --status kohadev You should email the general list so that you can get a broader range of answers as well. -Nick On Sat, Sep 7, 2024 at 5:55 PM Peter Kinyua <peterkmwara(a)gmail.com> wrote: > Greetings Nick, > My name is Peter Kinyua working as a Librarian for a private university > in Kenya. I have recently upgraded koha version 22 to 24.05.01 and finally > to 24.05.03.After switching to Elasticsearch from Zebra I was able to > search books.However from the server information Elasticsearch is indicated > as not running while system information page indicates - Records are not > indexed in Elasticsearch- 6 records (s) missing on a total of 5837 in > index koha_teau_library_biblios. > How can I solve this issue..please advise. > > Regards, > > Peter > > -- Nick Clemens ByWater Solutions bywatersolutions.com Phone: (888) 900-8944 Pronouns: (he/him/his) Timezone: Eastern Follow us: <https://www.facebook.com/ByWaterSolutions/> <https://www.instagram.com/bywatersolutions/> <https://www.youtube.com/user/bywatersolutions> <https://twitter.com/ByWaterSolution>

4 4