From 599a0689f728f4fc392634587bde1a6d7c1e2f50 Mon Sep 17 00:00:00 2001 From: Robert Soulliere Date: Tue, 9 Nov 2010 11:18:27 -0500 Subject: [PATCH] Add index terms. --- 1.6/development/actiontriggers.xml | 315 +++++++++++++ 1.6/development/booking.xml | 196 ++++++++ 1.6/intro/releasenotes.xml | 715 +++++++++++++++-------------- 3 files changed, 869 insertions(+), 357 deletions(-) create mode 100644 1.6/development/actiontriggers.xml create mode 100644 1.6/development/booking.xml diff --git a/1.6/development/actiontriggers.xml b/1.6/development/actiontriggers.xml new file mode 100644 index 0000000000..0d532a51b7 --- /dev/null +++ b/1.6/development/actiontriggers.xml @@ -0,0 +1,315 @@ + + + + Action Triggers + + Action Triggers were introduced to Evergreen in 1.6. They allow administrators the ability to set up actions for specific events. They are useful for notification events such as + hold notifications. + + + To access the Action Triggers module, select + + Admin + Local Administration + Notifications / Action triggers + + + You must have Local Administrator permissions to access the Action Triggers module. + You will notice four tabs on this page: Event Definitions, Hooks, + Reactors and Validators. + +
+ Event Definitions + Event Definitions is the main tab and contains the key fields when working with action triggers. These fields include: + + Action Trigger Event Definitions + + + + + + Field + Description + + + + + Owning library + The shortname of the library for which the action / trigger / hook is defined. + + + Name + The name of the trigger event, that links to a trigger event environment containing a set of fields + that will be returned to the Validators / Reactors for processing. + + + Hooks + The name of the trigger for the trigger event. The underlying action_trigger.hook table defines the Fieldmapper + class in the core_type column off of which the rest of the field definitions hang. + + + Enabled + Sets the given trigger as enabled or disabled. This must be set to enabled for the Action trigger to run. + + + Processing Delay + Defines how long after a given trigger / hook event has occurred before the associated action (Reactor) + will be taken. + + + Processing Delay Field + Defines the field associated with the event on which the processing delay is calculated. For example, the processing delay + context field on the hold.capture hook (which has a core_type of ahr) is capture_time. + + + Processing Group Context Field + Used to batch actions based on its associated group. + + + Validators + The subroutines receive the trigger environment as an argument (see the linked Name for + the environment definition) and returns either 1 if the validator is true or 0 + if the validator returns false. + + + Reactors + Links the action trigger to the Reactor. + + + Max Event Validity Delay + Define the threshold for how far back the action_trigger_runner.pl script should reach to generate + a batch of events. + + + +
+ + + Creating New Action Triggers + + From the top menu, select + + Admin + Local Administration + Notifications / Action triggers + + + + Click on the New button. + Select an Owning Library. + Create a unique Name for your new action trigger. + Select the Hook. + Check the Enabled check box. + + Create a unique Name for your new action trigger. + Set the Processing Delay in the appropriate format. Eg. 7 days to run 7 days from the trigger event + or 00:01:00 to run 1 hour after the Processing Delay Context Field. + Set the Processing Delay Context Field and Processing Group Context Field. + Select the Validator, Reactor, Failure Cleanup and Success Cleanup. + + Set the Processing Delay Context Field and Processing Group Context Field. + Enter text in the Template text box if required. These are for email messages. Here is an sample + template for sending 90 day overdue notices: + + + + Once you are satisfied with your new event trigger , click the Save button located at the bottom of the + form + + A quick and easy way to create new action triggers is to clone an existing action trigger. + + Cloning Existing Action Triggers + + Check the check box next to the action trigger you wish to clone + + + Click the Clone Selected on the top left of the page. + + + An editing window with open. Notice that the fields will be populated with content from the cloned action trigger. Edit as necessary and + give the new action trigger a unique Name. + + + Click Save. + + + + Editing Action Triggers + + Check the check box next to the action trigger you wish to delete + + + Click the Delete Selected on the top left of the page. + + + + Before deleting an action trigger, you should consider disabling it through the editing form. This way you can simply enable it if you decide that you would like to use + the action trigger in the future. + + Deleting Action Triggers + + Check the check box next to the action trigger you wish to delete + + + Click the Delete Selected on the top left of the page. + + +
+
+ Hooks + Hooks define the Fieldmapper class in the core_type column off of which the rest of the field definitions hang. + + Hooks + + + + + + Field + Description + + + + + Hook Key + A unique name given to the hook. + + + Core Type + Used to link the action trigger to the IDL class in fm_IDL.xml + + + Description + Text to describe the purpose of the hook. + + + Passive + Indicates whether or not an event is created by direct user action or is circumstantial. + + + +
+ You may also create, edit and delete Hooks but the Core Type must refer to an IDL class in the fm_IDL.xml file. +
+
+ Reactors + Reactors link the trigger definition to the action to be carried out. + + Action Trigger Reactors + + + + + + Field + Description + + + + + Module Name + The name of the Module to run if the action trigger is validated. It must be defined as a subroutine in + /openils/lib/perl5/OpenILS/Application/Trigger/Reactor.pm or as a module + in /openils/lib/perl5/OpenILS/Application/Trigger/Reactor/*.pm. + + + Description + Description of the Action to be carried out. + + + +
+ You may also create, edit and delete Reactors. Just remember that their must be an associated subroutine or module in the Reactor Perl module. +
+
+ Validators + Validators set the validation test to be preformed to determine whether the action trigger is executed. + + Action Trigger Validators + + + + + + + Field + Description + + + + + Module Name + The name of the subroutine in + /openils/lib/perl5/OpenILS/Application/Trigger/Reactor.pm to validate the action trigger. + + + Description + Description of validation test to run. + + + +
+ You may also create, edit and delete Validators. Just remember that their must be an associated subroutine in the Reactor.pm Perl module. +
+
+ Processing Action Triggers + To run the action triggers, an Evergreen administrator will need to run the trigger processing script /openils/bin/action_trigger_runner.pl + . This should be set up as a cron job to run + periodically. + You have several options when running the script: + + : Run the pending events. + : Create hook events + : OpenSRF core config file. Defaults to: + /openils/conf/opensrf_core.xml. + : File containing a JSON Object which describes any hooks that should + use a user-defined filter to find their target objects. Defaults to: /openils/conf/action_trigger_filters.json + : When in process-hooks mode, wait up to [seconds] for the lock file to go away. + Defaults to 3600 (1 hour). + : Define which hooks to create events for. If none are defined, it defaults to the list of hooks defined + in the option. + : Print server responses to stdout (as JSON) for debugging. + : Sets the lock file for the process. + : Show help information. + +
+ + diff --git a/1.6/development/booking.xml b/1.6/development/booking.xml new file mode 100644 index 0000000000..2e61316a16 --- /dev/null +++ b/1.6/development/booking.xml @@ -0,0 +1,196 @@ + + + + Using the Booking Module + + The Evergreen booking module is included in Evergreen 1.6.1.x and above. The following chapter will help staff create reservations for cataloged and non- + bibliographic items; create pull lists for reserved items; capture resources; and pick up and + return reservations. + + + +
+ Creating a Booking Reservation + Only staff members can create reservations. To initiate a reservation, staff can + + search the catalog, + enter a patron record, + or use the booking module. + + + + Search the catalog to create a reservation + + In the staff client, select Search Search the Catalog + + Search for the item to be booked. + Click Submit Search. + A list of results will appear. Select the title of the item to be reserved. + After clicking the title, the record summary appears. Beneath the record summary, + the copy summary will appear. In the Actions column, select Copy Details. + + The Copy Details will appear in a new row. In the barcode column, click the book now + link. + A screen showing the title and barcodes of available copies will appear. + Enter the user’s barcode in the Reserve to patron barcode box. If the patron barcode + does not exist, a pop up box will appear to alert you to the error. After entering the + patron’s barcode, the user’s existing reservations will appear at the bottom of the + screen. + To the right, a section titled, I need this resource... will allow you to set the dates and + times for which the item should be reserved. If the date/time boxes appear in red, + then the date and time set is incorrect. For example, if the time for which the + reservation is set has already passed, the boxes will appear in red. The times must be + set correctly for the reservation to be accomplished. If the item has already been + reserved at the time for which you are trying to reserve the item, then you will receive + an error message. + Finally, select the barcode of the item that you want to reserve. If multiple copies of + the item exist, choose the barcode of the copy that you want to reserve, and click + Reserve Selected. If you do not select a barcode, and you click Reserve Selected, you + will receive an error message. If you do not have a preference, you do not have to + select a barcode, and you may click Reserve Any. One of the barcodes will be pulled + from the list. + An item must have a status of available or reshelving in order to + be targeted for a reservation. If the item is in another status, the reservation will fail. + After you have made the reservation, a message will confirm that the action succeeded. Click OK. + The screen will refresh, and the reservation will appear below the user’s name. + + + + Enter a patron’s record to create a reservation + + Enter the barcode or patron information, and click Search to retrieve the patron’s record. + The match(es) should appear in the right pane. Click the desired patron’s name. In the + left panel, a summary of the patron’s information will appear. Click the Retrieve + Patron button in the right corner to access more options in the patron’s record. + Eight buttons will appear in the top right corner. Select Other Booking + to create, cancel, pick up, and return reservations. + The Copy Details will appear in a new row. In the barcode column, click the book now + link. + A screen showing the title and barcodes of available copies will appear. + Enter the user’s barcode in the Reserve to patron barcode box. If the patron barcode + does not exist, a pop up box will appear to alert you to the error. After entering the + patron’s barcode, the user’s existing reservations will appear at the bottom of the + screen. + To the right, a section titled, I need this resource... will allow you to set the dates and + times for which the item should be reserved. If the date/time boxes appear in red, + then the date and time set is incorrect. For example, if the time for which the + reservation is set has already passed, the boxes will appear in red. The times must be + set correctly for the reservation to be accomplished. If the item has already been + reserved at the time for which you are trying to reserve the item, then you will receive + an error message. + Finally, select the barcode of the item that you want to reserve. If multiple copies of + the item exist, choose the barcode of the copy that you want to reserve, and click + Reserve Selected. If you do not select a barcode, and you click Reserve Selected, you + will receive an error message. If you do not have a preference, you do not have to + select a barcode, and you may click Reserve Any. One of the barcodes will be pulled + from the list. + An item must have a status of available or reshelving in order to + be targeted for a reservation. If the item is in another status, the reservation will fail. + After you have made the reservation, a message will confirm that the action succeeded. Click OK. + The screen will refresh, and the reservation will appear below the user’s name. + + + + Use the booking module to create a reservation + + Select BookingCreate or Edit Reservations + Enter the barcode of the item and click Next. + A screen showing the name of the available resource will appear. + Enter the user’s barcode in the Reserve to patron barcode box. If the patron barcode + does not exist, a pop up box will appear to alert you to the error. After entering the + patron’s barcode, the user’s existing reservations will appear. + To the right, a section titled, I need this resource... will allow you to set the dates and + times for which the item should be reserved. If the date/time boxes appear in red, + then the date and time set is incorrect. For example, if the time for which the + reservation is set has already passed, the boxes will appear in red. The times must be + set correctly for the reservation to be accomplished. If the resource has already been + reserved at the time for which you want to reserve the item, then the item will + disappear. + Finally, select the resource that you want to reserve. If multiple items or rooms exist, + choose the resource that you want to reserve, and click Reserve Selected. If you do + not select a resource, and you click Reserve Selected, you will receive an error + message. If you do not have a preference, you may click Reserve Any, and one of the + resources will be pulled from the list. + After you have made the reservation, a message will confirm that the action + succeeded. Click OK. + The screen will refresh, and the reservation will appear below the user’s name. + + +
+
+ Cancelling a Reservation + Staff members can cancel a patron’s reservation through the Create or Cancel Reservations tab available in a patron’s record. Staff members can also cancel a + reservation immediately after it has been made. + + Enter the patron’s record to cancel a reservation + + Search for and retrieve a patron’s record. + Select OtherBookingCreate or Cancel Reservations. + The existing reservations will appear at the bottom of the screen. + To cancel a reservation, highlight the reservation that you want to cancel. Click Cancel Selected. + A pop-up window will confirm that you cancelled the reservation. Click OK. + The screen will refresh, and the cancelled reservation will disappear. + To the right, a section titled, I need this resource... will allow you to set the dates and + times for which the item should be reserved. If the date/time boxes appear in red, + then the date and time set is incorrect. For example, if the time for which the + reservation is set has already passed, the boxes will appear in red. The times must be + set correctly for the reservation to be accomplished. If the item has already been + reserved at the time for which you are trying to reserve the item, then you will receive + an error message. + + + + Cancel a reservation immediately after it has been made + + Create the reservation. + Follow steps four through six in the section, Enter the patron’s record to cancel a reservation, to cancel the reservation. + The existing reservations will appear at the bottom of the screen. + + +
+
+ Creating a Pull List + Staff members can create a pull list to retrieve items from the stacks. + + To create a pull list, select BookingPull List. + To find a pull list for your library, select a library from the dropdown box adjacent to See pull list for library. + You can decide how many days in advance you would like to select reserved items. Enter the number of days in the box adjacent to Generate + list for this many days hence. For example, if you would like to pull items that are needed today, you can enter 1 in the box, and you will retrieve items that need to be pulled today. + Click Fetch to retrieve the pull list. + The pull list will appear. Click Print to print the pull list. + +
+
+ Capturing Items for Reservations + Staff members can capture items for reservations. + + In the staff client, select BookingCapture Resources. + Enter the barcode of the items to be captured. Click Capture. + A Capture Succeeded message will appear to the right. Information about the item will appear below the message. You can print this + information as a receipt and add it to the item if desired. + +
+
+ Picking Up Reservations + Staff members can help users pick up their reservations. + + In the staff client, select BookingPick Up Reservations + Enter the user’s barcode. Click Go. + The title available for pickup will appear. Highlight the title of the item to pick up, and click Pick Up. + The screen will refresh to show that the patron has picked up the reservation. + +
+
+ Returning Reservations + Staff members can help users return their reservations. + + In the staff client, select BookingReturn Reservations. + You can return the item by patron or item barcode. Choose Resource or Patron, enter the + barcode, and click Go. + A pop up box will tell you that the item was returned. Click OK. + The screen will refresh to show the reservations that remain out and the resources that have been returned. + +
+ + diff --git a/1.6/intro/releasenotes.xml b/1.6/intro/releasenotes.xml index 48802fdee6..e7ab40a72f 100644 --- a/1.6/intro/releasenotes.xml +++ b/1.6/intro/releasenotes.xml @@ -1,357 +1,358 @@ - - - - Release Notes - - - - - 1.6.0.8 - - New features - - Added index for case insensitive barcode searching (1.6.0.7) for speed. - Move to BibTemplateBibTemplate for general title detail display, not just overlay of MVR-based display. - - - - Bug fixes - - Offline transaction timestamp and export fixes. - More configuration interface improvements. - Printing improvements to avoid the dreaded inner print_tree errors. - Fix Google BooksGoogle Books full-text functionality. - User Editor improvements (addresses, appropriate required fields). - - - - - 1.6.0.7 - - New features - - Made barcode searching from the general user search interface case insensitive - - - - Bug fixes - - FIFO Holds OrgholdsFIFO Setting name in the Library Settings Editor did not match that used by the SQL – repaired. - Repaired Authority Record ingest.authority record ingest - Backdating timestamp format bug fixed – patch from James Fournie at SITKA. - Configuration interface bugs addressed (ongoing improvement from 1.6.0.4). - Action/Trigger (notifications, etc) bugs addressed.action triggers - In-Database record merging In-Databaserecord merging bug fixes (indicators, Located URIs) - In-Database hold testing stored procedure bug fixed – patch from John Craig.In-Databasehold testing - - - - - - 1.6.0.6 - - Security - - Address a security vulnerability in open-ils.pcrud that allows retrieval of information beyond the bounds of the permissions for - the targeted objects. - - - - Bug fixes - - Remove a call to a non-existent method. - Add debugging messages to the action-trigger script and server code - action triggers - - - - 1.6.0.5 - - New features - - Patch from James Fournie to add a setting for first-in, first-out (FIFO) holds resolution so that items checked in will be assigned to holds - by request date first, rather than proximity.holdsFIFO - - - - Bug fixes - - Patch from Dan Wells to enable the bookbag menu to show up in Craftsman skin. - Patch from Bill Ott to add missing apostrophe in rdetail.js. - Fix for report editor parameters not consistently showing up. - Log bib search timeouts. - - - - - - 1.6.0.4 - - New features - - Patch from Dan Wells to add an org-unit setting to restrict renewals when the item in question is needed to fulfill a hold. - - - - Bug fixes - - Patch from Jason Stephenson to allow the EVERYTHING permission in permission.usr_has_perm_at_nd. - Patch from Warren Layton to remove a debugging alert in the permission creation interface. - Patch from Warren Layton to sort Z39.50 servers in Z39.50 import interface.Z39.50 - Patch from Galen Charlton to prevent legacy 852 fields from being exported during bib+holdings export. - Patch from Galen Charlton to prevent one bad MARC record from spoiling the rest of the export. - Patch from Galen Charlton to remove empty XML elements and control fields when ingesting a bib record. - Patch from Galen Charlton. This patch adds additional calls to escape_xml to handle cases where patron or library data could contain - ampersand or other characters that need to be converted to entities. Issue discovered by Bibliomation; patch includes contributions by Ben Ostrowsky. - Enable display of barcodes in brief circulation interface even when patron has no middle name (problem diagnosed by - Bill Ott). - Correct the calculation of patron bills. - Fix parsing of colons in search phrases. - Fix handling of horizontal patron summary setting. - Various fixes for server administration interfaces. - Correct date handling in My Account interface. - Prevent an exception from being thrown when a standing penalty is removed. - Fix ISSN quicksearch (bug reported by Dan Wells). - Prevent colons from being incorrectly inserted into titles in search results display. - Fix survey interface in patron editor to enable it to save results correctly. - Corrections in in-database circulation: enable check-out and renewal of pre-cataloged items, process non-cataloged items.in-databasecirculation - Correct Unicode handling in SRU/Z39.50 server.Z39.50Unicode - - - - - 1.6.0.3 - - Bug fixes - - Patch from Dan Wells to address a regression in the Reshelving-to-Available method call. - Patch from Warren Layton of NRCAN to address a regression in date calculation code. - Fix for offline identification requirement (relaxed to match on-line patron registration). - - - - - 1.6.0.2 - - New features - - Support indexing normalization and search of ratio-like strings. - Support specific-index searching via the basic search dropdown. - - - - Bug fixes - - Fix for search bug introduced in 1.6.0.1 which primarily effected Z39.50 searches against Evergreen.Z39.50 - Fix for offline patron blocked list generation (Patch from Joe Atzberger). - General translation and internationalization improvements. - Force at least one non-system billing type to exist (Identified by Dan Wells). - - - - - 1.6.0.1 - - Bug fixes - - Overdue notice XML normalization and encoding fixes.noticesoverdue - Remove cosmetic issues with Offline Mode.offline mode - Backport compatibility-improved triggers for summary data collection. - - (fixed super-simple record extract view issues for isbn and issn) - - - Interface fixes for Self Check.self checkoverdue - - (prevent login of patrons who are marked as invalid) - - - General grid-related interface cleanups. - - - (fixed pixel and alignment issues in table views accessible from admin settings) - - - String translation interface fix – translated strings can be removed. - - (the translation windows now perform removals correctly) - - - Command-line data extraction script fixes (Galen Charlton). - - (improved batch export) - - - Fixed billing time stamp calculation. - - (e.g. a book that circulates for whole days that is technically due at 3pm doesn't accrue fines until after the library is - closed) - - - Fix for searches containing colons but no command tag. - - (the : is no longer assumed to be an index specification so title searches for Homeward Bound: the Incredible Journey - will return results) - - - Fix for Z39.50 searches containing diacritical marks (Dan Scott).Z39.50 - - (the SRU is now better at detecting incoming encoding) - - - Horizontal user summary display fix in the Checkout entry point. - Return of Shadowed Record styling in the staff client for records with no items or no items at this location (Bill Ott). - Holdings import fixes (Dan Wells) (see changeset 15353). - - (Found and fixed the Vandelay bug that manifested based on log in type.) - - - Holdings import fixes (Dan Wells) (see changeset 15353). - Fixed an error that occurred when renewing multiple items at once in Items Out - - - - New features (front end) - - French translation updates. - Several new translations: - - Russian (from Tigran Zargaryan) - Czech (forward-ported from 1.4) - British English (submitted via Launchpad) - Spanish (submitted via Launchpad) - Brazilian Portuguese (submitted via Launchpad) - languages - - More places to access Record Buckets in the staff clientrecord buckets - Virtual due date for non-cataloged circulations honors closed dates - Differentiated messages for inactive vs. non-existent users. - - (error messages in patron OPAC log in are now different for inactive patrons versus bad log in (typo)/non-existent user) - - - - - - New features (server/administration) - - Action/Trigger initiator script.action triggers - - (1.6.0.1 includes the default script to initiate system scheduling for action/trigger events - for use in cron jobs) - - - Improved MFHD (serials) import script. - - (improved instructions in the read me files and relaxed database constraints) - - - SIP2 configurable encoding support.SIP - SIP1 renew-or-checkout support for some 3M equipment which support older SIP protocols. - Updated Linux distribution support. - Automatic update of OpenSRF support files when OpenSRF is upgraded. - OpenSRF - - - - Features from 1.6.0.0 - - - New features (front end) - - Added insert copy above (CTRL up) and insert - copy below (CTRL down) functionality in the MARC Editor. - Summary editing in MARC Format for Holdings Data - BibTemplate OPAC templating – Any field from any version of a record that Evergreen can deliver, with or without embedded holdings,BibTemplate - is now available for display using a simple template language which is further extended with basic JavaScript. - - Template customization is now supported that allows specific data fields to be pulled from the MARC and displayed in the OPAC. - Examples would be: added author, alternate title, subject links, and URI data. - - - BibTemplate OPAC templating – Any field from any version of a record that Evergreen can deliver, with or without embedded holdings, - is now available for display using a simple template language which is further extended with basic JavaScript. - - Template customization is now supported that allows specific data fields to be pulled from the MARC and displayed in the OPAC. - Examples would be: added author, alternate title, subject links, and URI data. - - - Located URIs – Adding an 856$9 containing the short name of a location will restrict search and display of entirely electronic records - (those with no physical copies) to the location named. - - In other words, the ability to restrict record visibility to a specific location or set of - locations in the same way as copies but without creating dummies. - Since there is no physical location, however, this does affect advanced searches wherein the shelving location limiter is used. - (improved instructions in the read me files and relaxed database constraints) - - - SRU(search/retrieval via url) and Z39.50 searches can now be scoped to specific locations.Z39.50 - - As of Evergreen 1.6, you can append an optional organization unit shortname for search scoping purposes, and you - can also append /holdings if you want to expose the holdings for any returned records. So your zurl could be - http://dev.gapines.org/opac/extras/sru/BR1/holdings to limit the search scope to BR1 and its children, and to expose its holdings. - - - As a benefit of the URI work, Z39.50 now supports a holdings record format. - Improvements in Fixed Field handling within the MARC Editor. - Staff-placed holds for patrons follow patron settings more closely (no longer pull notification preferences from staff settings) – - Patch from Jeff Godin of TADL. - Improved default configuration for LoC Z39.50 target - added support for required truncation specific to LoC. - Added a new default indexing definition for all subjects which will return more results when subject searching in the OPAC. - Many new server configuration interfaces for functions such as circulation policies, hold policies, and notifications. - Added time granularity display to Patron Items Out screen in the Staff Client. Due time now displays along with due date. - Added RefWorks (online bibliographic management program) export capability.RefWorks - Zotero compatability improvements (MODS namespacing). - Zotero - For more information on MODS, see this page. - MODS - - Ability to import holdings via the standard Record Importer (Vandelay).Vandelay - Google Book Preview support as added-content - Improvements made to cloned patron search; fixing issues with records not returning due to cloned fields. - Acquisitions Preview includes a sneak peek at the preliminary work for manual funding management, PO creation, cataloging and receiving processes. - These are functional but are not intended for insertion into current workflows. This feature was specifically included to solicit feedback from - the community on this important feature. - - - - - New features (server/administration) - - Event Triggers – An entirely new subsystem for automatically running arbitrary, user-defined reaction code when presented with an ILS event - defined by the user. Notifications, delayed actions, acquisitions, and many other systems will make use of this new infrastructure. - - Ability to set pre-due and overdue e-mail notices from the Staff Client. - Auto-marking items as lost after specific overdue period. - Makes it easier to add new data to notices. - Can be used for generating and creating delays for the sending of hold pickup notices. - These settings are configurable from the Staff Client per branch or globally. - - - Formal support for Postgresql 8.3. - Dojo profile build specific to Evergreen, increasing load speed dramatically for the OPAC and Staff Clients. - Staff Client interfaces for defining circulation and hold policies from the Admin menu. - - Please note that this represents a change from previous versions of Evergreen and for new clients it is recommended to - use this interface, for. - - - Formal support for IE8, including a bug fix where titles with the “@” symbol would display as a http link. - Spaces in user names are being deprecated as they can cause authentication failure -CamelCase will be supported from this point forward. - Supercat: added support for returning records in Federal Geographic Data Committee (FGDC) Content Standard for - Digital Geospatial Metadata (CSDGM) format.Digital Geospatial Metadata (CSDGM) - Increased the re-shelving-complete process speed; making the flipping process from re-shelving to available much faster – - on suggestion from Bill Ott of GRPL. - Reporter fix to the display of ISBN and ISSN in some reports, and in some environments (environments which had newer versions - of Perl database drivers that affected some reports). - Bug fixes for Server Administration interfaces such as hours of operation, and generally improving speed of all the SA interfaces. - Removed Spanish translation set from the build environment as no Spanish translation has been contributed to date. - Internationalization improvements in the default skin; there are less English-only strings. - Improved output handling for unAPI services; important for popular add-ons like Zotero. - Improved handling of day-granular circulations, and their interaction with penalties – i.e. For a 7 day - circulating item that is checked out at 9am on Sunday, it is not due until closing on the following Saturday.. - Evergreen will notify that printer setups need to be checked at Staff Client upgrade time. - - - - + + + + Release Notes + + + + + 1.6.0.8 + + New features + + Added index for case insensitive barcode searching (1.6.0.7) for speed. + Move to BibTemplateBibTemplate for general title detail display, not just overlay of MVR-based display. + + + + Bug fixes + + Offline transaction timestamp and export fixes. + More configuration interface improvements. + Printing improvements to avoid the dreaded inner print_tree errors. + Fix Google BooksGoogle Books full-text functionality. + User Editor improvements (addresses, appropriate required fields). + + + + + 1.6.0.7 + + New features + + Made barcode searching from the general user search interface case insensitive + + + + Bug fixes + + FIFO Holds OrgholdsFIFO Setting name in the Library Settings Editor did not match that used by the SQL – repaired. + Repaired Authority Record ingest.authority record ingest + Backdating timestamp format bug fixed – patch from James Fournie at SITKA. + Configuration interface bugs addressed (ongoing improvement from 1.6.0.4). + Action/Trigger (notifications, etc) bugs addressed.action triggers + In-Database record merging In-Databaserecord merging bug fixes (indicators, Located URIs) + In-Database hold testing stored procedure bug fixed – patch from John Craig.In-Databasehold testing + + + + + + 1.6.0.6 + + Security + + Address a security vulnerability in open-ils.pcrud that allows retrieval of information beyond the bounds of the permissions for + the targeted objects. + + + + Bug fixes + + Remove a call to a non-existent method. + Add debugging messages to the action-trigger script and server code + action triggers + + + + 1.6.0.5 + + New features + + Patch from James Fournie to add a setting for first-in, first-out (FIFO) holds resolution so that items checked in will be assigned to holds + by request date first, rather than proximity.holdsFIFO + + + + Bug fixes + + Patch from Dan Wells to enable the bookbag menu to show up in Craftsman skin. + Patch from Bill Ott to add missing apostrophe in rdetail.js. + Fix for report editor parameters not consistently showing up. + Log bib search timeouts. + + + + + + 1.6.0.4 + + New features + + Patch from Dan Wells to add an org-unit setting to restrict renewals when the item in question is needed to fulfill a hold. + + + + Bug fixes + + Patch from Jason Stephenson to allow the EVERYTHING permission in permission.usr_has_perm_at_nd. + Patch from Warren Layton to remove a debugging alert in the permission creation interface. + Patch from Warren Layton to sort Z39.50 servers in Z39.50 import interface.Z39.50 + Patch from Galen Charlton to prevent legacy 852 fields from being exported during bib+holdings export. + Patch from Galen Charlton to prevent one bad MARC record from spoiling the rest of the export. + Patch from Galen Charlton to remove empty XML elements and control fields when ingesting a bib record. + Patch from Galen Charlton. This patch adds additional calls to escape_xml to handle cases where patron or library data could contain + ampersand or other characters that need to be converted to entities. Issue discovered by Bibliomation; patch includes contributions by Ben Ostrowsky. + Enable display of barcodes in brief circulation interface even when patron has no middle name (problem diagnosed by + Bill Ott). + Correct the calculation of patron bills. + Fix parsing of colons in search phrases. + Fix handling of horizontal patron summary setting. + Various fixes for server administration interfaces. + Correct date handling in My Account interface. + Prevent an exception from being thrown when a standing penalty is removed. + Fix ISSN quicksearch (bug reported by Dan Wells). + Prevent colons from being incorrectly inserted into titles in search results display. + Fix survey interface in patron editor to enable it to save results correctly. + Corrections in in-database circulation: enable check-out and renewal of pre-cataloged items, process non-cataloged items.in-databasecirculation + Correct Unicode handling in SRU/Z39.50 server. + Z39.50Unicode + + + + + 1.6.0.3 + + Bug fixes + + Patch from Dan Wells to address a regression in the Reshelving-to-Available method call. + Patch from Warren Layton of NRCAN to address a regression in date calculation code. + Fix for offline identification requirement (relaxed to match on-line patron registration). + + + + + 1.6.0.2 + + New features + + Support indexing normalization and search of ratio-like strings. + Support specific-index searching via the basic search dropdown. + + + + Bug fixes + + Fix for search bug introduced in 1.6.0.1 which primarily effected Z39.50 searches against Evergreen.Z39.50 + Fix for offline patron blocked list generation (Patch from Joe Atzberger). + General translation and internationalization improvements. + Force at least one non-system billing type to exist (Identified by Dan Wells). + + + + + 1.6.0.1 + + Bug fixes + + Overdue notice XML normalization and encoding fixes.noticesoverdue + Remove cosmetic issues with Offline Mode.offline mode + Backport compatibility-improved triggers for summary data collection. + + (fixed super-simple record extract view issues for isbn and issn) + + + Interface fixes for Self Check.self checkoverdue + + (prevent login of patrons who are marked as invalid) + + + General grid-related interface cleanups. + + + (fixed pixel and alignment issues in table views accessible from admin settings) + + + String translation interface fix – translated strings can be removed. + + (the translation windows now perform removals correctly) + + + Command-line data extraction script fixes (Galen Charlton). + + (improved batch export) + + + Fixed billing time stamp calculation. + + (e.g. a book that circulates for whole days that is technically due at 3pm doesn't accrue fines until after the library is + closed) + + + Fix for searches containing colons but no command tag. + + (the : is no longer assumed to be an index specification so title searches for Homeward Bound: the Incredible Journey + will return results) + + + Fix for Z39.50 searches containing diacritical marks (Dan Scott).Z39.50 + + (the SRU is now better at detecting incoming encoding) + + + Horizontal user summary display fix in the Checkout entry point. + Return of Shadowed Record styling in the staff client for records with no items or no items at this location (Bill Ott). + Holdings import fixes (Dan Wells) (see changeset 15353). + + (Found and fixed the Vandelay bug that manifested based on log in type.) + + + Holdings import fixes (Dan Wells) (see changeset 15353). + Fixed an error that occurred when renewing multiple items at once in Items Out + + + + New features (front end) + + French translation updates. + Several new translations: + + Russian (from Tigran Zargaryan) + Czech (forward-ported from 1.4) + British English (submitted via Launchpad) + Spanish (submitted via Launchpad) + Brazilian Portuguese (submitted via Launchpad) + languages + + More places to access Record Buckets in the staff clientrecord buckets + Virtual due date for non-cataloged circulations honors closed dates + Differentiated messages for inactive vs. non-existent users. + + (error messages in patron OPAC log in are now different for inactive patrons versus bad log in (typo)/non-existent user) + + + + + + New features (server/administration) + + Action/Trigger initiator script.action triggers + + (1.6.0.1 includes the default script to initiate system scheduling for action/trigger events - for use in cron jobs) + + + Improved MFHD (serials) import script. + + (improved instructions in the read me files and relaxed database constraints) + + + SIP2 configurable encoding support.SIP + SIP1 renew-or-checkout support for some 3M equipment which support older SIP protocols. + Updated Linux distribution support. + Automatic update of OpenSRF support files when OpenSRF is upgraded. + OpenSRF + + + + Features from 1.6.0.0 + + + New features (front end) + + Added insert copy above (CTRL up) and insert + copy below (CTRL down) functionality in the MARC Editor. + Summary editing in MARC Format for Holdings Data + BibTemplate OPAC templating – Any field from any version of a record that Evergreen can deliver, with or without embedded holdings,BibTemplate + is now available for display using a simple template language which is further extended with basic JavaScript. + + Template customization is now supported that allows specific data fields to be pulled from the MARC and displayed in the OPAC. + Examples would be: added author, alternate title, subject links, and URI data. + + + BibTemplate OPAC templating – Any field from any version of a record that Evergreen can deliver, with or without embedded holdings, + is now available for display using a simple template language which is further extended with basic JavaScript. + + Template customization is now supported that allows specific data fields to be pulled from the MARC and displayed in the OPAC. + Examples would be: added author, alternate title, subject links, and URI data. + + + Located URIs – Adding an 856$9 containing the short name of a location will restrict search and display of entirely electronic records + (those with no physical copies) to the location named. + + In other words, the ability to restrict record visibility to a specific location or set of + locations in the same way as copies but without creating dummies. + Since there is no physical location, however, this does affect advanced searches wherein the shelving location limiter is used. + (improved instructions in the read me files and relaxed database constraints) + + + SRU(search/retrieval via url) and Z39.50 searches can now be scoped to specific locations.Z39.50 + + As of Evergreen 1.6, you can append an optional organization unit shortname for search scoping purposes, and you + can also append /holdings if you want to expose the holdings for any returned records. So your zurl could be + http://dev.gapines.org/opac/extras/sru/BR1/holdings to limit the search scope to BR1 and its children, and to expose its holdings. + + + As a benefit of the URI work, Z39.50 now supports a holdings record format. + Improvements in Fixed Field handling within the MARC Editor. + Staff-placed holds for patrons follow patron settings more closely (no longer pull notification preferences from staff settings) – + Patch from Jeff Godin of TADL. + Improved default configuration for LoC Z39.50 target - added support for required truncation specific to LoC. + Added a new default indexing definition for all subjects which will return more results when subject searching in the OPAC. + Many new server configuration interfaces for functions such as circulation policies, hold policies, and notifications. + Added time granularity display to Patron Items Out screen in the Staff Client. Due time now displays along with due date. + Added RefWorks (online bibliographic management program) export capability.RefWorks + Zotero compatability improvements (MODS namespacing). + Zotero + For more information on MODS, see this page. + MODS + + Ability to import holdings via the standard Record Importer (Vandelay).Vandelay + Google Book Preview support as added-content + Improvements made to cloned patron search; fixing issues with records not returning due to cloned fields. + Acquisitions Preview includes a sneak peek at the preliminary work for manual funding management, PO creation, cataloging and receiving processes. + These are functional but are not intended for insertion into current workflows. This feature was specifically included to solicit feedback from + the community on this important feature. + + + + + New features (server/administration) + + Event Triggers – An entirely new subsystem for automatically running arbitrary, user-defined reaction code when presented with an ILS event + defined by the user. Notifications, delayed actions, acquisitions, and many other systems will make use of this new infrastructure. + + Ability to set pre-due and overdue e-mail notices from the Staff Client. + Auto-marking items as lost after specific overdue period. + Makes it easier to add new data to notices. + Can be used for generating and creating delays for the sending of hold pickup notices. + These settings are configurable from the Staff Client per branch or globally. + + + Formal support for Postgresql 8.3. + Dojo profile build specific to Evergreen, increasing load speed dramatically for the OPAC and Staff Clients. + Staff Client interfaces for defining circulation and hold policies from the Admin menu. + + Please note that this represents a change from previous versions of Evergreen and for new clients it is recommended to + use this interface, for. + + + Formal support for IE8, including a bug fix where titles with the “@” symbol would display as a http link. + Spaces in user names are being deprecated as they can cause authentication failure -CamelCase will be supported from this point forward. + Supercat: added support for returning records in Federal Geographic Data Committee (FGDC) Content Standard for + Digital Geospatial Metadata (CSDGM) format.Digital Geospatial Metadata (CSDGM) + Increased the re-shelving-complete process speed; making the flipping process from re-shelving to available much faster – + on suggestion from Bill Ott of GRPL. + Reporter fix to the display of ISBN and ISSN in some reports, and in some environments (environments which had newer versions + of Perl database drivers that affected some reports). + Bug fixes for Server Administration interfaces such as hours of operation, and generally improving speed of all the SA interfaces. + Removed Spanish translation set from the build environment as no Spanish translation has been contributed to date. + Internationalization improvements in the default skin; there are less English-only strings. + Improved output handling for unAPI services; important for popular add-ons like Zotero. + Improved handling of day-granular circulations, and their interaction with penalties – i.e. For a 7 day + circulating item that is checked out at 9am on Sunday, it is not due until closing on the following Saturday.. + Evergreen will notify that printer setups need to be checked at Staff Client upgrade time. + + + + -- 2.43.2