Versions Compared

Old Version 2

changes.mady.by.user Mia Kujala

Saved on

compared with

New Version 3

changes.mady.by.user Esa-Pekka Keskitalo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Veli-Matti Häkkinen (Jyväskylän yliopisto ON
Sirpa Janhonen (Varastokirjasto) 
Esa-Pekka Keskitalo (Kansalliskirjasto) ON
Minna Kivinen (HAMK) ON
Mia Kujala (XAMK) ON
Johanna Miettunen (Haaga-Helia) ON
Christian Nelson (Tritonia) ON
Andrii Vashchuk (Kansalliskirjasto) EI
Anneli Österman (Koha-Suomi) ON

1. Version updates

1.1. Koha upgrade:  KOHA-44 - KK-Koha release 16: Autumn'21 In Progress

  • 3AMK as the pilot library confirmed. upgrades on Monday morning Oct 11th. Time postponed due to security fixes in CV. 
    KOHA-40 - Pilot libraries experience gathering: improvement of release process Open
  • 3AMK target for Week 40 Monday (4 October).
  • All other targets for 11 or 18 October. 18 October is not good for all, e.g. HAMK, due to school vacation week. 25.10. is a busy conference week. Dates need to be verified library by library.
  • Andrii: I will shift and update dates this week, we should go before or far after school vacation, I agree.

2. Issues

...

  • SQL-query that will list these fines is: SELECT * FROM accountlines WHERE debit_type_code="overdue" and itemnumber is null and amountoutstanding > 0 
  • Are there results to report in the first place? If there are such, libraries should check how these look like and then fix fines in table.
  • Fees should be fixed after updating to 20.XX version.
  • Even fees from Koha era are included in the query, if the item has been deleted.
  • KK has not have time to look at this yet. Mia has sent details about their case to koha-posti.
  • Nothing new to report on June 15th
  • Johanna: we get 2020 timestamps. See explanation above: if item has been deleted, it shows in the query. Must be remembered possible
  • NLF will check the situation, not a high priority. 

...

  • Glitches, see ticket 44. At least 
  • All other targets: agreed on November 8th. 

Pilot Retrospect:

  • Difficulty of comparing to what was after upgrade. Important to document how things look like in Koha and Finna, otherwise difficult to remember, as there are frequent cases. Snapshots!
  • Check lists being improved: Pilot library memo: hints to pre- and test fresh KK-Koha build
  • What is going to change? What new features, if any? (Many in use, now in CV)
  • Community release notes not very easy to understand. https://koha-community.org/koha-21-05-04-released-⚠-security-release/
  • Let's try to have this for November upgrade. 
  • Is reindexing needed? Not at the upgrade, but will be done in the near future. 
  • More guiding about what one was supposed to e.g. do with the automates, when to reboot, etc. 
  • Libraries might bring together their checklists & other documentation. Also, how to salvage useful notions from Slack and other sources.
  • Important to have peers 
  • Let's share notes about even minor and cosmetic changes. Could add comments to the relevant Jira ticket.
  • Discussed pros and cons of different communication channels.

2. Issues

...

3. Development tasks

  • Development tasks are listed on KIWI -page Update schedule and progress tracking. All development tasks are numbered on list so that it is easier to refer to each task.
    • Issues that will need status review or discussion:

...

  • KOHA-81 - Change circulation rules / CCode and shelfing location To Do
    CCode and shelving location
    • This will be addressed in the autumn due to scheduling issues. Libraries may of course do planning meanwhile. 
    Image RemovedKOHA-56 - Make OPACHoldsIfAvailableAtPickup work in Finna Done
    Limit pickup places in Finna according to OPACHoldsIfAvailableAtPickup - still relevant and waits for resolution. Works in Koha interface, not in Finna. → REST API question. 
    • Done in HAMK. New Finna plugin installed. 
    • If "on", the plugin works like required in that it hides certain pickup locations. 
    • Communication with libraries forthcoming. 
    • Check plugin situation → Waiting for the install to the rest of the libraries. 
    • 3AMK is happy. 
    • Will be updated in a few days after info to superlibrarians. 

3.2. Development and maintenance

...

3.3. Development tasks 2022

We will discuss this in thuis  meeting, people were asked: please think about your experiences, needs and expectations.

For a longer run, at least tases areas were mentioned in the steering group meeting in preparing the webinar on Dec 7th:

  • ERM
  • Automation of routines
  • Statistics, reports, analysis, insights
  • Impact of changes in metadata environment (RDA etc.) and changes in Melinda. 


Last meeting's list:

  • Needs discussion. We have a backlog of grade 2b and 3 issues. Those have been gathered to JIRA and need to be confirmed with their priorities there.
  • Melinda integration
  • Customer driven ILL from Repository Library
  • Acquisitions improvements
  • User data view logs
  • Holdings issues important for many libraries.
  • Statistics table update. Must be done during 2021 
  • Cataloguing: new RDA rules. Conversion needs might occur?
  • Visioning webinar 7.12.2021

We will discuss this in the next meeting: please think about your experiences, needs and expectations.

Security issues important.

Discussed also user experience at the checking automates; and generally, how integrations with devices could be reinvented. E.g. shop self-service counters affect what customers expect.

Discussed possibilities of PoweBI and other data analytics. Easier and wider access to data?

...

Discussion:

  • Cataloguing has frequent changes, needs to fine-tune working environment - must know something about what is happening in cataloguing. 
  • 3AMK: Cancellation of a fulfilled hold. Now they come thru telephone, email, chat and are therefore time-consuming. 
  • VARK: Nuuskija / Sniffer : Automatic updates of MARC fields. Functionality exists in Koha-Suomi's Koha. Also requested by Fikka. → TIKETTI?
  • MFA functionalities. → TIKETTI
  • Customer perspective: multiple library cards, Tuudos, Finnas. When to go where for doing what?
  • Diacritics in searching: make results identical (KOHA-69). Work like Melinda. (Should work like this already, are there mappings missing?)
  • Cashier _software_ integration. Ceepos, at least. Works in Koha-Suomi. → TIKETTI
  • Automatic switch of activation/deactivation. 
  • EditX: cost of doing on Koha3. 
  • Delete outdated payments → TIKETTI?

4 Action logs

How long to keep action logs and deleted data in database

...

 → TIKETTI

  • Mitä tehdään vanhojen lainojen kanssa tilanteessa, että on maksamaton maksu ja esim. 3v vanha palautettu laina, joka liittyy siihen. Lainatietoa ei haluttane poistaa ennen kuin maksu on käsitelty. Bugiraportin voisi laittaa yhteisöön jos halutaan, että palautettuja lainoja, joihin liittyy maksamaton maksu, ei poisteta. Siivousajoa ei ole laitettu kirjastoille ennen kun saadaan selvyys asiaan.
    • Barcode alone is not enough information. It tells about the item that cause the payment, but nothing about the transaction, i.e. no info of checkout date, due date...
    • Some libraries not so keen on fines if the item is returned. Others have kept them longer than 3 years. 
    • Might suggest a new filed, or adding the data to "notes"

    • https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27080

    • "If due payments, retain all data".
  • Seurataan bugia Bugzillassa
  • Voisiko olla cronjob, joka poistaa vanhoja lokititeoja?

...

  • The library directors and Koha experts are invited into a future webinar.

8 Other issues

...

9 Next meeting 

  • Tuesday afternoon, every 3rd Tue of the month
  • → Exception next time due to holidays: 16.11.2021
  • Ari and Anneli from Koha-Suomi will be invited, too.