Page History
...
Andrii Vashchuk, development, National Library
Pilot library patricipants:
Marjut Nuikka (Kansallisarkisto)
Hanna Saario (Diak)
Hannu Jokiranta (3AMK, Laurea)
Saija Pyhtilä (3AMK, Metropolia)
Matti Elomaa
...
Agenda
1. Status report of issues not related with version update
From last meeting: Some slownes, fixed for tritonia and 3 AMK - fixed for others as well?
- Incorrect number of servers. Now fixed for all. Case closed.
- Incorrect setting (LUMME sorting) in Koha has caused problems when replicating from Melinda. Fixed for all libraries: setting and data.
- Settings and data fixed for all libraries. Case closed.
2.Version update
Update schedule is found on KIWI -page Update schedule and progress tracking
...
Tilastokirjasto: Deployment on Nov 26th
- Test environment in use
- In schedule.
Varastokirjasto: Deployment on Dec 3rd
- First migration done but errors in the index,
- VARK will test again tomorrow (25.11.) Decision on update must be done on this Friday latest.
Hanken: Deployment on Dec 8th
- Test environment in use from Nov 18th
- Can test.
Centria:
- Test environment in use from Nov 18th
- Can test.
KK and JYU:
- Jyväskylä has the server and migration done
- KK in 1 or 2 weeks.
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.
- Tomorrow this version will be available on the test server, Andrii will notify.
- Release notes: Andrii will list the main changes.
- 20.11. will be released on Friday, will improve translations.
- Proposed date Wednesday Dec 2nd. If problems arise, may be postponed
- For HAMK and Kansallisarkisto more changes
2.4. Status report, common test environment
...
- 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:
- #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).
- Priority 1: what is the status of this issue?
- Fix exists. Needs QA.
- #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.
- Let's keep it this way.
- Fix suggested, does not work.
- #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
- #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).
...
- Koha service has send a suggestion to libraries about how long data should be kept
Table | Time to keep | Description | Comment |
---|---|---|---|
action_logs | 2 years | Check in, check out, making holds, item modifications etc. Which logs are collected is depending of system settings. | Suggest development: it would be nice to be able to delete patron data without deleting everything else. |
deleted_borrowers | 1 kk | Deleted borrowers, deleting has affect to statistics as categorycode or statistical group is not saved elsewhere | Affects to statistics, action logs, old_reserves, old_issues where only borrowernumber is saved to link to additional borrower information (categorycode, statistical group) We need to list cases where it's important to keep, or important to delete this data. |
old_reserves | 3 years | Handled holds. If patron is anonymized, link to patron is deleted when item is returned. | |
old_issues | 3 years | Returned loans. If patron is anonymized, link to patron is deleted when item is returned. | |
accountlines | 3 years | Paid fees. Unpaid fees must be deleted manually | |
statistics | 2 years | Statistical information about loans, renewals, reservations, payments. Needed until all statistics has been taken out. | New fields needed in the statistics table. ANd borrowernumber deleted |
message_queue | 3 years | Sent messages. Needed to check if the message has been sent from system. Only for active borrowers, information deleted when borrower is deleted | |
deleted_biblio, deleted_items | 5 years | Deleted bibliographic records and item records | National Library will not delete these, but it's a special case (Fennica). |
2.5.2. Statistics - need change to statistics table?
- Discussed about statistics. If borrower statistics group changes, all check out issues are attached to latest statistic group.
- For statistics need a new feature to Koha statistics table: borrower categorytype
- Needs new column for a link to relevant patron attributes.
- Statistics module (Mana?)
- It was felt that this issue need a forum of its own. We do not quite understand how all this works and what is dependent on what.
- First documentation, then decisions on the changes.
- Patron pseudonymization needs to be examined (see below) and see if it affects any things above.
- Might help on keeping statistics for a longer time.
- Can be tested on Koha3
- Johanna will talk with Saija and Hannu. Minna will explore, if she has time.
- If we need to unify statistics for 2021, must be done in December (statistics table)
- Cannot do things dyring the rest of 2020.
- Will set up a WG? Let's talk next time.
Column | Type | Size | Nulls | Auto | Default | Children | Parents | Comments |
---|---|---|---|---|---|---|---|---|
datetime | DATETIME | 19 | √ | null | date and time of the transaction | |||
branch | VARCHAR | 10 | √ | null | foreign key, branch where the transaction occurred | |||
value | DOUBLE | 16,4 | √ | null | monetary value associated with the transaction | |||
type | VARCHAR | 16 | √ | null | transaction type (localuse, issue, return, renew, writeoff, payment) | |||
other | LONGTEXT | 2147483647 | √ | null | used by SIP | |||
itemnumber | INT | 10 | √ | null | foreign key from the items table, links transaction to a specific item | |||
itemtype | VARCHAR | 10 | √ | null | foreign key from the itemtypes table, links transaction to a specific item type | |||
location | VARCHAR | 80 | √ | null | authorized value for the shelving location for this item (MARC21 952$c) | |||
borrowernumber | INT | 10 | √ | null |
...
kirjasto | |||||
ccode | VARCHAR | 80 | √ | null |
...
foreign key from the items table, links transaction to a specific collection code
2.5.3. Patron pseudonymization
- For GDPR reason there has been developed feature for patron pseudonimization in Koha https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24151:
The goal of this new feature is to add a way to pseudonymize patron's data, in a way they could not be personally identifiable.
- "This development proposes to have 2 different tables:
* 1 for transactions and patrons data (pseudonymized_transactions) * 1 for patrons' attributes (pseudonymized_borrower_attributes) Entries to pseudonymized_transactions are added when a new transaction (checkout, checkin, renew, on-site checkout) is done. Also, anonymized_borrower_attributes is populated if patron's attributes are marked as "keep for pseudonymization".
- Configuration
- Pseudonymization: turn on the feature
- PseudonymizationPatronFields: which fields are copied to separate table
- PseudonimizationTransactionFields: which transcation information is copied to separate table
- Configuration
2.5.4. Bugzilla Reporting
...
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
- SQL-query that will list these fines is:
- 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". →
- Numerous renewals
- There is a rule, noRenewalBefore. should be the same as the renewal period, then you can renew once a day.
4. Next meeting
- Next scheduled meeting is on Tuesday Dec 8th 13-14.30