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)

Andrii Vashchuk, development, National Library  

Pilot library patricipants:
Marjut Nuikka (Kansallisarkisto) 
Hanna Saario (Diak) 

Hannu Jokiranta (3AMK, Laurea) 
Saija Pyhtilä (3AMK, Metropolia) 
Matti Elomaa

Koha-Suomi participants:
Ari Mäkiranta EI
Anneli Österman ON

Agenda

1. Status report of issues not related with version update

• No reports

2.Version update

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

Pilot libraries are asked to inform the preferred date for deployment to Koha-posti.

Schedule changes: 3AMK library deployment has been postponed to week 45 (November 5th)

2.1. News

2.2. Status report, pilot libraries:

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

2.3 Status report, Coming migrations:

ARCADA

3AMK

• Q about Tuudo. New patrons cannot be created as yet, but they have a new plugin in place, waiting for testing.
• Payment problems detected in DIAK Tuudo. Some payments did not show in Tuudo. Reported to Tuudo coders, and the reason was found. New Koha has so many differemts payments, that it is very complicated. Also, Joonas noticed confusion about write-off turning into a pending fee. In Finna it was correct.

MPKK

2.4. Status report, common test environment

Koha3 test environment

1. Has the newest version
2. Ccode: is it functional? Minna has tested a few weeks ago and it worked then. Andrii: it has been kept as it was. Report any problems with Andrii directly.
3. Address to Finna view https://kohatesti.finna-test.fi

2.4 Status of development tasks on Update schedule 

1. 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.
2. Discussion topics - items that need discussion about priority or definitions for implementing
   1. Action logs in Koha

      1. How long are the action_log items saved in community version. - They need to be stored for a year at least for library statistics. 1,5 years is better, perhaps 2 years. Libraries can make the system preference options for which actions are logged.
         

      2. Issue about deleted_borrowers, old_reserves, old_issues.

         1. Discussed if it is enough to keep deleted_borrowers for 1 month or should they be kept for longer time. Can be configured by library also.

         2. Not sure if old_issues and deleted_reserves are needed for statistics. At least half a year is needed? If patron is deleted, then the old_issues table could be change borrowernumber to dummy patron record that is used for anonymised statistics.

         3. Deleted_biblio or deleted_items could be saved for longer time. But for security reasons there should be possible to remove information completely. (decided that in these seldom cases library could ask for a record to be removed.) Deleted_biblio and deleted_items would be saved for 5 years.

      3. Discussed about statistics. If borrower statistics group changes, all check out issues are attached to latest statistic group.

      4. Continue in next meeting after discussions with system librarians if needed.

3. Other issues

• Question about component parts: no changes, the parts will come along with the replication.

• Tuudo: basic functionalities for existing customers will be there at time, but uploading new patron information does not work.

• Voyager fines: there are some fines remaining from Voyager time where fines were still in accruing situation in Voyager.
  • 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)

  • If there are such, libraries should check how these look like and then fix fines in table.

4. Next meeting 

Meeting of development tasks for next year on Wednesday Oct 28th at 11-12

Next scheduled meeting is on Tuesday Oct 10th 13-14.30