You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Osallistujat

Veli-Matti Häkkinen (Jyväskylän yliopisto)
Sirpa Janhonen (Varastokirjasto)
Esa-Pekka Keskitalo (Kansalliskirjasto)
Minna Kivinen (HAMK)
Mia Kujala (XAMK)
Joonas Kylmälä (Kansalliskirjasto)
Johanna Miettunen (Haaga-Helia)
Christian Nelson (Tritonia)

1. Version updates

1.1. Schedule of major updates from the national fork to the community version

Update schedule is found on KIWI -page Update schedule and progress tracking

Past upgrades

  • National Archives: Deployment Sept 22nd
  • HAMK: Deployment Sep 24th 
  • XAMK: Deployment on Thursday Oct 1st
  • DiakDeployment on Oct 7th.
  • Tritonia: Deployment on Thursday Oct 15th
  • Arcada: Deployment on Thursday Oct 29th
  • 3AMK: Deployment on Thursday Nov 5th
  • MPKK: Deployment on Nov 11th
  • Humak: Deployment on Nov 19th
  • Tilastokirjasto: Deployment on Nov 26th 
  • Varastokirjasto: Deployment on Dec 3rd
  • Centria: Deployment on Dec 9th
  • Jyväskylä University: Deployment on Dec 17th
  • Hanken Deployment on Jan 12th
  • KK Deployment on Jan 26th

1.2. Version update to 20.11.

  • Koha update to 20.11. version. Update done to several libraries already, last libraries will be updated on January 26th.

1.3. Version update to the Koha x.xx in February

  • All libraries updated to a new Koha version on February 15th, 2021.
  • 264c will be added to the biblio table separately very possibly before this update. (Important to manage hold queues.)

2. Issues

  • Acquisitions price are incorrect (HAMK, XAMK)
    • In acquisition one should be careful to fill up all price fields when receiving items. Koha does not anymore update automatically Unitprice -fields when receiving items.
    • Ticket required → Redmine → Palaute-projekti
    • Reporting to Bugzilla may often result in quick fixes.
  • 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 debit_type_code="overdue" and itemnumber is null and amountoutstanding > 0 
    • 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.
    • Myös Kohan aikaisia maksuja tilassa kertyvä maksu, vaikka palautettu.
    • KK has not have time to look at this yet.
    • Mia has sent details about their case to koha-posti.

3. Development tasks

  • 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:

3.1. Priority 1 tasks

  • #T24 & #T25
    • This is big refactoring, will take Q1+Q2.
    • if items cannot be transferred, hold button should be hidden
    • If no items (only biblio), hold button should be hidden
    • On the other hand, patron should be able to make hold and pick it up in that library. (Must be tested if works now)
    • Joonas is working with the root issue. Lots of necessary checks missing (Patron's fines, branch, etc.) Must make this follow circulation rules.
    • Same applies to holds-to-pull list, it does not follow circ rules. And transfers, different logic in different places, have similar issues.
    • No update at this time.

  • #F16 - Christian will ask from Finna-posti
    • Any translations in Koha (authorized values) - contains a description only, cannot have impact on this issue?
    • Code based translations do not work, shows only the description.
    • Something must have changed!
    • Johanna will look what is different in Metropolia: in Metropolia, they have done new translations, which have to cover all branches. For example:
      • location_Metropolia Arabia, Laina-aika 14 vrk = "Metropolia Arabia, Kahden viikon laina"
      • location_Metropolia Arabia, Laina-aika 28 vrk = "Metropolia Arabia, Neljän viikon laina"
      • location_Metropolia Arabia, Nuotit - Laina-aika 14 vrk = "Metropolia Arabia: Nuotit, Kahden viikon laina"

      • location_Metropolia Arabia, Nuotit - Laina-aika 28 vrk = "Metropolia Arabia: Nuotit, Neljän viikon laina"

      • location_Metropolia Karamalmi, Laina-aika 14 vrk = "Metropolia Karamalmi, Kahden viikon laina"

      • location_Metropolia Karamalmi, Laina-aika 28 vrk = "Metropolia Karamalmi, Neljän viikon laina"

    • Esa-Pekka will inquire again.

  • #11 DO NOT ALLOW SELF SERVICE CHECK OUT WHEN ON HOLD AND IN TRANSFER – KULJETUTUSTILAISTEN VARATTUJEN NITEIDEN LAINAAMINEN AUTOMAATILLA ESTETTÄVÄ - Discussed. Hard to estimate the timeline (the other bugs). Will be discussed in January again.
    • Forthcoming.

3.2. Development and maintenance

  •  Kehitys ja ylläpito 2021

    Tammikuu

    • Kansalliskirjaston päivitys
    • Tilastot: KITT, yhteenliittymän kustannustenjako, Sanasto, julkaisutilasto
    • Alustapalvelun kehittäminen CSC:n kanssa, suunnittelun aloittaminen
    • Ylläpitotehtäviä

    Helmikuu

    • Prioriteetti 1 -kehitystehtävät: dependenssien tarkistukset ja korjaukset
    • Alustapalvelun kehittäminen CSC:n kanssa, suunnittelu
    • Formaattien automaattinen päivitys
    • [Tilastointihackathon?]
    • Ylläpitotehtäviä

4. Common test environment

5 Action logs

How long to keep action logs and deleted data in database 

  • In the last meeting,following notes were made
    • deleted_borrowers: "We need to list cases where it's important to keep, or important to delete this data."
      • Decided: for GDPR reasons, 1 month is good.
      • EP will inform superlibrarians.
    • action_logs: "It would be nice to be able to delete patron data without deleting everything else."
      • Difference btw patron related data and bibliographic data
      • Needs pseudonymization
      • If we do cronjobs, HAMK would be first affected.
      • It is easy to see 6 months back. What about the rest? There is a table called 'action_logs_cache' where these can be found.
      • NLF is not taking action at the moment,.
  • Is there need to revisit the table otherwise?

Patron pseudonymization

6 Statistics

Statistics - need change to statistics table?

  • Statistics
    • Hackathon 17.2.2021 klo 21-15

7 Reporting & Documentation

Redmine Reporting

  • New project: Kehitysehdotukset
  • Sisältää yhteisö- ja Koha-Suomi-Kohan kehittämisehdotukset, joita työstetään Suomessa.
  • Status (Tila): "Kehitys yhteisössä", if there is a ticket in the Bugzilla, if not, select any other status

  • Category (Sektori): Yleinen / Tieteellinen

Bugzilla Reporting

  • Bugzilla reporting is important, everyone is encouraged to do those tickets.
  • Add a link to our own documentation in Kiwi or Redmine.
    • Project: Kehitysehdotukset
    • Category: tieteelliset
    • Status (Tila): "Kehitys yhteisössä"
  • Does not apply to
    • Finna issues.
    • plugins. For example, printer plugin, made by Bywater, they might have a Github project.
  • Let's start with a clean list regarding CV. Joonas will do it.
  • Let's use English primarily.
  • Who can do Bugzilla reports? System librarians.
  • Minna Kivinen & Mia Kujala will move the issues.
  • Instructions: to Kiwi; Esa-Pekka.

9 Next meeting 

  • Tuesday afternoon, every 3rd Tue of the month
  • → 16.3.2021 klo 13-14.30.
  • Ari and Anneli from Koha-Suomi will be invited, too.
  • No labels