HTTPS clone URL
Subversion checkout URL
Commits on Feb 14, 2011
This patch causes a display of the total number of holds as well as the number of active holds in the OPAC result and detail pages. This information is displayed to the right of the Place Hold link for each bib record. Active holds are considered holds that are not currently suspended. Finally, the syspref OPACXSLTResultsAvailabilityDisplay was also added. This syspref defaults to ON, and will show the availablity section of the bib record in OPAC results when XSLT is being used.
Commits on Jan 25, 2011
Story initially reported an inconsitency in the OPAC, but one existed in the staff client as well. Now only item specific holds should be displayed as 'On Hold' in the OPAC and staff clients.
Commits on Jun 30, 2010
Commits on Jun 28, 2010
This is an attempt to extract the LLEK course reserves from their code base. MySQL changes are as follows... DROP TABLE IF EXISTS `courses`; CREATE TABLE `courses` ( `course_id` INT(11) NOT NULL auto_increment, `department` VARCHAR(20), -- req, auth value `course_number` VARCHAR(255), -- req, free text `section` VARCHAR(255), -- free text `course_name` VARCHAR(255), -- req, free text `term` VARCHAR(20), -- req, auth value `staff_note` mediumtext, `public_note` mediumtext, `students_count` VARCHAR(20), `course_status` enum('enabled','disabled') NOT NULL DEFAULT 'enabled', `timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP, PRIMARY KEY (`course_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; DROP TABLE IF EXISTS `instructor_course_link`; CREATE TABLE `instructor_course_link` ( `instructor_course_link_id` INT(11) NOT NULL auto_increment, `course_id` INT(11) NOT NULL default 0, `instructor_borrowernumber` INT(11) NOT NULL default 0, PRIMARY KEY (`instructor_course_link_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; DROP TABLE IF EXISTS `course_reserves`; CREATE TABLE `course_reserves` ( `course_reserve_id` INT(11) NOT NULL auto_increment, `course_id` INT(11) NOT NULL, `itemnumber` INT(11) NOT NULL, `staff_note` mediumtext, `public_note` mediumtext, `itemtype` VARCHAR(10) default NULL, `ccode` VARCHAR(10) default NULL, `location` varchar(80) default NULL, `branchcode` varchar(10) NOT NULL, `original_itemtype` VARCHAR(10) default NULL, `original_ccode` VARCHAR(10) default NULL, `original_branchcode` varchar(10) NOT NULL, `original_location` varchar(80) default NULL, `timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP, PRIMARY KEY (`course_reserve_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; INSERT INTO `authorised_values` ( category, authorised_value, lib ) values ( 'DE PARTMENT', 'Default', 'Default Department' ); INSERT INTO `authorised_values` ( category, authorised_value, lib ) values ( 'TE RM', 'Default', 'Default Term' ); INSERT INTO permissions (module_bit,code,description) VALUES ( 1, 'manage_course s', 'View, Create, Edit and Delete Courses'), ( 1, 'put_coursereserves', 'Basic Course Reserves access, user can put items on course reserve'), ( 1, 'remove_co ursereserves', 'Take items off course reserve'), ( 1, 'checkout_via_proxy', 'Che ckout via Proxy'), ( 4, 'create_proxy_relationships', 'Create Proxy Relationship s'), ( 4, 'edit_proxy_relationships', 'Edit Proxy Relationships'), ( 4, 'delete_ proxy_relationships', 'Delete Proxy Relationships'); Additionally added the following to /etc/zebradb/biblios/etc/bib1.att... att 9016 Course att 9017 Instructor att 9018 srcnum There still appear to be some small bugs, but I think in this current version, it's good enough for in-house and/or client testing.
Commits on Jun 21, 2010
Previously XSLT translation was only available for the OPAC. Koha community did provide a patch that sort of enabled XSLT for the staff bib details page. This was only partially functional. This patch cleans up the various pieces of code as well as adds staff side XSLT capability to the search results page as well as details page. Another patch will alter the staff XSL file to include certain MARC 245 subfields.
Commits on Apr 13, 2010
OPAC suppression was already available for a bib record, but not on an individual item. This patch tries to create this functionality. In order to accomplish this, I ended up adding a suppress field to the items table by running the following SQL... ALTER TABLE items ADD suppress tinyint(1) NOT NULL DEFAULT 0 AFTER wthdrawn; A new authorised value named I_SUPPRESS was also created with a binary option of 0 - Not Suppressed (blank in authorised_value.description) | 1 - Suppressed. The items.suppress field was then linked to the MARC 952$i field and the I_SUPPRESS authorised value. In addition, I added the following to the three Zebra configuration files... ZEBRADIR=~/koha-dev/etc/zebradb $ZEBRADIR/biblios/etc/bib1.att:att 8033 suppress $ZEBRADIR/ccl.properties:suppress 1=8033 $ZEBRADIR/marc_defs/marc21/biblios/record.abs:melm 952$i suppress,suppress:n The Koha maintenance utility sync_items_in_marc_bib.pl also needed to be run to sync the items table to the MARC record. Finally, an index rebuild (i.e., rebuild_zebra.pl) was performed. I'm not positive if at least one item needed to be suppressed for the indexing to work correctly; however, for testing, I did set at least one item to be suppressed before I ran rebuild_zebra.pl.
Commits on Mar 5, 2010
The logic with regards to how reserved items are displayed was changed. Before unattached items were loosely attached to result in a display of 'On hold'. This was changed to display only 'On hold' for attached items. A disclaimer for the total number of holds has also been added to the detail pages.
Commits on Mar 4, 2010
* immediately changes an item status to "On hold" when a hold is placed on it. Prior to this, the "On hold" status would only show up when a check-in occurred to a held item. * Allowed hold from search list even if item is already on hold. * When a hold is placed on a multiple item bib, the previous code would indicate that all items of that bib were on hold. This was the case when a next available hold was placed because a specific item was not tied to that hold. This code tricks the display into temporarily associating only the current number of holds versus the number of total items. * Do not allow a hold to display on a lost item when non specific item hold is placed. This accounts for cases when an item is lost and a "next available" hold is placed. Previously it would try to place a hold on a lost item. This patch should hopefully fix that. * Changed the status message in staff detail screen when an item is reserved but not yet waiting to be picked up. * Added on-hold status to hitlist display for grouped results. * Ported this feature to XSLT results
Commits on Jan 21, 2010
Commits on Aug 27, 2009
First of all, items.otherstatus was coded to become NULL on the check in of a particular item that had NOT NULL status. Second, the holdsfilled column in the itemstatus table was not being used to trigger hold unavailability. This was corrected.
Commits on Aug 19, 2009
Previously the only way to change item status was via the moredetail template. I've added this option to the edit and add option pages as well. The detail and moredetail pages were also not displaying the new item status. It was, however, successfully showing up in the catalogue search pages. So additional code was added to display alternate item status in the detail pages. Finally, examined if holds were allowed on said item status and display accordingly.
Commits on May 1, 2009
dlbptfs authored Galen Charlton committed
If the items.location field was NULL, then the current SQL query would produce no results. I have turned this into a conditional block that removes the location condition in the query if the location is not specified. In addition, there was a small change to opac-detail.tmpl that changed Library to Shelves when the shelf browser was open. This removes a potential redundant Library Library display if Library is contained in the starting_homebranch. Signed-off-by: Galen Charlton <firstname.lastname@example.org>