Participants

Veli-Matti Häkkinen (Jyväskylän yliopisto) x
Sirpa Janhonen (Varastokirjasto) x
Esa-Pekka Keskitalo (Kansalliskirjasto) x
Minna Kivinen (HAMK), chair x
Mia Kujala (XAMK) x
Joonas Kylmälä (Kansalliskirjasto) x

Andrii Vashchuk, development, National Library x

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

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


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


Absent:

Johanna Miettunen (3AMK, Haaga-Helia)

Christian Nelson (Tritonia)



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: none since 7.9.

Server redepolyment timetable issue

But: Server changes were planned in one way but CSC will do them differently. We are still waiting for CSC:n further response. It might affect the new server creations every time.

3AMK will have its server only next week. This leaves a very short testing time, like 2 weeks. We very probably need to postpone this, if CSC vannot accelerate.

Regarding Arcada, they must be notified in case delay will happen, see above.


2.1. News

2.2. Status report, pilot libraries:

National Archives 

  • Deployment Sept 22nd
  • Migration had to be restarted, but after that everything went OK.

HAMK

  • Deployment Sep 24th
  • No big issues, some minor ones
  • Migration started at 7, testing at 10:30, Koha live in 11, Finna live at 12.
  • Checklist is important. Ohjeita KV-version testaamiseen ja käyttöönottoon
  • There are many things that needs to be done simultaneously!
  • Melinda goes smoothly
  • Mikroväylä automates: stunnel config file changed, for IP address / domain name; very easy. 

XAMK

  • XAMK test environment (srv2) ready June 12th, Finna-view ready
  • Deployment scheduled on Thursday Oct 1st
  • Library closed only for morning service hours.

Diak:

  • Finna view will be ordered today

Tritonia:

  • Finna view will be ordered today


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
  4. Holdings records should be working with Finna and also facets should show item information
  • Finna:
  • Continue to report bugs via Slack and email, but collect issues to Update schedule -page in KIWI. Please note that this page is public.

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. Logging of access to Patron personal information
      1. There is discussion about this in slack. We should discuss about the need and priority of logging access to patron personal information.
      2. Look at bugzilla bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25673
      3. Minuses: takes space as it logs a lot, and will be hard to examine. Will be a burden with further changes.
      4. Some university systems do this kind of logging
      5. we log API queries at some level
      6. Minna has hidden hetu from the view page, so it is only seen when editing.
      7. Decision: we come back to this after the updates
    2. Hold transfer slip
      1. In Koha-Suomi version there  was a hold transfer slip Slip is printed when item is attached to hold with pickup at another branch than the branch where it is checked in.
      2. Decision: Development item. Wil be a system preference, not an selectabe option, in order tho avoid clutter and errors on GUI.

3. Other issues

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

  • Tuudo: basic functionalities for existing customers will be there at time, but there will propably be a halt in activating new patrons.

4. Next meeting 

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



  • No labels