Hi Michael, I didn't see that you received a response to this post. If you did but I missed it, I'm sorry. Defining an additional patron attribute is a valid way of achieving your goal. However if it is the only additional attribute you will have, there are times it might feel cumbersome. For example, when you need to use the parameter in a report, you'll need to join the additional attributes table - by no means a game breaker, but a consideration. An alternative approach that some schools have taken is to use the Sort1 or Sort2 fields in the borrowers table. You can define your classes as a set of Authorised Values for the chosen field if you wish. And if you feel the need, you can re-name the field using a little js. I hope this helps, despite the delay. Bob Birchall Calyx On 21/03/18 11:02, FNPS Library wrote:
Hello everyone,
I work in a primary school library in Melbourne, I'm looking at transitioning our library system from Oliver Junior to Koha. We have set up a test system to play with settings and so on, and I was hoping someone might have an idea for this. I want to be able to group students by class (e.g. 56A, 56B, 56C, etc.) for the purpose of finding them for checkout, and for grouping overdue notices.
I thought of using a custom patron parameter, but I was wondering if anybody had a more elegant solution available.
Thank you,
Kind regards,
Michael Barry.
_______________________________________________ Koha-oz mailing list Koha-oz@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-oz