Participants

Veli-Matti Häkkinen (Jyväskylän yliopisto) 
Sirpa Janhonen (Varastokirjasto) 
Esa-Pekka Keskitalo (Kansalliskirjasto) ei
Minna Kivinen (HAMK), chair 
Mia Kujala (XAMK) 
Joonas Kylmälä (Kansalliskirjasto) 
Johanna Miettunen (Haaga-Helia) ei
Christian Nelson (Tritonia)

Andrii Vashchuk, development, National Library  

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

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


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

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


No test servers yet for Humak or Tilastokirjasto, but should not reflect to time schedule.

2.4. Status report, common test environment

Koha3 test environment

Update to Koha is planned for Koha3 test environment and after that for all the libraries 

  • Tritonia can be the first library after Koha3-server

About upgrades:

  • There comes a lot of development going on community version
  • Discussed about regular upgrading, decided to go for regular updates when all libraries have been updated to 20.XX version


  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.
    • Issues that will need status review or discussion:
      • #01: label printer - what is the status for this in 3AMK?
        • Discussed in slack, need live session between development and library
      • #T16: change to holds to pull list: add possibility to filter list by pick up location 
        • This change is added to the list of future development reviewed an prioritized for next year, is that ok?
        • Review Koha-Suomi plans about this feature
      • #T17: Checking out a non-reservable item (in our case short loan / overnight copy) automatically removes the patron's title hold (eg. queuing for the normal 2 week copies). Solved by adding non-reservable item type to Default holds policy by item type > No holds allowed, Bug report in Bugzilla should be made however
        • Greate a bug report in Bugzilla
      • #T18: Searching in Koha with words that are in different marc fields returns 0 results. (e.g. Hirsjärvi tutki or Tutki ja kirjoita 2009). This worked fine in old Koha.
        • Review again after updating Koha to libraries (3AMK)
        • If not working add to prioritized list with high priority
  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. - Keep action_logs for 2 years. Libraries can make the system preference options for which actions are logged.

        If action_logs are deleted after 2 years then also information about changes in bib-records and items will be lost.

      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.

      3. Discussed about pending fees and how do that reflect to deleting information
        1. Suggested to keep all information that have pending fees attached, but there might be no tools to check that.
      4. Deleted_borrowers
        1. Suggestion: Keep for 1 month
      5.  Old_reserves
        1. Kept for ever or as long as the patron is active on database
        2. If there are fees attached to holds not picked up in time then old_reserve should not be deleted - no tools to check the fees
        3. Suggestion: Keep for 3 years
      6. Old_issues
        1. Kept for ever or as long as the patron is active on database
        2. If there are fees attached to holds not picked up in time then old_issues should not be deleted  - no tools to check the fees
        3. Suggestion: Keep for 3 years
      7. Accountlines
        1. How long to keep paid feed
          1. When borrower is deleted, there still is a record in accountlines
          2. Suggestion: Keep for 3 years
        2. How long to keep unpaid fees
      8. Statistics table
        1. Suggestion: Keep for 2 years
      9. Send messages
        1. Deleted when the borrower is deleted
        2. Suggestion: Keep for 3 year
      10. Loan history
        1. Change information that Finna gives about loan history. Finna has an option that the customer can choose to keep loan history for ever, but that is not possible.

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

    2. Statistics - need change to statistics table

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

      2. For statistics need a new feature to Koha statistics table:
    3. How do we proceed with the suggestions:
      1. National Library will write down a policy about how information is kept.
        1. Add a decription how does this affect to different things in Koha use, replication to Melinda, Finna
      2. Koha-team will then ask from libraries how they want to act

3. Other issues

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

  • Tuudo:

    • functionalities are ready

    • discussed if possible to test before going alive
    • Koha-plugin should be installed after Koha upgrade
  • 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)
    • 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

4. Next meeting 

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

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



  • No labels