...

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

...

• 3AMK as the pilot library confirmed.
• 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.
• Let's

2. Issues

• Jira
  server Kansalliskirjaston JIRA serverId f77f19b3-0866-3dd6-97a9-e424355d78c1 key KOHA-79

  
  Voyager fines: there are some fines remaining from Voyager time where fines were still in accruing situation in Voyager. There was incorrect information if the item was returned or not.
  • 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. 
•  

  Jira
  server Kansalliskirjaston JIRA serverId f77f19b3-0866-3dd6-97a9-e424355d78c1 key KOHA-80

  
  Indexes
  • Indexing workgroup is not actively working any more. 
  • If any new needs, notify Superlibrarians. 
  • New mappings received 6.9.→ Need to be implemented. 
  • Search of holdings still missing, must wait holdings support in the CV. 
    
    • https://tiketti.koha-suomi.fi/projects/koha-suomen-dokumentaatio/wiki/Indeksointitarpeet ; read also "testaushuomioita". These are being tested in Täti. 
    • Limiting to Component part / Analytic records still under work. 

...

• Jira
  server Kansalliskirjaston JIRA serverId f77f19b3-0866-3dd6-97a9-e424355d78c1 key KOHA-81

  
  CCode and shelfing shelving location
  • This will be addressed in the autumn due to scheduling issues. Libraries may of course do planning meanwhile. 

• Jira
  server Kansalliskirjaston JIRA serverId f77f19b3-0866-3dd6-97a9-e424355d78c1 key KOHA-56

  
  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

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

E materials outside Koha scope.

4 Action logs

How long to keep action logs and deleted data in database  

...

• 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.Discussion March 16th: 
  
  • 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 no 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

• Needs testing > Pseudonymization enabbled 20.9.2021 in Koha3
• For previous developments, see notes 8.12.2021.
• Deadline: this year, so that there will be no more problems due to this in 2022.
• Should we have a pace to document this, other than Bugzilla?
• Might query for a tutorial thru mailing lists. Kohacon presentation by Sonia Bouis:
  
• https://wiki.koha-community.org/wiki/Category:GDPR
• https://wiki.koha-community.org/wiki/Improve_data_protection_and_patron_privacy

• Pseudonymization in 21.05: The new feature you'll want to learn to spell and pronounce: https://bywatersolutions.com/education/pseudonymization-in-21-05-the-new-feature-youll-want-to-learn-to-spell-and-pronounce

• Mia Kujala & Johanna Miettunen will look at this in the test implementation.
• Johanna will come back to this after upgrade.
• Back to this later.

• Jira
  server Kansalliskirjaston JIRA serverId f77f19b3-0866-3dd6-97a9-e424355d78c1 key KOHA-77

   

  Jira
  server Kansalliskirjaston JIRA serverId f77f19b3-0866-3dd6-97a9-e424355d78c1 key KOHA-78

...

• Jira
  server Kansalliskirjaston JIRA serverId f77f19b3-0866-3dd6-97a9-e424355d78c1 key KOHA-82

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

Server Access

• Jira
  server Kansalliskirjaston JIRA serverId f77f19b3-0866-3dd6-97a9-e424355d78c1 key KOHA-83

• Needs to check the instructions. Usernames still missing? 

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

• JYU: working. 

...

• Tuesday afternoon, every 3rd Tue of the month
• → 19.10.2021 klo at 13-14.30.
• Ari and Anneli from Koha-Suomi will be invited, too.