From: rsoulliere Date: Thu, 24 Nov 2011 19:50:30 +0000 (-0500) Subject: Add release notes for 2.1. X-Git-Tag: sprint4-merge-nov22~4203^2~103^2~6 X-Git-Url: https://old-git.evergreen-ils.org/?a=commitdiff_plain;h=76ff17b63b7ce729a52c44be87e0f1312aa38096;p=working%2FEvergreen.git Add release notes for 2.1. --- diff --git a/intro/release_notes.xml b/intro/release_notes.xml new file mode 100644 index 0000000000..da718cae7a --- /dev/null +++ b/intro/release_notes.xml @@ -0,0 +1,818 @@ + + + + 2.1 Release Notes + + + +Installation enhancements + + + +eg_db_config.pl now has a --create-database option to automatically create + the database and add the required contrib modules/extensions, rather than + requiring users to carry out a number of error-prone manual steps. + + + + +The OpenILS Perl modules are now installed in the system Perl package + directories. In prior versions, they were typically installed in + /openils/lib/perl5. + + + + +README is now the single source of install instructions + + + + + +Administration enhancements + + + +Automatic client updates: It is now possible to build staff clients that, + when they connect to the Evergreen server, automatically check to see if + the staff client has been updated. If so, the staff client can download just + the files that have been updated and replace those files in the existing + staff client. + + + + +Printing subsystem: Changes to the staff client should improve the print + functionality (both speed and likelihood of success). + + + + +To protect against exploits between a shared staff client session via + operator change, add the requirement for the DEBUG_CLIENT permission to + invoke debugging functions such as the Javascript Shell or DOM Inspector + in the staff client. + + + + + +Cataloging enhancements + + + +Unified copy / call number editor: The default holdings maintenance interface + now enables cataloguers to edit copies and call numbers on a single screen. + + + + +Call number prefixes and suffixes: While previous releases of Evergreen + supported the automatic prepending or appending of prefixes and suffixes to + call numbers based on their shelving location, the functionality was limited + primarily to printing spine labels. As of 2.1, you also have the option to + assign prefixes or suffixes for individual call numbers; these will be + displayed in the public catalogue and other interfaces, but prefixes in + particular do not affect shelf browsing, which is based entirely on the + label. + + + + +Bibliographic parts: This feature adds the ability to designate specific + "part" roles for the items attached to a given bibliographic record, such + that a user can place holds on a specific kind of item without limiting it + to an individual item. For example, libraries may assign parts to each DVD + in a season of a popular TV show; or to individual volumes of an + encyclopedia. This feature also introduces "part holds". + + + + +Conjoined items: This feature adds the ability to associate a single barcode + with multiple bibliographic records, so that the availability of those + records is updated based on that copy. For example, libraries may make an + electronic reader available for loan that is preloaded with 1000 electronic + books; they can add 1000 bibliographic records to the library system and + associate them all with a single barcode, so that when the electronic reader + is signed out, the availability for all 1000 records changes to "Checked out". + + + + + +Circulation improvements + + + +Transfer selected holds to a different title: It is now possible to select + multiple holds on a given title and transfer them to a different title. + Use case: Your library acquires another copy of "Pride and Prejudice and + Zombies", but as it is a new edition it must be cataloged as a new + bibliographic record; however, you would like to spread out some of the holds + queue from your current edition to the new edition. + + + + +Mark patron as exempt from billing collections: It is now possible to mark a + patron as being exempt from being sent to collections. + + + + +Hold-driven recalls: It is now possible to define a loan + period threshold (such as 60 days) so that if a hold is placed on an item with + a loan period beyond that threshold, the system will automatically shorten the + loan period to a specified value; change the fine rules; and send email + notification to the person who currently holds the item saying "A hold has + been placed on this item, get it back before <new_due_date>". + + + + +Weighting of the individual fields of the in-database circulation and holds + rules can now be configured, rather than using hard-coded values. This allows + the importance of each field to be adjusted as needed through the circulation + matrix weighting, hold matrix weighting, and weighting associations settings. + + + + +The in-database circulation rules support "fall-through" wherein some + information can be left out of more specific rules and filled in from less + specific rules. For example, disabling fines for staff could be accomplished + with a single rule setting only the fine rate and/or max fine rules, without + having to duplicate all duration related rules in the system. + + + + +Grace periods are now stored in the database and set via circulation rules, + rather than passed into the fine generation code, and can thus differ between + different rules. They are also no longer based on a number of fine intervals, + but are instead defined by their own specific interval. This can eliminate + problems with closed date interpretation during grace periods. + + + + + +Public interface improvements + + + +Spell-checking suggestions are now case-insensitive, to avoid generating + terms which would yield the same result set. + + + + +Part holds: patrons are guided to select a specific part if they are + placing a hold on a bibliographic record that has parts assigned to its + copies. + + + + +Located URI visibility: Located URIs (856 fields with a subfield $9 + specifying the shortname of the owning library) now show up in a search with + a context library of its owning library or below. For example, a Located URI + with an owner of SYS1 will cause its record to show up in a search with a + context OU of BR1 or SYS1, regardless of depth scoping. + + + + +Set a JavaScript cache token when autogen.sh is run, so that a subsequent + run of autogen.sh will automatically cause browsers to fetch refreshed + copies of generated files. This improves the usability of the catalog after + upgrades or certain configuration changes by preventing browsers from relying + on stale cached copies of these files. + + + + + +Serials enhancements + + + +Routing lists: it is now possible to define and print routing lists for + subscriptions. + + + + +Clone subscriptions: new functionality available in the alternate + serials control view to clone subscriptions, thereby speeding initial + setup of a lot of subscriptions. + + + + +MFHD/Distribution summary methods: enable the summary method field for + generating summary holdings statements from the distribution and/or + the record entry (i.e., the MFHD). The four options that are available are: + + + + +Add to record entry + + + + +Merge with record entry + + + + +Use record entry only + + + + +Do not use record entry + + + + + + +Advanced receiving: rename the previous serials receiving interface + to "advanced receiving". The new "receive" interface will now show items + from an entire subscription, but not allow you to receive directly into + a specific unit. + + + + +Unit-less receiving: new option for receiving serials into a no unit, + allowing items to be received but not unitized (i.e., created as a + circulating copy record). This allows issues to be received for + reading room or non-circulating use. + + + + +Caption/pattern enhancements: + + + + +The Caption/Pattern Wizard now includes a graphical way to include + regularity information (that is, the values typically conveyed in the 85x + subfield $y). + + + + +The Alternate Serials Control interface can now import caption and pattern + information from the 85x fields of the MFHD record, allowing the + Caption/Pattern Wizard to be bypassed. + + + + + + +Can now create one-off issuances for unpredicted or unexpected serial issues. + + + + +Improvements to the copy template editor for serials, including the addition + of reasonable default values for some fields. + + + + +Various minor interface improvements, including new links between various pages + in the serials control interfaces and removing redundant questions from the holding code + mini-wizard. + + + + +Bugfixes to the batch receive interface. + + + + + +Staff client improvements + + + +The client supports new hotkey sets that are selectable per workstation. In + addition, there is now a toggle for temporarily disabling hotkeys available + on the toolbar and in the admin menu. + + + + +The client has a second toolbar for cataloging functions as well as options + controlling the presence and size of icons and presence and position of + labels. To support the preferences of individual staff, each workstation can + be configured differently. See the Admin → Workstation Administration → + Toolbars sub-menu for options. + + + + +Patron registration now supports "Suggested" fields that are configurable + per library. In addition, library settings allow required fields to be + adjusted, and it is possible to specify regular expressions to validate + input for many fields in the patron registration interface. Open Admin → + Local Administration → Library Settings Editor and filter on GUI. + + + + + +New configuration and administration settings + +New <literal>opensrf.xml</literal> settings +(The path to these settings is relative to /opensrf/default/apps/). + + + +open-ils.search/app_settings/default_CD_modifiers: parameters to + the cover density ranking function used to calculate relevance during + bibliographic searches. + + + + +open-ils.trigger/app_settings/parallel/collect: number of parallel + processes that action_trigger_runner.pl should use when collecting events. + Setting this can decrease the time it takes for Action/Trigger processing to + run on large Evergreen databases. + + + + +open-ils.trigger/app_settings/parallel/react: number of parallel + processes that action_trigger_runner.pl should use when processing event reactors. + Setting this can decrease the time it takes for Action/Trigger processing to + run on large Evergreen databases. + + + + +open-ils.resolver/app_settings/cache_timeout: how long to cache results + from your OpenURL resolver. + + + + +open-ils.resolver/app_settings/default_url_base: set to the base URL + of your OpenURL resolver. + + + +In addition, the default_preferred_language and default_preferred_language_weight +settings have been moved from the open-ils.storage simplesect to the open-ils.search +simplesect of opensrf.xml. + + +New administration pages +The following new administration pages can all be accessed +from the Admin | Server Administration menu item in the staff client: + + + +Call Number Prefixes: Populates a drop down menu in the new Unified Copy / + Call Number Editor + + + + +Call Number Suffixes: Populates a drop down menu in the new Unified Copy / + Call Number Editor + + + + +Circulation Matchpoint Weights: Related to the in-database Circulation and + Hold Rule configuration changes + + + + +Hold Matchpoint Weights: Related to the in-database Circulation and + Hold Rule configuration changes + + + + +MARC Coded Value Maps: Sets labels for fixed fields and extends the set of + values for display + + + + +MARC Record Attributes: Sets labels for fixed fields and extends the set of + values for display + + + + +Weights Associations: Related to the in-database Circulation and + Hold Rule configuration changes + + + + + +New library settings + + + + + + + Label + Description + + + + +Cataloging: Default copy status (fast add) +Default status when a copy is created using the "Fast Add" interface. + + +Cataloging: Default copy status (normal) +Default status when a copy is created using the normal volume/copy creator interface. + + +GUI: Default Hotkeyset +Default Hotkeyset for clients (filename without the .keyset). Examples: Default, Minimal, and None + + +GUI: Default showing suggested patron registration fields +Instead of All fields, show just suggested fields in patron registration by default. + + +GUI: Example for day_phone field on patron registration +The Example for validation on the day_phone field in patron registration. + + +GUI: Example for email field on patron registration +The Example for validation on the email field in patron registration. + + +GUI: Example for evening_phone field on patron registration +The Example for validation on the evening_phone field in patron registration. + + +GUI: Example for other_phone field on patron registration +The Example for validation on the other_phone field in patron registration. + + +GUI: Example for phone fields on patron registration +The Example for validation on phone fields in patron registration. Applies to all phone fields without their own setting. + + +GUI: Example for post_code field on patron registration +The Example for validation on the post_code field in patron registration. + + +GUI: Horizontal layout for Volume/Copy Creator/Editor. +The main entry point for this interface is in Holdings Maintenance, Actions for Selected Rows, Edit Item Attributes / Call Numbers / Replace Barcodes. This setting changes the top and bottom panes for that interface into left and right panes. + + +GUI: Regex for day_phone field on patron registration +The Regular Expression for validation on the day_phone field in patron registration. + + +GUI: Regex for email field on patron registration +The Regular Expression for validation on the email field in patron registration. + + +GUI: Regex for evening_phone field on patron registration +The Regular Expression for validation on the evening_phone field in patron registration. + + +GUI: Regex for other_phone field on patron registration +The Regular Expression for validation on the other_phone field in patron registration. + + +GUI: Regex for phone fields on patron registration +The Regular Expression for validation on phone fields in patron registration. Applies to all phone fields without their own setting. + + +GUI: Regex for post_code field on patron registration +The Regular Expression for validation on the post_code field in patron registration. + + +GUI: Require county field on patron registration +The county field will be required on the patron registration screen. + + +GUI: Require day_phone field on patron registration +The day_phone field will be required on the patron registration screen. + + +GUI: Require dob field on patron registration +The dob field will be required on the patron registration screen. + + +GUI: Require email field on patron registration +The email field will be required on the patron registration screen. + + +GUI: Require evening_phone field on patron registration +The evening_phone field will be required on the patron registration screen. + + +GUI: Require other_phone field on patron registration +The other_phone field will be required on the patron registration screen. + + +GUI: Show active field on patron registration +The active field will be shown on the patron registration screen. Showing a field makes it appear with required fields even when not required. If the field is required this setting is ignored. + + +GUI: Show alert_message field on patron registration +The alert_message field will be shown on the patron registration screen. Showing a field makes it appear with required fields even when not required. If the field is required this setting is ignored. + + +GUI: Show alias field on patron registration +The alias field will be shown on the patron registration screen. Showing a field makes it appear with required fields even when not required. If the field is required this setting is ignored. + + +GUI: Show barred field on patron registration +The barred field will be shown on the patron registration screen. Showing a field makes it appear with required fields even when not required. If the field is required this setting is ignored. + + +GUI: Show calendar widget for dob field on patron registration +If set the calendar widget will appear when editing the dob field on the patron registration form. + + +GUI: Show claims_never_checked_out_count field on patron registration +The claims_never_checked_out_count field will be shown on the patron registration screen. Showing a field makes it appear with required fields even when not required. If the field is required this setting is ignored. + + +GUI: Show claims_returned_count field on patron registration +The claims_returned_count field will be shown on the patron registration screen. Showing a field makes it appear with required fields even when not required. If the field is required this setting is ignored. + + +GUI: Show day_phone field on patron registration +The day_phone field will be shown on the patron registration screen. Showing a field makes it appear with required fields even when not required. If the field is required this setting is ignored. + + +GUI: Show dob field on patron registration +The dob field will be shown on the patron registration screen. Showing a field makes it appear with required fields even when not required. If the field is required this setting is ignored. + + +GUI: Show email field on patron registration +The email field will be shown on the patron registration screen. Showing a field makes it appear with required fields even when not required. If the field is required this setting is ignored. + + +GUI: Show evening_phone field on patron registration +The evening_phone field will be shown on the patron registration screen. Showing a field makes it appear with required fields even when not required. If the field is required this setting is ignored. + + +GUI: Show ident_value field on patron registration +The ident_value field will be shown on the patron registration screen. Showing a field makes it appear with required fields even when not required. If the field is required this setting is ignored. + + +GUI: Show ident_value2 field on patron registration +The ident_value2 field will be shown on the patron registration screen. Showing a field makes it appear with required fields even when not required. If the field is required this setting is ignored. + + +GUI: Show juvenile field on patron registration +The juvenile field will be shown on the patron registration screen. Showing a field makes it appear with required fields even when not required. If the field is required this setting is ignored. + + +GUI: Show master_account field on patron registration +The master_account field will be shown on the patron registration screen. Showing a field makes it appear with required fields even when not required. If the field is required this setting is ignored. + + +GUI: Show other_phone field on patron registration +The other_phone field will be shown on the patron registration screen. Showing a field makes it appear with required fields even when not required. If the field is required this setting is ignored. + + +GUI: Show second_given_name field on patron registration +The second_given_name field will be shown on the patron registration screen. Showing a field makes it appear with required fields even when not required. If the field is required this setting is ignored. + + +GUI: Show suffix field on patron registration +The suffix field will be shown on the patron registration screen. Showing a field makes it appear with required fields even when not required. If the field is required this setting is ignored. + + +GUI: Suggest active field on patron registration +The active field will be suggested on the patron registration screen. Suggesting a field makes it appear when suggested fields are shown. If the field is shown or required this setting is ignored. + + +GUI: Suggest alert_message field on patron registration +The alert_message field will be suggested on the patron registration screen. Suggesting a field makes it appear when suggested fields are shown. If the field is shown or required this setting is ignored. + + +GUI: Suggest alias field on patron registration +The alias field will be suggested on the patron registration screen. Suggesting a field makes it appear when suggested fields are shown. If the field is shown or required this setting is ignored. + + +GUI: Suggest barred field on patron registration +The barred field will be suggested on the patron registration screen. Suggesting a field makes it appear when suggested fields are shown. If the field is shown or required this setting is ignored. + + +GUI: Suggest claims_never_checked_out_count field on patron registration +The claims_never_checked_out_count field will be suggested on the patron registration screen. Suggesting a field makes it appear when suggested fields are shown. If the field is shown or required this setting is ignored. + + +GUI: Suggest claims_returned_count field on patron registration +The claims_returned_count field will be suggested on the patron registration screen. Suggesting a field makes it appear when suggested fields are shown. If the field is shown or required this setting is ignored. + + +GUI: Suggest day_phone field on patron registration +The day_phone field will be suggested on the patron registration screen. Suggesting a field makes it appear when suggested fields are shown. If the field is shown or required this setting is ignored. + + +GUI: Suggest dob field on patron registration +The dob field will be suggested on the patron registration screen. Suggesting a field makes it appear when suggested fields are shown. If the field is shown or required this setting is ignored. + + +GUI: Suggest email field on patron registration +The email field will be suggested on the patron registration screen. Suggesting a field makes it appear when suggested fields are shown. If the field is shown or required this setting is ignored. + + +GUI: Suggest evening_phone field on patron registration +The evening_phone field will be suggested on the patron registration screen. Suggesting a field makes it appear when suggested fields are shown. If the field is shown or required this setting is ignored. + + +GUI: Suggest ident_value field on patron registration +The ident_value field will be suggested on the patron registration screen. Suggesting a field makes it appear when suggested fields are shown. If the field is shown or required this setting is ignored. + + +GUI: Suggest ident_value2 field on patron registration +The ident_value2 field will be suggested on the patron registration screen. Suggesting a field makes it appear when suggested fields are shown. If the field is shown or required this setting is ignored. + + +GUI: Suggest juvenile field on patron registration +The juvenile field will be suggested on the patron registration screen. Suggesting a field makes it appear when suggested fields are shown. If the field is shown or required this setting is ignored. + + +GUI: Suggest master_account field on patron registration +The master_account field will be suggested on the patron registration screen. Suggesting a field makes it appear when suggested fields are shown. If the field is shown or required this setting is ignored. + + +GUI: Suggest other_phone field on patron registration +The other_phone field will be suggested on the patron registration screen. Suggesting a field makes it appear when suggested fields are shown. If the field is shown or required this setting is ignored. + + +GUI: Suggest second_given_name field on patron registration +The second_given_name field will be suggested on the patron registration screen. Suggesting a field makes it appear when suggested fields are shown. If the field is shown or required this setting is ignored. + + +GUI: Suggest suffix field on patron registration +The suffix field will be suggested on the patron registration screen. Suggesting a field makes it appear when suggested fields are shown. If the field is shown or required this setting is ignored. + + +GUI: Unified Volume/Item Creator/Editor +If true combines the Volume/Copy Creator and Item Attribute Editor in some instances. + + +Printing: Custom Javascript File +Full URL path to a Javascript File to be loaded when printing. Should implement a print_custom function for DOM manipulation. Can change the value of the do_print variable to false to cancel printing. + + +Recalls: An array of fine amount, fine interval, and maximum fine. +Recalls: An array of fine amount, fine interval, and maximum fine. For example, to specify a new fine rule of $5.00 per day, with a maximum fine of $50.00, use: [5.00,"1 day",50.00] + + +Recalls: Circulation duration that triggers a recall. +Recalls: A hold placed on an item with a circulation duration longer than this will trigger a recall. For example, "14 days" or "3 weeks". + + +Recalls: Truncated loan period. +Recalls: When a recall is triggered, this defines the adjusted loan period for the item. For example, "4 days" or "1 week". + + + + + + +New user permissions + + + + + + + Code + Description + + + + +ADMIN_CODED_VALUE +Create/Update/Delete SVF Record Attribute Coded Value Map + + +ADMIN_SERIAL_ITEM +Create/Retrieve/Update/Delete Serial Item + + +ADMIN_SVF +Create/Update/Delete SVF Record Attribute Defintion + + +CREATE_BIB_PTYPE +Create Bibliographic Record Peer Type + + +CREATE_MONOGRAPH_PART +Create monograph part definition. + + +CREATE_PURCHASE_REQUEST +Create User Purchase Request + + +CREATE_VOLUME_PREFIX +Create prefix label definition. + + +CREATE_VOLUME_SUFFIX +Create suffix label definition. + + +DEBUG_CLIENT +Allows a user to use debug functions in the staff client + + +DELETE_BIB_PTYPE +Delete Bibliographic Record Peer Type + + +DELETE_MONOGRAPH_PART +Delete monograph part definition. + + +DELETE_VOLUME_PREFIX +Delete prefix label definition. + + +DELETE_VOLUME_SUFFIX +Delete suffix label definition. + + +MAP_MONOGRAPH_PART +Create/Update/Delete Copy Monograph Part Map + + +MARK_ITEM_MISSING_PIECES +Allows the Mark Item Missing Pieces action. + + +UPDATE_BIB_PTYPE +Update Bibliographic Record Peer Type + + +UPDATE_HOLD_REQUEST_TIME +Allows editing of a hold’s request time, and/or its Cut-in-line/Top-of-queue flag. + + +UPDATE_MONOGRAPH_PART +Update monograph part definition. + + +UPDATE_PATRON_COLLECTIONS_EXEMPT +Allows a user to indicate that a patron is exempt from collections processing + + +UPDATE_PICKLIST +Allows update/re-use of an acquisitions pick/selection list. + + +UPDATE_VOLUME_PREFIX +Update prefix label definition. + + +UPDATE_VOLUME_SUFFIX +Update suffix label definition. + + +UPDATE_WORKSTATION +Allows update of a workstation during workstation registration override. + + +VIEW_USER_SETTING_TYPE +Allows viewing of configurable user setting types. + + + + + + + diff --git a/intro/releasenotes.xml b/intro/releasenotes.xml deleted file mode 100644 index f13944de0e..0000000000 --- a/intro/releasenotes.xml +++ /dev/null @@ -1,348 +0,0 @@ - - - - 2.0 Feature List - - - - - Circulation - - Patron Registration Enhancements - - Zip code information can be added to a local table which will pre-populate the City/State fields during patron registration. - Added the ability to delete patrons by anonymizing the patron's personally identifiable data and purging the related data from other tables - without destroying information important to the integrity of the database as a whole (does not delete the actor.usr row). - Supports the ability to merge patrons; when it is determined that more than one account exists for a single patron. There is an interface for - side-by-side comparison of the records; ability to delete addresses on merged accounts, delete cards and deactivate cards. Patrons with a status of in collections - are not eligible for merging. - Added quick links for staff to copy and paste patron address information. Information will paste in a standard mailing format. - Patrons with an address alert (invalid/bad address) will be displayed at the top of a duplicates list. - Patrons may create library accounts through the OPAC. These are set as pending until they can be confirmed by staff. The backend support for this - is done. - The system recognizes certain categories of patrons like Card Canceled, Deceased, etc. and will not place holds for these categories. - - The patron record screen obscures certain information which can be considered sensitive. - Patrons may create library accounts through the OPAC. These are set as pending until they can be confirmed by staff. The backend support for this - is done. - Evergreen has the ability to automatically enter date, user, and location in messages and notes. - - - - Item Checkout enhancements - - During check-out, the patron's fines list appears first if there is a balance. If there is an alert, the alert page will show first, then fines - screen. - Evergreen has the ability to track hourly checkout stats. Self-check now operates by workstation and it's possible to gather statistics for checkouts - between staff workstations and self-check workstations. (There is a workstation registration wizard built into the self-check UI.) - Audible cue support, for successful and unsuccessful check-out, at self check-out stations has been added. This is customizable at the database level. - Evergreen has fast-add capability. During check-out, if an item is found not to be cataloged,you can pre-cat the item quickly, we've added other field - such as library, ISBN and circ modifier to this pre-cat. - The system supports sets or kits of items and has the ability to display the number of items and a list of descriptions. - Evergreen allows patrons to renew a title as long as they have not exceeded the allowed number of renewals and there are more available items - than there are unfrozen holds. This is an administration setting. - - - - Self Check module enhancements - - In self check and SC, if a staff member checks out an item to a patron that is already checked out to that patron, the item will simply renew. This does - have configurable age-based parameters to prevent a double scan at checkout resulting in a renewal. - For self check receipts, receipts include the same information for renewal as checkouts and includes notes on items that failed to renew. - In the self-check UI, patrons can view holds and patron position vs. the number of circulating copies. - The self check-out station displays holds ready for pickup, then removes each hold as the item is checked out. - Evergreen supports the ability to pay fines with a credit card at self check-out stations. This requires the library to have a merchant account with a credit - card processor like Paypal. The current supported processors include Authorize.net and Paypal. - - - - Item Check-in enhancements - - Evergreen supports a set number of claim returns allowed; beyond that, additional claim returns require supervisor authorization. This is based off the - claims returned counter. This only blocks another claim returned, and circulation can still occur. Also, there is a new permission to allow changing the claims - returned count for a patron. In order to use this feature, staff needs to have the appropriate permission. - There's a new calendar widget in the backdating function in the item check-in module. The system has the ability to select items already checked in - and retroactively backdate those items, using a button with a calendar selector. Any fines resulting from original check-in are removed. When a check-in is backdated, - the item record retains both the actual date of check-in and backdate used. This information will display in the copy details interface. - When marking an item damaged, several library settings are checked to determine whether the patron should be charged the copy price and/or a processing fee. - Staff is prompted with this amount, which can either be applied or modified or canceled. - - - - Holds Enhancements - - Evergreen allows for hold slips to be customized to include any field from the patron record and/or item record, in any position and orientation on the - slip. Font, font size, and font weight are customizable. In addition, the hold slip may include a branch symbol (gif or jpg format) - Evergreen supports behind the desk indicator printing on holds slip for patrons who have this flag in their patron record. (This would be for libraries - with public hold shelves.) - In Evergreen, between the time that a hold is checked in and a hold is placed on the hold shelf, there is a configurable delay before the status is changed - to On Hold Shelf. - Evergreen has the ability to ensure that manually edited copies (either deleting or changing to a non-holdable status) will have their holds - retargeted. - In Evergreen, between the time that a hold is checked in and a hold is placed on the hold shelf, there is a configurable delay before the status is - changed to On Hold Shelf. - The system supports a Clear Hold Shelf process. First, it removes holds from items that have expired on the hold shelf, and generates a report (aka clear - hold shelf report) listing items to be cleared from hold shelf. Then staff can print the list, go out and physically pull the items off of the hold shelf. Next, - staff scan the items in EG to either reset the items to the correct shelving location, capture the next hold or put the items in transit to the correct owning - location. - Staff can extend pickup deadlines for holds. - In the patron view in the SC (staff client), you can select multiple holds in actions for selected holds and choose to change the pickup location. - Evergreen has the ability to change the pickup location for all of a patron's holds in a single process. Additionally, Evergreen has the ability to modify all - holds attached to a bibliographic record, including the ability to change the hold expiration date. This functionality is covered with current bib holds list - interface. - Evergreen allows patrons with specific permissions to place holds on items they have already checked out. All other patrons cannot. This works by warning the - user that the item is already checked out to them and, if they have the permission, the system gives them the ability to override. - The system supports the ability to place holds on titles with status on-order. For additional information, see the Acquisitions notes later in this - document. - Evergreen has the ability to designate specific org units that will not trigger a hold upon check-in. - Evergreen added logic to hold targeting to skip branches that are closed at the time of hold placement and x time (x - time being a set interval). This is - to prevent the hold being targeted at branches that will be closed Saturday and Sunday (for example), making it impossible for patrons to receive their hold. This - presumes there is another copy available at another branch. - There are more options now for hold settings. One option is library weighting as well as looping. If looping is set, the holds targeter will skip any - libraries that it targeted in a previous loop and will continue doing so until it has tried all libraries at which point it will start the process over again. If max - loops are being used in hold management, at the end of the last determined loop, if there are no copies that could potentially fill a hold, the hold may be canceled. - If there are checked-out copies, the hold stays in queue; otherwise, the hold is canceled and a cancellation notice is sent to the patron. - The system offers the ability to secondarily sort the Holds Pull List by physical shelving location within the library. - The system offers the ability to distinguish between staff-placed holds and patron-placed holds through a column in the holds interface. - Hold cancellation can be displayed, along with information regarding the cancellation (e.g., cause, cancellation type, date, item, patron, etc.) - There is support now in the system to allow configuration to disallow holds for items that are on the shelf at the location from which the patron is - searching. - The system supports patron specific hold notes that can display in the OPAC and print in the hold notice, but do not necessarily print on hold slips. - The system supports ability for staff to move someone to the top of the holds queue. This was developed due to cases where a patron picked up a hold but the - item was damaged. Since the patron had picked up the hold, it was considered filled. - The patron can change the pickup location before the hold is ready for pickup. Then, the item is put in transit & a new holds slip is printed with a - special symbol to indicate that the pickup location has been changed. If the location is changed while the item is in transit, than at next checkin the item is put - in transit to the new location. A new holds slip is printed. - The system supports a separate hold note field for staff use that can print on hold slip. - Ability for patrons to view recently canceled holds and easily re-place holds. - - - - - Staff Client Interface Enhancements - - Evergreen includes color-coding into staff view of patrons when there is a bad or invalid address. Also included is an alert to patrons in the My Account view - in the OPAC to alert them to the bad address problem. System automatically blocks /unblocks a patron when an address is marked invalid/valid. - Ability to have the staff client automatically minimize after a settable period of inactivity to protect patron privacy. This is controlled through an org - unit setting. - Summary of bills, checkouts, and holds are visible from all of the patron screens. - Historical summary of paid fines is sortable by column and displays sub-totals for each column; also allows the ability to limit by voided/non-voided - payments. Fines history detail includes more information including location and time/date where item was returned and much more. - More streamlined display of copy information including number of copies, copy status, and number of holds in both staff client interface and patron - OPAC. - The system supports the ability to edit item records from any item record access point. - From holding maintenance or item status by barcode, you can retrieve more item details. For example, total circulations by current and previous year, last - status change, last checkout date & works station, last checkin time and workstation, and more. - The system includes a separate date field for the last change to the item in the item record. - In the item record, the system displays total check-outs and renewals for year-to-date, previous year, and lifetime. - Better audio signal handling. - In Evergreen, there is an org setting to disable all staff client circ popups unless an unhandled exception occurs. The exception handling has been automated - as much as possible, based in settings, to prevent the amount of popups that require staff attention at the circ desk. Alerts are communicated visually (e.g., screen - color change) or audibly. - The system supports two views of patron information: horizontal and vertical. - From the patrons screen, under holds, clicking place hold will bring up an embedded catalog. Placing a hold from the embedded catalog will automatically - generate a hold for the current account of the patron you are viewing. - The system supports a new messages (notes) UI in the info tab of the patron screen. - The system supports a new interface that shows the most recent activity on the workstation (checkout/checkin/ renewal/ patron-reg activity, with links to - relevant patron from each item). This would be helpful to a supervisor trying to backtrack an issue to assist a staff member. - The system now captures and displays check-in and workstation history. - Added the ability to pre-define messages, populated in a drop-down menu, to be applied to patron accounts. Includes: the ability to configure the message to - act as a penalty (if desired), record the date and staff who applied the message, include a flag to mark item as resolved. If item is marked as resolved it will not - display as an alert. - Under grocery billings in Evergreen, billing type can be pre-populated with a list of common fine events (such as types and costs). - Evergreen has the ability to retrieve users by numberic ID (separate from the barcode) in the staff client. This functionality is optional and set to false - by default. - Backend support for other types of receipts (like holds/fines). - - - - OPAC and My Account Enhancements - - There is backend code support for a method to allow patrons to link their records in a way that grant privileges. This could be utilized in future - implementations for social networking features. - Patron passwords are now more flexible in length and content (shorter and numeric-only passwords are now allowed). Libraries can set minimum and maximum - limits on password length in Password format in the Library Settings Editor. - Patrons can select a username, which can then be used to access OPAC and self check-out stations. - My Account can allow patrons to update some information including: street address, e-mail address and preferred pick-up library for holds. Changes to address - will be marked as pending in the patron's file until a staff member verifies the new address and completes the change. - From the My Account interface, patrons can see their estimated wait time for a hold. Evergreen calculates the estimated wait time from the circ mods on the set - of potential copies available to fill the holds on that title. Hold wait estimate is configurable at the consortial level and each Evergreen implementation would need - to take into consideration their avg circulation time, hold wait time or other factors like transit time which might influence hold wait estimates. - Patrons can title their bookbags (aka reading list) and place holds from it. - Backend support has been developed to allow patrons to waive certain kinds of notices. - The system supports combining multiple notices of the same type to the same patron into one event, so long as the system is configured to batch notices - on an approximately daily basis. - - - - Billing, Collections and Fine/Fee Enhancements - - Fines now consistently link to item record details. - The fine record includes a comments field, editable by staff. Staff can annotate payments and add notes to a specific billing. Staff can sort on payment - type. When adding note, the current text shows as default in a pop-up window, so it can be appended or over-written. - Staff and users can now only pay using the latest user data, which prevents accidental/duplicate payments against the same transaction or against stale - data. - The system supports setting the maximum fine based on item type (e.g. generic=.50) AND not to exceed the cost of item. This works as an inheritable OU - setting, circ.max_fine.cap_at_price, that changes the max_fine amount to the price IF the price is not null and is less than the rule-based max_fine amount. - The system has the ability to run a report of accounts with users with overall negative balances, including the balance owed and last billing activity - time, optionally filtered by home org. There is an option for issuing refunds for selected accounts on the resulting list. The report also captures patrons with - any refundable transaction. - Evergreen provides 3 distinct and independent types of blocks: system, manual and collections. Manual and collections are set manually by staff. - A new penalty type of PATRON_IN_COLLECTIONS has been added. Its set when the collections agency puts the patron into collections, staff can define the blocks - and clear threshold for each group, etc. The system supports removing collection block immediately once charges are paid down to zero (applies to both ecommerce and at - CIRC desk). - - - - Action/Triggered Event and Notice Enhancements - - Action Triggers (AT) support many new notices for events such as items that are about to expire off of the hold shelf; items that are on hold and are about - to reach the max hold time (if one is set); courtesy notices that are prior to due date. AT also logs all notices sent to patrons and this is accessible to staff in the - SC to view all notices or cancel all pending notices. - The system has the ability to cancel unsent notices before they are sent and the ability to search pending notices by item barcode. - Administrators can choose to implement a collections warning prior to sending patrons to collections. When the account balance of the patron meets a - certain threshold, they are sent a bill notice. This is driven by the total amount owed, not by individual bills. The patron is sent to collections after a - configurable number of days since the bill notice was sent. The billing notice is handled with a new PATRON_EXCEEDS_COLLECTIONS_WARNING penalty. Files can be sent via - SCP and FTP. - - - - Acquisitions - - From within the general acquisitions search page, users are able to search on many fields in the acquisitions /serials workflow. For example on attributes - of invoices, purchase orders, selection lists, bib records, etc. - General catalog searching is now supported for explicit truncation/wildcard searches. - Acquisitions line item searches support NOT searches. - Money can be transferred from one fund to another (or to none). - All transactions (except batch EDI delivery to vendors) post in real time including: purchase orders, invoices, fund balances, vendors balances, vendor - statistics and history. EDI delivery delay is configurable at the system level admin interface. - In the User Interface, users now have access to all active funds, spanning multiple years, in the various ordering/invoicing/etc interfaces. - There is support for year-end fiscal turnover process that closes out funds and transfers encumbered amounts into a new fiscal year. This includes the ability - to selectively roll certain funds over, while not rolling over others. - Evergreen handles validation of ordering, receiving,and invoicing processes, using validated data, to satisfy auditor requirements. In the staff client, - there is a menu option which allows staff to locate the PO that resulted in the purchase of that copy. - Selection lists are collections of bibliographic records (short or full) that temporarily store titles being considered for purchase. Selection lists can be - shared for collaborative input. - Library staff have the ability to create distribution formulas for ease of receiving, processing and distributing materials. Branch, shelving location, and fund need - to be separate from the distribution formula, so that staff can enter the distribution sets. Staff are able to use that formula for any shelving location they decide. Staff - also have the ability to add multiple distribution formulas together and the ability to override distribution formulas. After applying the distribution formula; it will be an - all or none redistribution of copies from one branch to another. Staff can add or delete individual copies because the distribution pattern may not account for the exact total - of copies. If the total number of copies has not been allocated, the user will receive a flag or warning. This puts the use count for each distribution formula in the DF - dropdown for users to see. - The system supports Batch ISBN/UPC search. This is located in the general Acquisitions search page, where you can choose to search by single isbn, upc, or you can - choose to upload a batch of isbns. The ISBN search method looks at MARC tag 024, where UPC codes are supposed to live. For LI searching, the system uses - open-ils.acq.lineitem.search.ident. Catalog records are included in the batch isbn/upc search and staff can now search catalog records in the acq search. - Backend support has been integrated to give patrons the ability to submit purchase requests through the OPAC. The UI for this has not yet been integrated into the - OPAC. - The system supports claiming, specifically there is: - - a place to store the default claim interval for each vendor - a way to show the selected claim date during the order - ` a way to show the selected claim date during the order - a way to override the claim date during order - a way to list items/orders that have reached the claim date. - - A list of items that meet claims requirements can be generated, but claims must be initiated by librarians. - From the UI, staff can access the lineitem and PO history. Entries in the history table are ordered from most recent to oldest. - The purchase order printout is customizable, including the ability to break up a single order into separate purchase orders. Also, staff can print groups - of POs from a search as a single printout, which can be used to generate physical POs for vendors who do not support EDI. Staff can add notes and there is an indicator - in the PO interface of the existence/number of attached notes. - Staff are able to see all of the lineitems (with prices, copy counts, etc.) for a set of Pos and summary information is listed along the top of the page. - The summary information includes: total price, total # lineitems, and total # of copies. Additionally, staff can do a PO search by vendor for all - activated-but-not-yet-sent Pos (i.e., show me what we are about to order) and view the results. - The system supports flagging prepaid orders so that invoicing is handled correctly. - The system allows building orders based on templates (distribution formulas); by shelving location or owning library. - The system supports the ability to gather orders together and send them all at once, instead of manually and individually, a rolling FTP function that runs - every 15 minutes (or other set interval) with detailed log information and control of frequency and action. Additionally, there is an automatic retrieval of status - reports records from the vendor, which are then automatically inserted into the order records. - Staff have the ability to apply and view notes and cancel causes on purchase orders as well as cancel causes on lineitems. In the UI, there is a staff client - menu entry for cancel cause. - There is an interface in the ACQ system for viewing what was sent to vendors via EDI. There are two ways to approach the viewing of sent orders: via PO - search interface (for the general case) which gives finer detail on EDI orders and the ability to reset failed outbound EDI deliveries. - Pending final UI work in the OPAC, the system has the ability to allow patrons to place volume level and issue level holds. - Ability to create and print routing worksheets for manual receiving processes. - Nothing in the selection lists is holdable (either by patrons or by most staff, apart from acquisitions staff). When an on-order title has been canceled and - the lineitem is canceled, the corresponding bib record and on-order copies will be deleted so the copies will no longer be holdable. The lineitem has a cancel cause to - show why order was canceled. Selection list records are never visible in the OPAC. Catalog records with no visible copies (within the search scope) do not show up in - the public OPAC. This also applies to on-order records. - Deleted bibs, callnumbers, copies, and patrons are retained for reporting purposes. Only patrons can be purged (by staff). “Deleted” items are more - accurately described as “inactive.” However, patrons can now be complete purged, however this isn't recommended as you lose historical data. - The system supports shared and floating items by collection. Item records can be added or removed from the collection group and can be updated in batch - via buckets in the copy edit interface. - ACQ permissions control which workgroups have view/edit access to lineitem and catalog records while PO/PL and copy-level ownership and permission depths - affect viewing in other, more location-specific interfaces. - The system supports the ability to transfer patron holds queue from one bibliographic record to another, singly or in batch, while preserving the original - hold order. - The system has a reporting view which allows staff to identify bibs (shows ISBNs) for which the last item was removed based on the date of removal. - Report templates can be built from this view for external processes. - The system supports lineitem alerts, lineitem receive alerts, and lineitem detail alerts for EDI messaging. - The system supports the ability to exclude some types of items from patron hold limits. - There is support for new, locally defined, cancel reasons for EDI. There is also support for EG interpretation of EDI defined cancellation standards. - The system supports the ability to send batches of orders to vendors, including orders for multiple accounts. The process of breaking outbound EDI messages - into controlled and timed batch sizes is automated but settable to a specific, preferred, time interval. - The system supports the ability to FTP orders directly to vendors and receive acknowledgements and status reports from vendors. More specifically, the - system supports push and pull of files via FTP, SFTP and - SSH. - The system supports MARC file import with PO data. - The OPAC accepts enhanced content from the following vendors: ChiliFresh, Content Café & Novelist. (note that these are subscription services) - - You can set up vendor profiles and flag those that are active. Those that aren't can be saved for historical purposes. - The system supports the ability to “flag” vendor records for vendor who require pre-payment of purchase orders with a number of visual cues in the UI. During - PO creation, the pre-payment flag in the form will show and pre-populate it's value with the value from the chosen provider. During PO activation, if prepayment - is required, a confirmation dialog is inserted before sending the activate request. It indicates in the PO summary when a PO requires pre-payment. - The system supports sequential barcode generation for ease of receiving and processing of new items and easily changing large groups of barcodes. There is - a choice to use auto generated barcodes in interfaces where they would normally be used (such as receiving). Some parameters about the barcode symbology may need to - be entered in the admin interface to correctly calculate the barcodes. - The system supports the ability to manually select libraries to receive items when partial orders are received or when items come in multiple deliveries. - Orders with multiple copies will have an owning library per copy, so staff can pick which copies to mark as received. - The system is compatible with Zebra Z4M thermal transfer printers. - The system supports the ability to create, format and print spine labels. - In the ACQ UI, there is a batch fund updater. When there is a given set of line items, the batch fund updater updates the fund for all attached copies in - batch. - The system has a configurable drop-down of alerts for line items that staff can control. - The system supports the ability to update order records at the receiving stage; the ability to receive partial orders and unreceive orders; and the order - record is updated automatically when the balance of a partial order is received. - The system supports the ability to transfer item records from one bibliographic record to another. - The system supports a worksheet for each title received, to include title, call number, number of copies received, distribution, and processing notes. - The system supports the ability to easily scan over a “dummy” or placeholder barcode in a temporary, brief or on-order record by simply scanning the - real barcode. - The system supports the import/export of MARC bibliographic and authority records via Vandelay. An option has been added to use the internal bib ID as the TCN - for all records while retaining the OCLC number in the record. The authority import now matches bib import in overlay/merge functionality. - The system is fully compatible with OCLC Connexion for editing and transferring bibliographic and authority records (Z39.50). - The system supports the ability to create a short bib record pending creation of the full MARC record. Short bibs can be created from a lineitem - search. - The system supports a utility to facilitate searching for full bibliographic records and create temporary short bibliographic records if no full - records are found. - Added the ability to perform electronic receiving and invoicing as follows: ability to receive electronic packing slips and invoices by purchase order or - invoice number; ability to edit number of copies, amount due, freight and service charges, and tax; ability to delete line items; ability to recalculate total - amounts; ability to authorize payment within ILS. - System supports the ability to do both regular and generic or blanket invoicing (refers to invoices without a purchase order number, e.g., direct charges to - a fund). - System supports simultaneous access to invoice interface. - System supports a number of fields including: date, invoice number, invoice type, shipping vendor name, billing vendor, purchase order number, title, - author, number of copies ordered, number of copies paid or received, number of copies available for payment, number of copies being paid for, amount, notes, - invoice subtotal, freight charge, service charge, tax, invoice total, & vendor order was placed with. - The system prevents overpayment in the invoice view page by linking invoices to PO/Lineitems. - Staff can print a list of invoices paid before/after a specified date. When searching for invoices in the unified search interface, there's now a button that - will print a voucher for whichever invoices have checked checkboxes. - The system supports the ability to search invoices by number or vendor name, with links to vendors, and vendor records include links to invoice history. - Staff can retrieve a PO or lineitem and access all the related invoicing data. - The system supports reopening a closed invoice (example: an invoice was paid from the wrong fund; staff wants to go back and change the fund). There is - a Reopen button, which requires permissions. - The system has the ability to pay a partial invoice for partial receipt of shipment, and then generate claims for the items that were not received. Also, - the system supports invoicing extra copies when a vendor sends more copies than what staff ordered and staff decides to keep the extra copies. - Issues can be automatically moved to a configured shelving location upon receipt of the newer issue. This can be done on a per item basis and is based on - the owning library of the copies. - When using full serials control, the default behavior for serials issue sorting and display in the holdings display will be reverse chronological order. - Staff can label serials issuances with easily identifiable text such as YYYYMONTH or V.12 NO.1. - In serials receiving staff are able to choose which issues to receive and distribute to which locations. - Staff can add regular, supplemental, and index issues in the serials interface. - The system supports purchase alert query (aka holds ratio report, holds alert report) compares holds to items and flags titles that need more copies. - The option exists to include inprint/out-of-print status from the bibliographic record. The system also handles the ability to add query results directly to - selection lists, singly or in batch, and the ability to create order records directly from query results. This is handled by an interface for uploading a CSV file - to generate a page of bib records that can have lineitems created from them to go into selection lists and/or POs. - - - diff --git a/root.xml b/root.xml index e1c9a98317..a0e72a1575 100755 --- a/root.xml +++ b/root.xml @@ -38,7 +38,7 @@ - + @@ -51,30 +51,25 @@ Core Staff Tasks - + Administration - - - - - + @@ -82,7 +77,7 @@ Reports - + @@ -104,7 +99,7 @@ Development - +