Participants

Veli-Matti Häkkinen (Jyväskylän yliopisto) *
Sirpa Janhonen (Varastokirjasto) 
Esa-Pekka Keskitalo (Kansalliskirjasto) 
Minna Kivinen (HAMK), chair *
Mia Kujala (XAMK) 
Joonas Kylmälä (Kansalliskirjasto) 
Johanna Miettunen (Haaga-Helia) *
Christian Nelson (Tritonia)*
Hanna Saario (DIAK) *
Andrii Vashchuk, development, National Library  


Agenda

1. Status report of issues not related with version update

1.1 Platform problems 7.-8.12.2020

  • First detected Monday 7.12. around 20.30.
  • Around 9.30 this morning situation had normalized with the exception of 3AMK and Centria. These back up around 12.30.
  • Hanken update had to be postponed.
  • HAMK might have little if no problems.
  • Caused probably by maintenance at CSC.

2.Version update

Update schedule is found on KIWI -page Update schedule and progress tracking

  • Hanken update had to be postponed.
    • 12.1.2021 has been settled.
  • Centria 9.12. - should be OK.
  • Jyväskylä 17.12.
  • KK 14.1.2021

2.1. News

2.2. Status report, deployments

National Archives: Deployment Sept 22nd

HAMK: Deployment Sep 24th 

XAMK: Deployment on Thursday Oct 1st

Diak: Deployment on Oct 7th.

Tritonia: Deployment on Thursday Oct 15th

Arcada: Deployment on Thursday Oct 29th

3AMK: Deployment on Thursday Nov 5th

MPKK: Deployment on Nov 11th

Humak: Deployment on Nov 19th

Tilastokirjasto: Deployment on Nov 26th 

Varastokirjasto: Deployment on Dec 3rd

  • Minor problems, now fixed.


2.3 Status report, Coming migrations

Hanken: Deployment on Dec 8th Will be postponed

  • Test environment in use from Nov 18th

Centria: Deployment on Dec 9th

  • Test environment in use from Nov 18th

JYU: Deployment on Dec 18th

  • Jyväskylä has the server and migration done

KK: Deployment on January

2.3.1 Update of updated Kohas (to the latest version)

From last meeting: 

  • Koha is updated to 20.11. version. Update done to several libraries already, last libraries will be updated on Wednesday December 14th.
  • 3.12.2020 fixed the bug that prevented deleting patrons.
  • Acquisitions price are incorrect (HAMK, XAMK) → needs to be checked.

2.4. Status report, common test environment

Koha3 test environment

Address to Finna view https://kohatesti.finna-test.fi

2.4 Status of development tasks on Update schedule 

  • 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.
    • Development tasks prioritized on the meeting and priorities are found on update schedule -page
    • There are some development tasks in Bugzilla that are needing testing and sign off. Specialists will try to test and sign off all those issues where they have tools to test. Tasks about signing of are documented in the table of development issues.
    • Issues that will need status review or discussion:
  • Priority 1 issues
    • #T24 - No progress to report
    • #18 - Will be fixed in the nex update
    • #F16 - Christian will ask from Finna-posti
    • #11 - Discussed. Hard to estimate the timeline (the other bugs). Will be discussed in January again.

2.5. Discussion topics - items that need discussion about priority or definitions for implementing

2.5.1 How long to keep action logs and deleted data in database 

  • In the last meeting,following notes were made
    • deleted_borrowers: "We need to list cases where it's important to keep, or important to delete this data."
      • Decided: for GDPR reasons, 1 month is good.
      • EP will inform superlibrarians.
    • action_logs: "It would be nice to be able to delete patron data without deleting everything else."
      • Difference btw patron related data and bibliographic data
      • Needs pseudonymization
      • If we do cronjobs, HAMK would be first affected.
      • It is easy to see 6 months back. What about the rest? There is a table called 'action_logs_cache' where these can be found.
      • NLF is not taking action at the moment,.
  • Is there need to revisit the table otherwise?

 2.5.2. Statistics - need change to statistics table?

  • Working Group:
    • Minna, Christian, Esa-Pekka, someone from KK
    • EP will convene
  • Koha webinar about statistics will be planned for the spring.

2.5.3. Patron pseudonymization

No progress. Last meeting notes: 

  • For GDPR reason there has been developed feature for patron pseudonimization in Koha https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24151:
  • The goal of this new feature is to add a way to pseudonymize patron's
data, in a way they could not be personally identifiable.

  • "This development proposes to have 2 different tables:  * 1 for transactions and patrons data (pseudonymized_transactions)
  * 1 for patrons' attributes (pseudonymized_borrower_attributes)
Entries to pseudonymized_transactions are added when a new transaction
(checkout, checkin, renew, on-site checkout) is done.
Also, anonymized_borrower_attributes is populated if patron's attributes are
marked as "keep for pseudonymization". 
    • Configuration
      • Pseudonymization: turn on the feature
      • PseudonymizationPatronFields: which fields are copied to separate table
      • PseudonimizationTransactionFields: which transcation information is copied to separate table

2.5.4. Bugzilla Reporting

  • Bugzilla reporting is important, everyone is encouraged to do those tickets.
  • Add a link to our own documentatio in Kiwi or Redmine
  • Does not apply to Finna issues.
  • Does not apply to plugins. For example, printer plugin, made by Bywater, they might have a Github project.
  • As noted above, we shall use Redmine for internal purposes.

3. Other issues

  • Translation mistake, "kausijulkaisut"? (In component parts). Translation makes sense in Koha-Suomi.

  • Tuudo:

    • Koha-plugin should be installed after Koha upgrade
    • permissions need to be narrowed
  • 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 accounttype = "O" and amountoutstanding > 0 and itemnumber IS NULL;
      (have to check this SQL query, if this a right one or not
    • This might have been copied from somewhere, it's the general idea but there might be minor issues that need fixing.
    • 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
  • Statistics
    • KK will run the statistics for the Consortium costs distribution.
    • Also, Sanasto statistics will be done by KK
  • Patrons' right to check and correct their data. Has been discussed if Hypernova can do development on this. Some work has been done in the community but needs further development.

Further Bugs end development needs

  • We need a place to report new findings
  • Koha-Suomi Redmine might be a solution. Harder to fill in & follow, but more organized.
    • Discussion in the same place.
    • Remember to update descriptions etc. as the ticket matures.
  • Kiwi is more readable and easier to access but harder to maintain.
    • Perhaps update of a Kiwi list from time to time for more outsider readers.
  • Decided: New Redmine Project. Transfer open Kiwi issues there.

4. Specialist group for 2021

Mia Kujala will be chair 2021.

Other members at the group will be:

  • Veli-Matti Häkkinen
  • Sirpa Janhonen, Varastokirjasto
  • Minna Kivinen, HAMK 
  • Christian Nelson, Tritonia
  • Johanna Miettunen, Haaga-Helia / 3AMK
  • Esa-Pekka Keskitalo, Kansalliskirjasto
  • Joonas Kylmälä, Kansalliskirjasto

5. Next meeting 

  • 22.12.2020 klo 13.00-15.30
  • No labels