Osallistujat

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 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
  • 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: Release 21.11 pilot library memo
  • 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:

3.1. Priority tasks

  • 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. 

3.2. Development and maintenance

NOTES

Kehitystoiveet

  • It is important to document Priority 3 issues in Bugzilla. As we do not intend to look at these, we need to notify the community in case someone else were willing to take it up. 
  • The relevant libraries need to contribute, reports cannot be written by there. → Superlibrarians 

 Kehitys ja ylläpito 2021

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

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: luotu:  KOHA-150 - Getting issue details... STATUS  Henkilökunnalle yhteisöversiossa on itse asiassa CV:ssa nähtävästi aika valmis ratkaisu. 
  • 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: luotu  KOHA-152 - Getting issue details... STATUS
  • Automatic switch of activation/deactivation.  KOHA-60 - Getting issue details... STATUS
  • EditX: cost of doing on Koha3. 
  • Delete outdated payments → TIKETTI: luotu, täydentäkää:  KOHA-153 - Getting issue details... STATUS

4 Action logs

How long to keep action logs and deleted data in database  → TIKETTI  KOHA-154 - Getting issue details... STATUS

  • 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?

Patron pseudonymization

5 Statistics

Statistics - need change to statistics table?

  • KOHA-82 - Make changes to Statistics table after check-ups To Do
  • Working Group:
    • Minna, Christian, Esa-Pekka, Inkeri Hakulinen
    • 2021-06-04 Tilastopalaveri
    • In brief following additions are suggested:
    • Patron data
      • categorycode, customer group (asiakasryhmä) ; ollut usercode, ei ole enää?
      • borrower_attributes: STAT_CAT (not added by pseudonymization work), statistics group
      • (question) branchcode, home library. Discussed the merits of this. Not actively used and updated in all libraries. 
    • Item data : N.B. work done with pseudonymization adds these. / 21.9.2021
      • homebrach, niteen kotipaikka 
      • itemcallnumber, niteen hyllypaikka
    • Methdod of issuing, renewal Not solved by pseudonymization development
      • basically, the interface used: staff GUI, SIP, API 

Could pseudonymization work sole this issue? Using SORT fields. May be tested on Koha3. Moving STAT-CAT to SORT1. 

Statcat now comes from extended patron attribute types that is domestic extension. Patron_stat_groups. 

Esa-Pekka convenes the Statistics WG and Andrii to clarify if we will use pseudonymization

6 Server Access

  • KOHA-83 - Help libraries with server access as needed To Do
  • Needs to check the instructions. Usernames still missing? 

  • XAMK has access to the server but no db usernames. 

  • JYU: working. 

7 Tulevaisuuswebinaari 7.12.2021 klo 10.15-12

  • 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.
  • No labels