http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10612 --- Comment #19 from Nora Blake <nblake@masslibsystem.org> --- Hello, I am the force behind this whole development and I can tell you what our situation is and what we are trying to accomplish. We have many schools in our consortium. They want to be able to remove classes of students each year after they graduate. Our schools do not treat their patron accounts in the same way that they treat books, so they do not have the student barcodes on hand or available in the same way that they can grab a stack of books and scan them all in to the batch item deletion tool. They need to be able to search for a group of patrons by a common piece of information stored in a single field. In our case, we store year of graduation information in either the "sort 1" or "sort 2" field of the patron record. They need to be able to search for that common piece of information easily, obtain a grouping of patrons from the search and then decide whether they want to delete the whole class of kids from the system (probably the most common event we will have) OR change their patron type from "student" to "alumni" or something else. They don't use patron card numbers to find patron accounts. Often they checkout based on a name search or they may scan the kid's school ID, but they won't have those ID cards on hand when it comes time to delete them from the system. So they need to be able to perform a search for the "class of 2014" or "2014" or "grade 12," depending on what they have entered in the child's record and get a group of patrons together in one place so they can then delete them (most common need) or modify their patron type or modify their year of graduation if several are being held back or do something else that I can't think of. I hope this helps clarify why Kyle is looking to do what he is proposing. Thanks, Nora Blake -- You are receiving this mail because: You are watching all bug changes.