Osallistujat

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)

1. Version updates

1.1. Koha upgrade:  KOHA-44 - Getting issue details... STATUS

  • 3AMK as the pilot library confirmed.
    KOHA-40 - Getting issue details... STATUS
  • 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

  • KOHA-79 - Getting issue details... STATUS
    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. 
  •   KOHA-80 - Getting issue details... STATUS
    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. 

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 - Getting issue details... STATUS
    CCode and shelving location
    • This will be addressed in the autumn due to scheduling issues. Libraries may of course do planning meanwhile. 
  • KOHA-56 - Getting issue details... STATUS
    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

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

  • 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.
    • 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 - Getting issue details... STATUS
  • 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

Server Access

  • KOHA-83 - Getting issue details... STATUS
  • Needs to check the instructions. Usernames still missing? 

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

  • JYU: working. 

6 Other issues

  • Data removal request from Metropolia. 
    • "Deleting" / deleting:
      KOHA-22 - Getting issue details... STATUS

7 Next meeting 

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