Aka: pe 26.11.2021 klo 12-13

Paikka: Zoom

Osallistujat: Inkeri Hakulinen, Esa-Pekka Keskital, Christian Nelson

Translated to English for future processing. 

Ticket: KOHA-82 - Getting issue details... STATUS

Previous data page: 2021-06-04 Tilastopalaveri

Option A: Rely on pseudonymization only

External info: https://bywatersolutions.com/education/pseudonymization-in-21-05-the-new-feature-youll-want-to-learn-to-spell-and-pronounce

Christian; It seems implementation of pseudonymization will mostly solve the needs.

  • Need to move statistical groups to SORT
    • SORT does not require an authorized form. 
    • Should have restricted values, drop-down 
  • MPKK uses SORT fields for something else.
    • Check the use with everyone
    • What to do with MPKK and other's data in SORT fields?
  • HAMK wishes info about the loan method, manual/machine, etc.
    • Can live without, though, if difficult to 
  • Statistics scripts need to be checked.

Option B: Change the Table

  • Add columns to the statistics table. We might have good arguments.
  • Andrii prefers this. Easier to use data, more consistent. Does not interfere with another SORT usage.
  • Andrii will, after the upgrade, look at the possibilities. 

The real difference btw options is the location of the statistical group. 

Need to amend statistics table

The Statistics table now lacks data that is required to determine the nature of actions from the statistical point of view, e.g. at the end of the year. Checking the data from elsewhere will produce skewed results, if, for example, a patron's status changes during the year. A few additions could make data significantly more reliable. 

Data now

ColumnTypeSizeNullsAutoDefaultChildrenParentsComments
datetimeDATETIME19√
null

date and time of the transaction

branchVARCHAR10√
null

foreign key, branch where the transaction occurred

valueDOUBLE16,4√
null

monetary value associated with the transaction

typeVARCHAR16√
null
account_offset_types

transaction type (localuse, issue, return, renew, writeoff, payment)

otherLONGTEXT2147483647√
null

used by SIP

itemnumberINT10√
null

foreign key from the items table, links transaction to a specific item

itemtypeVARCHAR10√
null
itemtypes

foreign key from the itemtypes table, links transaction to a specific item type

locationVARCHAR80√
null

authorized value for the shelving location for this item (MARC21 952$c)

borrowernumberINT10√
null

kirjasto
ccodeVARCHAR80√
null


Suggestions for added data

  • Patron data
    • categorycode = patron group. Pseudo will add.
    • borrower_attributes: STAT_CAT = statistics group - not added by pseudonymization
    • (question) branchcode, home library. Not used or maintained by all libraries. Pseudo will add.
  • Item data
    • homebrach, Pseudo will add.
    • itemcallnumber, Pseudo will add.
  • Method of issuing - not added by pseudonymization
    • More exactly, data on the API used. Staff member, SIP, other API...
      • Only in logs? Which log? 
      • Intranet/SIP/RestAPI
    • Action log. Used in KITT script.
    • As it is, we can't see e.g. different behaviour of patron groups,
    • NICE TO HAVE; NOT A MUST. 
  • No labels