https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35972 Bug ID: 35972 Summary: Using Course reserves module for Research table reserves Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Course reserves Assignee: koha-bugs@lists.koha-community.org Reporter: mirjam.vantieghem@etf.edu QA Contact: testopia@bugs.koha-community.org Created attachment 161714 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=161714&action=edit Screenshot of example Research tables on OPAC Our library has research tables and lets patrons (mainly master students working on their thesis) keep items for a longer period on these tables. In order for both library staff and patrons to be able to quickly track down items, we are using the Course reserves module to set a certain research table as temporary location for a certain item. Because tables are not courses, we use a custom patch to have the research tables appear as a separate module on the OPAC. We use the authorized value category DEPARTMENT to distinguish courses from tables. The tables have a separate value "Research tables". Because some of the columns used for the course reserves are not relevant for the tables, we also change the display of these on the OPAC. The following columns are renamed: “Course #” => “Table #” “Instructors” => “Researcher” “Notes” => “Topic” And these columns are hidden: “Dept.”, “Section”, “Term”. Notes: 1) Because of possible privacy issues, we are no longer displaying the name of the researcher, so this column might also be hidden. 2) The topic is optional. Some like to see what others are doing research on. It also helps to know where to look for a book on a certain topic if it is not on the shelf, because keeping the 'table reserves' up to date is a bit of a challenge sometimes, depending on the cooperation of the patron. Ideally this should be a separate module on both the Staff client and the OPAC. It might be called 'Table reserves' if 'Research tables' is too specific. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.