Hyvät KK-Koha* DevTeam -asiakkaat!

DevTeam NEWSLETTER #1

beginning with this and further, we will do regular newsletter publishing for you to complement our meetings and other communication and to gather all Koha development and servers support (and some data support) topics which important to be raised in such a manner.

1. We encourage you to use our KK-Koha JIRA:

    https://jira.kansalliskirjasto.fi/projects/KOHA

All of you, our customers, have personal accounts and are represented there and can subscribe, comment, edit or create tickets: feel free to get more acquainted with it. Short hint: browse issues ("tickets"): and become watchers of those you are interested in, so you will have notifications about comments, status changes, and content changes of those tickets, in the ticket body, when you logged in with your JIRA account we provided, in the right column, you'll find:

Click Start watching this issue link and you will have email notifications about ticket changes (status, comments, contents).
Note on this: the first time you might see some extra emails when we sorting tickets across groups, labels, and updating their content.
I will bring more hints and tips in the next newsletters, piece by piece

2. New DI plugin version v1.2.10: fix for "Available material that is not available", more info:

     KOHA-90 - Getting issue details... STATUS
    and previous v1.2.9: "Make OPACHoldsIfAvailableAtPickup work in Finna", more info:
     KOHA-56 - Getting issue details... STATUS

This plugin will be installed on your Kohas TODAY 13:00 but no worries:

  • That is a soft harmless hot restart (by Andrii) invisible for the outer world, so no need to expect any interruptions.
  • Just be aware to alert us if something will be unexpected.
  • Check those new features tomorrow, and feedback to Ere and us.

Please communicate in this particular ticket (KOHA-90) about this topic comments, this will make our communication sorted and all topics connected. 

3. Our former colleague Joonas account was disabled in all your Koha's, but:

but please do other things you need with the deactivated account (probably it's just about to delete it, I suspect, but informing you. More info and let's continue here:  KOHA-34 - Getting issue details... STATUS

4. Koha Autumn'21 release

    (expected build number 324 or above)
     KOHA-44 - Getting issue details... STATUS

We are working to make it happen.

Some issues (temporary build on Koha3 now) with pseudonymization were found by 3AMK and fixed already, testing further, the process goes, but:

Recently in the community was a number of (really serious) security patches to Koha, it was done in a "secret manner" for not to be public (Andrii hot-patched our Koha's too). But that code is not in "master", for not to be public. We still waiting for the community to publish security patches in the master branch, and we should base our build on that patches, so this makes some delay with the release.

Let's agree tomorrow on dates, we might decrease the rush postpone this post-Syysloma (viikolla 42) and post-Kirjastoverkkopäivät as well. Discussion and more info in comments in KOHA-44 ticket.

5. Update lastborroweddate for all customers

   (3AMK updated, confirmed, so this can be done for others)
     KOHA-37 - Getting issue details... STATUS

Andrii will perform some special SQL queries to update all customers' DBs, and those wrong post-voyager lastborroweddate field values will be properly updated.

More info and communication will be done in the ticket on the go.

This will be done throughout this and next week: need more time. I will notify you about this in the next newsletter and also will send personal updates for each library (how many records were changed, so on). You can tomorrow tell me to provide extra info if you need (3AMK can tell tomorrow their experience on this topic so all be aware).

And, the best option to communicate -- in JIRA tickets. All sorted and even - beautiful :).

6. Duplicate SSN removal for all customers

     KOHA-38 - Getting issue details... STATUS

As described in the ticket -- if you occasionally add spaces or newlines around the SSN it is then not detected as "unique". This lead to some errors in the current DB, there're some libraries not listed below, because don't have dupes for now: 3amk, arkisto, hanken, humak, mpkk, stat, varasto, xamk.
Other libraries have dupes, and here is the list (thank you Inkeri for help in improving the report!):

Legend: numbers (like "2 or 54") means so much matching records with one SSN, and a few lines per library means different SSNs,

## Check for non-unique SSNs:
## ------------------------
arcada:
    2
    2
centria:
    55
    21
    2
    2
    2
    2
diak:
    2
fikka:
    2
    2
    2
    2
    2
hamk:
    2
    2
    2
    2
    2
    2
    2
    2
    2
jyu:
    2
    2
    2
tritonia:
    2


We prepared an SQL report for you to find those "duplicated" items, so please, use the report SQL file attached to the KOHA-38 ticket, and fix your borrowers' records (if you need that).

Also, we preparing fixes for the community, some complicated code changes are required, but we expect that we will create in this way: it will be a "trimming option" for any occasionally entered white spaces around the SSN, an extra option for "custom patron attributes" in settings per-attribute.

--- 


SEE YOU TOMORROW ON "Developers Hour" (this time short talk, all here in the letter you have!).
Bring your updates to tell live, regarding these topics above and more.


*KK-Koha on Kansalliskirjasto-Koha,
         jotka ovat: Andrii, Petro, Jussi, Ari, ja Esa-Pekka.
         ... uusi jäsen on tulossa pian!

  • No labels