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

Compare with Current View Page History

« Previous Version 4 Next »

Older page(s): 21.11 pilot library memo, 22.05 pilot library memo, 22.11 pilot library memo

CURRENT 23.05 RELEASE:

dates, plans, steps and progress in JIRA:

PLEASE! Use Slack channel:  ADD HERE
for most issues and their life cycle support talks and get back there with notes, which you think should be noted.

Table of contents:




 

Something working differently as before?


Something new added? 

-Cataloging: Batch item modification: https://koha-pre-ko.koha.csc.fi/cgi-bin/koha/tools/batchMod.pl : Possibility to choose in batch item modification that items that check out items can be check in 

How to and what to test to be sure that your Koha works properly

When testing, it is important to check the result of any action in Koha and in Finna views (also Finna.fi).

Some functions may seem like they work fine, but it is a good practice to verify the situation from the staff view and patron's point of view.

Check all functions related to nightly cronjobs

  • Autorenewals

  • Fines

  • Holds expiring

  • Hold expire charges

Other resources:

Test plan notes by 3AMK, regarding test server


Function/process to test

  • test Finnish and English (and Swedish) interfaces

Koha

Finna

Cataloging

Create a new bibliographic record, if you do those in your Koha 

  • frameworks are working as they should 

  • fields are shown as they used to be

  • MARC bibliographic framework test, cgi-bin/koha/admin/checkmarc.pl

  • item date picker should work when adding item)  (see Jira KOHA-278 - Getting issue details... STATUS )



Cataloging

Making a new holdings (previous version: 500 error)

  • holdings templates (bibliographic frameworks) and fields are working as they should (previous version: couldn't change the tab in holdings framework)

  • cgi-bin/koha/admin/biblio_framework.pl



Cataloging

Adding and editing an item

  • editing via Action button: Duplicate a copy

  • add multiple copies using Add & duplicate, Add multiple copies of this item

  • change item's Not for loan -status eg. from Ordered to In Process etc. Check that status changes correctly in Finna too.



Cataloging

Component parts, e.g. music (parent and child records)

  • linking with parents and child record 

  • child and parents can be found with title



Circulation (borrowing)

Borrow items with different item types to different patron categories (regular, staff, students, ILL, special groups etc.)

  • correct due dates

  • print due date slips

Fikka: -tested regular +reading room loans with patrons KOT, LUK and items KL, VL, LS / IH

Circulation (borrowing, returning)

Renewing an item

  • one by one

  • all loans



Circulation (borrowing, returning)

Borrowing items with special status (e.g withdrawn, lost, in process, ordered etc.)

  • borrowing

  • renewing

  • returning (popup windows on staff Koha, behaviour with SIP machines)



Circulation (holds)

Placing a request and editing it

  • change pick-up place for title-level holds

  • delete title-level hold

  • make hold for title where some of items are “in order”-status

  • revert a hold and print a new slip

  • place multiple item-level and title-level holds for same patron (check that functions and blocks according to your processes)

  • canceling waiting hold (new feature in 20.11.  with Koha-Opac maybe)



Circulation (holds)

Borrowing with SIP machines, before the request is processed

  • another patron should be able to borrow

  • does the request trap correctly when some item (from same bib) is returned

  • can item be renewed before trapping (if enough copies available on shelf)



Circulation (holds)

Holds in transfer



Circulation (holds)

Holds available for pick up

  • try to borrow item for someone else

  • cancel request (from patron page and from holds page). See that no fees are calculated either way!



Circulation (holds)

Special cases that might differ in libraries due to different service processes and settings, eg, in 3AMK, check this process:

  • all items are available, place a request

  • request is trapped in different branch from pickup location

  • cancel the request while in transit

  • record the behaviour when item arrives to original pickup location (popup messages, statuses in Koha and in Finna)



Circulation (holds)

Check that new holds appear on Holds queue (Varausjono) & Holds to pull (Hyllyvaraukset) -reports

  • Transport cost matrix



Circulation (renewing)

Automatic renewing



Customer information

Adding a patron




Customer information

Making address change in Finna: request comes to Koha for approval and is changed when approved.

Check that correct fields are included in the form, and that everything works
! These have variations in different libraries (example on test-Finna)




Customer infomation

Making changes in Finna regarding (patron can do this without library approval)

  • SMS number (Koha's Primary phone) NB! Not used in 3AMK.

  • email address change in Finna: is changed successfully when patron clicks Save Patron information in Finna.



Customer information

Patron messaging preferences

  • check in Koha that there are no suprises with settings, for different patron groups

  • check that they work in Finna (if you have allowed patrons to modify them)

  • test latest messaging settings and slips: eg. Autorenewal, Hold reminder (if you are using those)



Customer information (login in Finna)

Test ability to login and operating in Finna as a patron, who

  • has more fines than Overdue fines cap (amount), like 15 euros etc.

  • has material onloan with Lost -statuses

  • is debarred

  • account is expired

  • wants to change his/her PIN code (password)



Customer information

Accounting (Money-related) issues are extremely important

  • overdue charges accumulating correctly

  • fines and fees showing correctly

  • adding payment manually
  • buttons and functions: Pay amount, Pay selected, Write off all, Write off selected

    • if unwanted buttons re-appear, check your IntranetUserCSS



Searching (patrons)

  • search patrons with special characters (ä, å, é etc.)

  • scandinavian characters:


Searching (bibliographic data and items)

  • search with item barcode

  • search with ISBN and ISSN, other standard numbers if you are using them

  • search with special characters (ä, å, é etc.)

  • with item barcode:

  • with ISBN, ISMN, 028,  ISSN, standardnumber :

  • with é, ä, ö, å:


Slips/prints

Patron slips

  • issueslip (Patron -print slip -tulosta kuitti)

  • issueqslip (Patron-print quick slip -tulosta tänään lainatut)

Returning slips

  • transferslip (Returning item - transfer to other library)

  • holdslip (varauskuitti)


  • print-slip

  • print quick slip


  • transferslip with/without reservation

  • holdslip



Plugins

Make sure necessary plugins are installed/updated and enabled, e.g. Finna plugin, Tuudo plugin, Label Maker plugin

  • test processes related to plugins, e.g. for spine labels 3-letters printing 

  • /cgi-bin/koha/plugins/plugins-home.pl

  • Label Maker

  • Tuudo plugin


Tools

Batch item modification

  • change items full call number, or something similar

  • remove batch of biblios

  • is job queued and operated as it should, logs afterwards, any error messages


  • changed full call number for several item barcodes. Background job finished.


Reports

Testing your often used reports (daily, weekly, montly reports)

  • document changes

  • report error messages

  • be prepared to edit your reports if database structure has changed (big grin)



CSS

Prefence: IntranetUserCSS

  • see that all CSS-changes you made are still working (e.g. suppressed/hidden fields in intranet) 

  • Necessary "must" CSS code added to test server, and those work. These are library-specific, so we can't pre-test all.


Things that can’t be tested beforehand 

  • Tuudo app: making a new card, renewals

  • self-service machines: item in transit, item in transit with a hold, items with “special” status (e.g. withdrawn etc.)

  • expire reserve charge

  • overduecharges  (can be tested, but the truth reveals itself in production)

  • messages which are possilbly not delivered (bounce messages)

  • Melinda replication

Things that should be saved  from old version before update? 

Just in case? Not sure?

  • own holdings frameworks  

    • 3AMK


  • No labels