Torstaina 13.1.2022

Etäkokous Zoomilla klo 13-14.

Linkki lähetetty pääkäyttäjäpostituslistalle.

Edellinen kokous: 2021-12-09 Pääkäyttäjäverkoston kokous

Muistio

Kehittäjätuokio / Developers' hour

  • After version update 21.11 duplicating items copied unwanted subfields (number of loans, date accessioned, etc.). Has this been fixed? Is there a ticket in Jira related to this? ➟

    • KOHA-240 - Getting issue details... STATUS


Kohan käännökset / Translating Koha

  • Some fixes made according to KOHA-215 - Getting issue details... STATUS Are they in production already?
    • "p2" solution still not correct: Andrii will update with Esa-Pekka.
    • "p1": Inkeri will append examples and proposals in the KOHA-215 ticket, but to keep in mind that "2" (or "6" as it was on another example) is always stays at the end of the string and it's not related to a number of renewals probably:
      • "Number 6" refers to a number of renewals, totally irrelevant actually, but may be must be retained. But it's not "syspref no 6" 
      • "Järjestelmäasetus esti uusinnan numero 6" or something like that

Pseudonymized_transactions and pseudonymized_borrower_attributes tables

  • This is running now fine. Or was there still something to be fixed with sort1 field and stat_cat?
    • Sort1 and Sort2 are free to be used as wished, at least MPKK uses them for some special needs.
    • Stat_cat goes to a column of its own. Checkbox in asiakasmääreet. It's a multiple value field, so it's in an additional table. pseudonymized_borrower_attributes
    • Clean-ups:
      • ticket: KOHA-228 - Getting issue details... STATUS  
      • we need to clean up borrowernumbers from Sort1 field for some libraries (that happened to be filled Sort1 there since Voyager)
      • also, we need to clean up pseudonymized_transactions rows which contain insecure Sort1 which already went into pseudonymized_transactions table.
    • Useful info about differences across libraries with "STAT_CAT" settings: 
      • in details this text from that chat, STAT_CAT, what checkboxes are set for different libraries:

      • 3amk:

        • multiple values per patron (and data in DB for that!)

        arcada:

        • searchable

        arkisto:

        • searchable

        diak:

        • searchable
        • multiple values per patron (and data in DB for that!)

        fikka:

        • searchable
        • multiple values per patron (and data in DB for that!)

        hamk:

        • searchable

        hanken:

        • searchable
        • multiple values per patron (and data in DB for that!)

        humak:

        • searchable
        • multiple values per patron (and data in DB for that!)

        jyu:

        • searchable
        • multiple values per patron (and data in DB for that!)

        mpkk:

        • no STAT_CAT field at all

        stat:

        • searchable
        • multiple values per patron (NO multiple values in DB though)

        varasto:

        • searchable

        xamk:

        • searchable

        centria:

        • searchable

        tritonia:

        • searchable
        • mandatory
      • outstanding are:
        • MPKK: because nothing (no STAT_CAT at all),
        • Tritonia: STAT_CAT set as mandatory,
        • 3AMK: STAT_CAT set as "not searchable",
        • All others: some libraries have "multiple values" enabled, some don't.
      • 3AMK had cases where a customer has two stat_cats. Duplicate stat can be deleted by changing Patron attribute types->STAT CAT->Mandatory: "Check to make this attribute mandatory when creating or editing a patron". Take it off for a while, clean patron information and put setting back.
        • Changing settings - may have affected Tuudo, but not sure. Anyway fixed by Tuudo people.
        • does this 3AMK-multiple stat_cats closed / not require Andrii/devs participation?

Tilastot /Statistics

  • 16.12. korkeakoulukirjastojen tilastokokous →saadaan yhteiset tilastomääritykset. Onko tästä kerrottavaa?
  • Does Koha Office run the script and deliver the results to libraries? If yes, when?
  • Will be available during January. 

Acquisitions

  • WG meeting 14.12. H-H will pilot with one provider.
  • Piloting needs to be done on the productions server. 
  • Andrii needs specifications for required installations, there will be a separate meeting. 
  • KOHA-88 - Getting issue details... STATUS ,  KOHA-91 - Getting issue details... STATUS

Other Business

  • JIRAn ja Slackin käyttö. Sovitaanko perehdytys seuraavalle tapaamiskerralle? Jos joku ei pääse Slackiin, voi pyytää kutsun Esa-Pekalta.
    • Could be recorded for future reference. 
    • Andrii and Esa-Pekka will plan the programme and suggest a date. 
  • Joulukuun webinaarin tuloksena suunnitteilla ERM-webinaari, tästä tulee myöhemmin lisätietoja. 

Seuraava kokous

  • 27.1.2022




  • No labels