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)

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 
Anneli Österman 

Agenda

1. Status report of issues not related with version update

  • Some slownes, fixed for tritonia and 3 AMK

  • Will be run to others later.

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.


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

  • Some issues with fine rules w/ ccodes found today. Andrii working with this.
  • Some confusion about changes in e.g. holds management.
  • Finna is working, Tuudo, too. Permissions to Tuudo need to be curtailed.
  • Label plugin now works - documentation needed, different settings need to be checked.
  • Perhaps the libraries should have been closed.
  • When testing: check setting regarding different item statuses. When an item is "perinnässä" - when returned by an automat, it removes the status without notification. Johanna will update the instructions.
  • "Block lost items" could prevent returning, but that is not what is wanted.
  • Remember to restart lending machines when settings are changed. Or ask for restart of SIP2 server.

2.3 Status report, Coming migrations:

MPKK: 

Humak: Upgrade date a bit uncertain, as we got the servers only this morning.

Tilastokirjasto: Envrinomnet got today

Varastokirjasto, Hanken, Centria still waiting for servers.

  • Varastokirjasto: Two weeks should be enough, prepared to  →
  • It takes 2 weeks to get a new server. If we get one in Friday, we can proceed.

KK and JYU: servers not requested yet.

2.3.1 Update of updated Kohas (to the latest version)

  • We have fixes that we could start doing next week.
  • Need to settle the timetable.
  • First Tritonia, then others.

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

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?
        • Working, needs to go through different settings on different printers.
      • #T16: change to holds to pull list: add possibility to filter list by pick up location
      • #T19: Koha functionalities when a transferred hold is cancelled - change transfer destination to item homebranch when hold in transfer is cancelled
      • #T20: When adding a new holdings record or editing a holdings record, there are only 2 MARC frameworks showing in the selection list.
        • Fix suggested, does not work.
        • Indicator problem, too.
        • Other holdings issues reported.
        • → Priority 3. National Library will discuss its importance.
      • #T21:  In staff interface it is not possible to place holds on titles where all items have Not for loan status.  Item type normal loan, status 'Ordered' (952 subfield 7, NOT_LOAN value -1). Place hold -button is missing from the tool row.Placing holds in this case is possible in Finna
      • #F17:  In Finna it is possible to place holds on titles one already has a hold waiting for pick-up and if there is any item available in any library. 
        • → Priority 1
      • #F18: In Finna it is possible to place holds on titles where there are no items at all in patron's home library but item in another branch library
        • → Priority 1
  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.
        1. NLF will work on this.
        2. Discussed about deleted ptarons, etc.

      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 description 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

Bugzilla Reporting

  • Bugzilla reporting is important, everyone is encouraged to do those tickets.
  • Add a link to our own documentatio in Kiwi.
  • Does not apply to Finna issues.
  • Does not apply to plugins. For example, printer plugin, made by Bywater, they might have a Github project.
  • At least, describe the issue in Kiwi. Slack is not good for this purpose.

3. Other issues

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

    • In progress.
    • Translation mistake, "kausijulkaisut"?

  • Tuudo:

    • functionalities are ready

    • discussed if possible to test before going alive
    • 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
  • Translating Koha
    • Can we have a 20.11 sandbox? – If Bywater, you need to specify master - but it does not work at the moment.
  • Sandboxes
    • have had other problems, so have the translation tool. Joonas has mentioned these things in the community
    • For sandboxes, a fix is being worked on.
    • Finna view to old Koha test server? "koha-kk". →

      https://kohatesti.finna-test.fi/kohakk

4. Next meeting 

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



  • No labels