Page History

...

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?
     • #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?
     • #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
     • #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.
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.

...