...

Andrii Vashchuk, development, National Library

Marketta Lukkari
Hanna Saario

Agenda

1. Status report of issues not related with version update

...

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

1. News
   1. HAMK is considering to replace HAMK App with Tuudo. No information of time table yet.
   2. Public libraries have started a conversation about circulation rules in order to minimize Koha Suomi specific code. 

2. Status report:

   1. Koha3 test environment has the latest improvements:
      1. Handling of holding -records
      2. Circulation rules with ccode and shelving location
      3. Edition information added to holds to pull list for each biblio
      4. Anonymized hold indentifier
         1. Test again
      5. Finna view 
   2. HAMK test environment (srv1) updated June 12th, API plugins installed. Finna-view still missing
   3. XAMK test environment (srv2) ready June 12th, Finna-view still missing

3. GDPR requirements - logging all access to patron personal information  - copied from last meeting on June 16th

   1. In Koha-Suomi version all access to patron personal information is logged. In community version there is only logged changes to patron information. In community version there are possibilites to reduce information of patrons to show on different views and there are permission settings for allowing to see/modify patron information.
      1. Discussion topic: how vital is it to log all access to patron information in perspective to GDPR. Should we develop logging and if so, on what level
         1. Logging of of access to personal information is needed in order to monitor, who has had access to personal information
         2. About level of logging
            1. Very wide logging makes log-files hard to use
            2. Minimal logging might leave out actions that ought to be monitored

      2. More information of viewing patron information is gathered here Viewing of patron information.  There is also a list of views showing patron information (can be used when deciding level of logging)

      3. There is already one bug report regarding to this in bugzilla https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25673.

   2. Summary of the discussion:
      1. It is vital to be able to show that personal information is handled with care in library system
      2. Logging is important
      3. About level of logging: log everything (not affecting to performance to add actions on log files), make effort how to report from logs
      4. Low priority for this task: Logging access to patron information. Develop when more important tasks are done. Have discussion with Koha community.

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 

...

• Are there jobs running on test environment - gathering fees, expiring holds that have not picked up in time, LOST (long overdue)?Public libraries have started a conversation about circulation rules in order to minimize Koha Suomi specific code. 

4. Next meeting 

Next meeting is on Tuesday August 18th at 13-14.30. Pilot libraries has been invited to join the meetings in autumn.

...