1) Subject Categories
Subject Categories should be used to generally categorize the ticket.
One and only one label should be given to a ticket.
If none of the specific labels seems to fit, label "other" should be used. Tickets so labelled will be reviewed, and the list of labels amended from time to time. No ticket should remain just "other".
Categories are partly derived from the Koha GUI. Some other labels are added, external integrations mainly. In choosing, you may ask yourself, which module the ticket is mainly about? Where one should go to examine the issue?
| Label | Notes |
| other | If no other label applies properly. |
| acquisitions | |
| administration | In UI, there is: "Koha administration" |
| cataloging | |
| circulation | Includes fees, holds |
| finna | |
| holdings | |
| holds | |
| ILL | including Airut |
| indexing | including Elastic Search. Cf. "search" |
| lists | |
| melinda | including replication |
| patrons | |
| plugins | |
| reports | |
search | Cf. "indexing" |
| serials | |
| SIP | |
| statistics | |
| tools |
2) Organization Labels
These are voluntary and are more for the benefit of the customers. The label may mean, that
- the ticket is about something that only is relevant for one library (or 3AMK), or a few at most, or
- that it was reported by that library even if it is of a more general nature.
Therefore, filtering with the organization name produces a list of tickets that are either peculiar to the library, or created by it.
| 3AMK |
| HAAGA |
| HAMK |
| HANKEN |
| HUMAK |
| JYU |
| ARKISTO |
| FIKKA |
| LAUREA |
| METROPOLIA |
| MPKK |
| STAT |
| TRITONIA |
| VARASTO |
| XAMK |