Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Difficulty of comparing to what was after upgrade. Important to document how things look like in Koha and Finna, otherwise difficult to remember, as there are frequent cases. Snapshots!
  • Check lists being improved: Pilot Release 21.11 pilot library memo: hints to pre- and test fresh KK-Koha build
  • What is going to change? What new features, if any? (Many in use, now in CV)
  • Community release notes not very easy to understand. https://koha-community.org/koha-21-05-04-released-⚠-security-release/
  • Let's try to have this for November upgrade. 
  • Is reindexing needed? Not at the upgrade, but will be done in the near future. 
  • More guiding about what one was supposed to e.g. do with the automates, when to reboot, etc. 
  • Libraries might bring together their checklists & other documentation. Also, how to salvage useful notions from Slack and other sources.
  • Important to have peers 
  • Let's share notes about even minor and cosmetic changes. Could add comments to the relevant Jira ticket.
  • Discussed pros and cons of different communication channels.

...

  • Cataloguing has frequent changes, needs to fine-tune working environment - must know something about what is happening in cataloguing. 
  • 3AMK: Cancellation of a fulfilled hold. Now they come thru telephone, email, chat and are therefore time-consuming. 
  • VARK: Nuuskija / Sniffer : Automatic updates of MARC fields. Functionality exists in Koha-Suomi's Koha. Also requested by Fikka. → TIKETTI?
  • MFA functionalities. → TIKETTI: luotu: 
    Jira
    serverKansalliskirjaston JIRA
    serverIdf77f19b3-0866-3dd6-97a9-e424355d78c1
    keyKOHA-150
     Henkilökunnalle yhteisöversiossa on itse asiassa CV:ssa nähtävästi aika valmis ratkaisu. 
  • Customer perspective: multiple library cards, Tuudos, Finnas. When to go where for doing what?
  • Diacritics in searching: make results identical (KOHA-69). Work like Melinda. (Should work like this already, are there mappings missing?)
  • Cashier _software_ integration. Ceepos, at least. Works in Koha-Suomi. → TIKETTI: luotu 
    Jira
    serverKansalliskirjaston JIRA
    serverIdf77f19b3-0866-3dd6-97a9-e424355d78c1
    keyKOHA-152
  • Automatic switch of activation/deactivation. 
    Jira
    serverKansalliskirjaston JIRA
    serverIdf77f19b3-0866-3dd6-97a9-e424355d78c1
    keyKOHA-60
  • EditX: cost of doing on Koha3. 
  • Delete outdated payments → TIKETTI: luotu, täydentäkää: 
    Jira
    serverKansalliskirjaston JIRA
    serverIdf77f19b3-0866-3dd6-97a9-e424355d78c1
    keyKOHA-153

4 Action logs

How long to keep action logs and deleted data in database  → TIKETTI 
Jira
serverKansalliskirjaston JIRA
serverIdf77f19b3-0866-3dd6-97a9-e424355d78c1
keyKOHA-154

  • Mitä tehdään vanhojen lainojen kanssa tilanteessa, että on maksamaton maksu ja esim. 3v vanha palautettu laina, joka liittyy siihen. Lainatietoa ei haluttane poistaa ennen kuin maksu on käsitelty. Bugiraportin voisi laittaa yhteisöön jos halutaan, että palautettuja lainoja, joihin liittyy maksamaton maksu, ei poisteta. Siivousajoa ei ole laitettu kirjastoille ennen kun saadaan selvyys asiaan.
    • Barcode alone is not enough information. It tells about the item that cause the payment, but nothing about the transaction, i.e. no info of checkout date, due date...
    • Some libraries not so keen on fines if the item is returned. Others have kept them longer than 3 years. 
    • Might suggest a new filed, or adding the data to "notes"
    • https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27080

    • "If due payments, retain all data".
  • Seurataan bugia Bugzillassa
  • Voisiko olla cronjob, joka poistaa vanhoja lokititeoja?

...