--- /dev/null
+<?xml version="1.0" encoding="UTF-8"?>\r
+<chapter xml:id="releasenotes" xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="EN"\r
+ xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink">\r
+ <chapterinfo>\r
+ <title>2.1 Release Notes</title>\r
+ </chapterinfo>\r
+\r
+<simplesect id="_installation_enhancements">\r
+<title>Installation enhancements</title>\r
+<itemizedlist>\r
+<listitem>\r
+<simpara>\r
+<literal>eg_db_config.pl</literal> now has a <literal>--create-database</literal> option to automatically create\r
+ the database and add the required contrib modules/extensions, rather than\r
+ requiring users to carry out a number of error-prone manual steps.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+The OpenILS Perl modules are now installed in the system Perl package\r
+ directories. In prior versions, they were typically installed in\r
+ <literal>/openils/lib/perl5</literal>.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+README is now the single source of install instructions\r
+</simpara>\r
+</listitem>\r
+</itemizedlist>\r
+</simplesect>\r
+<simplesect id="_administration_enhancements">\r
+<title>Administration enhancements</title>\r
+<itemizedlist>\r
+<listitem>\r
+<simpara>\r
+Automatic client updates: It is now possible to build staff clients that,\r
+ when they connect to the Evergreen server, automatically check to see if\r
+ the staff client has been updated. If so, the staff client can download just\r
+ the files that have been updated and replace those files in the existing\r
+ staff client.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Printing subsystem: Changes to the staff client should improve the print\r
+ functionality (both speed and likelihood of success).\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+To protect against exploits between a shared staff client session via\r
+ operator change, add the requirement for the DEBUG_CLIENT permission to\r
+ invoke debugging functions such as the Javascript Shell or DOM Inspector\r
+ in the staff client.\r
+</simpara>\r
+</listitem>\r
+</itemizedlist>\r
+</simplesect>\r
+<simplesect id="_cataloging_enhancements">\r
+<title>Cataloging enhancements</title>\r
+<itemizedlist>\r
+<listitem>\r
+<simpara>\r
+Unified copy / call number editor: The default holdings maintenance interface\r
+ now enables cataloguers to edit copies and call numbers on a single screen.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Call number prefixes and suffixes: While previous releases of Evergreen\r
+ supported the automatic prepending or appending of prefixes and suffixes to\r
+ call numbers based on their shelving location, the functionality was limited\r
+ primarily to printing spine labels. As of 2.1, you also have the option to\r
+ assign prefixes or suffixes for individual call numbers; these will be\r
+ displayed in the public catalogue and other interfaces, but prefixes in\r
+ particular do not affect shelf browsing, which is based entirely on the\r
+ label.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Bibliographic parts: This feature adds the ability to designate specific\r
+ "part" roles for the items attached to a given bibliographic record, such\r
+ that a user can place holds on a specific kind of item without limiting it\r
+ to an individual item. For example, libraries may assign parts to each DVD\r
+ in a season of a popular TV show; or to individual volumes of an\r
+ encyclopedia. This feature also introduces "part holds".\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Conjoined items: This feature adds the ability to associate a single barcode\r
+ with multiple bibliographic records, so that the availability of those\r
+ records is updated based on that copy. For example, libraries may make an\r
+ electronic reader available for loan that is preloaded with 1000 electronic\r
+ books; they can add 1000 bibliographic records to the library system and\r
+ associate them all with a single barcode, so that when the electronic reader\r
+ is signed out, the availability for all 1000 records changes to "Checked out".\r
+</simpara>\r
+</listitem>\r
+</itemizedlist>\r
+</simplesect>\r
+<simplesect id="_circulation_improvements">\r
+<title>Circulation improvements</title>\r
+<itemizedlist>\r
+<listitem>\r
+<simpara>\r
+Transfer selected holds to a different title: It is now possible to select\r
+ multiple holds on a given title and transfer them to a different title.\r
+ Use case: Your library acquires another copy of "Pride and Prejudice and\r
+ Zombies", but as it is a new edition it must be cataloged as a new\r
+ bibliographic record; however, you would like to spread out some of the holds\r
+ queue from your current edition to the new edition.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Mark patron as exempt from billing collections: It is now possible to mark a\r
+ patron as being exempt from being sent to collections.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Hold-driven recalls: It is now possible to define a loan\r
+ period threshold (such as 60 days) so that if a hold is placed on an item with\r
+ a loan period beyond that threshold, the system will automatically shorten the\r
+ loan period to a specified value; change the fine rules; and send email\r
+ notification to the person who currently holds the item saying "A hold has\r
+ been placed on this item, get it back before <new_due_date>".\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Weighting of the individual fields of the in-database circulation and holds\r
+ rules can now be configured, rather than using hard-coded values. This allows\r
+ the importance of each field to be adjusted as needed through the circulation\r
+ matrix weighting, hold matrix weighting, and weighting associations settings.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+The in-database circulation rules support "fall-through" wherein some\r
+ information can be left out of more specific rules and filled in from less\r
+ specific rules. For example, disabling fines for staff could be accomplished\r
+ with a single rule setting only the fine rate and/or max fine rules, without\r
+ having to duplicate all duration related rules in the system.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Grace periods are now stored in the database and set via circulation rules,\r
+ rather than passed into the fine generation code, and can thus differ between\r
+ different rules. They are also no longer based on a number of fine intervals,\r
+ but are instead defined by their own specific interval. This can eliminate\r
+ problems with closed date interpretation during grace periods.\r
+</simpara>\r
+</listitem>\r
+</itemizedlist>\r
+</simplesect>\r
+<simplesect id="_public_interface_improvements">\r
+<title>Public interface improvements</title>\r
+<itemizedlist>\r
+<listitem>\r
+<simpara>\r
+Spell-checking suggestions are now case-insensitive, to avoid generating\r
+ terms which would yield the same result set.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Part holds: patrons are guided to select a specific part if they are\r
+ placing a hold on a bibliographic record that has parts assigned to its\r
+ copies.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Located URI visibility: Located URIs (856 fields with a subfield $9\r
+ specifying the shortname of the owning library) now show up in a search with\r
+ a context library of its owning library or below. For example, a Located URI\r
+ with an owner of SYS1 <emphasis role="strong">will</emphasis> cause its record to show up in a search with a\r
+ context OU of BR1 or SYS1, regardless of depth scoping.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Set a JavaScript cache token when <literal>autogen.sh</literal> is run, so that a subsequent\r
+ run of <literal>autogen.sh</literal> will automatically cause browsers to fetch refreshed\r
+ copies of generated files. This improves the usability of the catalog after\r
+ upgrades or certain configuration changes by preventing browsers from relying\r
+ on stale cached copies of these files.\r
+</simpara>\r
+</listitem>\r
+</itemizedlist>\r
+</simplesect>\r
+<simplesect id="_serials_enhancements">\r
+<title>Serials enhancements</title>\r
+<itemizedlist>\r
+<listitem>\r
+<simpara>\r
+Routing lists: it is now possible to define and print routing lists for\r
+ subscriptions.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Clone subscriptions: new functionality available in the alternate\r
+ serials control view to clone subscriptions, thereby speeding initial\r
+ setup of a lot of subscriptions.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+MFHD/Distribution summary methods: enable the summary method field for\r
+ generating summary holdings statements from the distribution and/or\r
+ the record entry (i.e., the MFHD). The four options that are available are:\r
+</simpara>\r
+<itemizedlist>\r
+<listitem>\r
+<simpara>\r
+Add to record entry\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Merge with record entry\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Use record entry only\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Do not use record entry\r
+</simpara>\r
+</listitem>\r
+</itemizedlist>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Advanced receiving: rename the previous serials receiving interface\r
+ to "advanced receiving". The new "receive" interface will now show items\r
+ from an entire subscription, but not allow you to receive directly into\r
+ a specific unit.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Unit-less receiving: new option for receiving serials into a <emphasis>no unit</emphasis>,\r
+ allowing items to be received but not unitized (i.e., created as a\r
+ circulating copy record). This allows issues to be received for\r
+ reading room or non-circulating use.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Caption/pattern enhancements:\r
+</simpara>\r
+<itemizedlist>\r
+<listitem>\r
+<simpara>\r
+The Caption/Pattern Wizard now includes a graphical way to include\r
+ regularity information (that is, the values typically conveyed in the <literal>85x</literal>\r
+ subfield <literal>$y</literal>).\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+The Alternate Serials Control interface can now import caption and pattern\r
+ information from the 85x fields of the MFHD record, allowing the\r
+ Caption/Pattern Wizard to be bypassed.\r
+</simpara>\r
+</listitem>\r
+</itemizedlist>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Can now create one-off issuances for unpredicted or unexpected serial issues.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Improvements to the copy template editor for serials, including the addition\r
+ of reasonable default values for some fields.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Various minor interface improvements, including new links between various pages\r
+ in the serials control interfaces and removing redundant questions from the holding code\r
+ mini-wizard.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Bugfixes to the batch receive interface.\r
+</simpara>\r
+</listitem>\r
+</itemizedlist>\r
+</simplesect>\r
+<simplesect id="_staff_client_improvements">\r
+<title>Staff client improvements</title>\r
+<itemizedlist>\r
+<listitem>\r
+<simpara>\r
+The client supports new hotkey sets that are selectable per workstation. In\r
+ addition, there is now a toggle for temporarily disabling hotkeys available\r
+ on the toolbar and in the admin menu.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+The client has a second toolbar for cataloging functions as well as options\r
+ controlling the presence and size of icons and presence and position of\r
+ labels. To support the preferences of individual staff, each workstation can\r
+ be configured differently. See the <emphasis role="strong">Admin → Workstation Administration →\r
+ Toolbars</emphasis> sub-menu for options.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Patron registration now supports "Suggested" fields that are configurable\r
+ per library. In addition, library settings allow required fields to be\r
+ adjusted, and it is possible to specify regular expressions to validate\r
+ input for many fields in the patron registration interface. Open <emphasis role="strong">Admin →\r
+ Local Administration → Library Settings Editor</emphasis> and filter on <literal>GUI</literal>.\r
+</simpara>\r
+</listitem>\r
+</itemizedlist>\r
+</simplesect>\r
+<simplesect id="_new_configuration_and_administration_settings">\r
+<title>New configuration and administration settings</title>\r
+<simplesect id="_new_literal_opensrf_xml_literal_settings">\r
+<title>New <literal>opensrf.xml</literal> settings</title>\r
+<simpara>(The path to these settings is relative to <literal>/opensrf/default/apps/</literal>).</simpara>\r
+<itemizedlist>\r
+<listitem>\r
+<simpara>\r
+<literal>open-ils.search/app_settings/default_CD_modifiers</literal>: parameters to\r
+ the cover density ranking function used to calculate relevance during\r
+ bibliographic searches.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+<literal>open-ils.trigger/app_settings/parallel/collect</literal>: number of parallel\r
+ processes that <literal>action_trigger_runner.pl</literal> should use when collecting events.\r
+ Setting this can decrease the time it takes for Action/Trigger processing to\r
+ run on large Evergreen databases.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+<literal>open-ils.trigger/app_settings/parallel/react</literal>: number of parallel\r
+ processes that <literal>action_trigger_runner.pl</literal> should use when processing event reactors.\r
+ Setting this can decrease the time it takes for Action/Trigger processing to\r
+ run on large Evergreen databases.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+<literal>open-ils.resolver/app_settings/cache_timeout</literal>: how long to cache results\r
+ from your OpenURL resolver.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+<literal>open-ils.resolver/app_settings/default_url_base</literal>: set to the base URL\r
+ of your OpenURL resolver.\r
+</simpara>\r
+</listitem>\r
+</itemizedlist>\r
+<simpara>In addition, the <literal>default_preferred_language</literal> and <literal>default_preferred_language_weight</literal>\r
+settings have been moved from the <literal>open-ils.storage</literal> simplesect to the <literal>open-ils.search</literal>\r
+simplesect of <literal>opensrf.xml</literal>.</simpara>\r
+</simplesect>\r
+<simplesect id="_new_administration_pages">\r
+<title>New administration pages</title>\r
+<simpara>The following new administration pages can all be accessed\r
+from the <literal>Admin | Server Administration</literal> menu item in the staff client:</simpara>\r
+<itemizedlist>\r
+<listitem>\r
+<simpara>\r
+Call Number Prefixes: Populates a drop down menu in the new Unified Copy /\r
+ Call Number Editor\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Call Number Suffixes: Populates a drop down menu in the new Unified Copy /\r
+ Call Number Editor\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Circulation Matchpoint Weights: Related to the in-database Circulation and\r
+ Hold Rule configuration changes\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Hold Matchpoint Weights: Related to the in-database Circulation and\r
+ Hold Rule configuration changes\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+MARC Coded Value Maps: Sets labels for fixed fields and extends the set of\r
+ values for display\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+MARC Record Attributes: Sets labels for fixed fields and extends the set of\r
+ values for display\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Weights Associations: Related to the in-database Circulation and\r
+ Hold Rule configuration changes\r
+</simpara>\r
+</listitem>\r
+</itemizedlist>\r
+</simplesect>\r
+<simplesect id="_new_library_settings">\r
+<title>New library settings</title>\r
+<informaltable\r
+frame="all"\r
+rowsep="1" colsep="1"\r
+>\r
+<tgroup cols="2">\r
+<colspec colname="col_1" colwidth="50*"/>\r
+<colspec colname="col_2" colwidth="50*"/>\r
+<thead>\r
+<row>\r
+<entry align="left" valign="top"> Label </entry>\r
+<entry align="left" valign="top"> Description</entry>\r
+</row>\r
+</thead>\r
+<tbody>\r
+<row>\r
+<entry align="left" valign="top"><simpara>Cataloging: Default copy status (fast add)</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Default status when a copy is created using the "Fast Add" interface.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>Cataloging: Default copy status (normal)</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Default status when a copy is created using the normal volume/copy creator interface.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Default Hotkeyset</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Default Hotkeyset for clients (filename without the .keyset). Examples: Default, Minimal, and None</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Default showing suggested patron registration fields</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Instead of All fields, show just suggested fields in patron registration by default.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Example for day_phone field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The Example for validation on the day_phone field in patron registration.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Example for email field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The Example for validation on the email field in patron registration.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Example for evening_phone field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The Example for validation on the evening_phone field in patron registration.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Example for other_phone field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The Example for validation on the other_phone field in patron registration.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Example for phone fields on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The Example for validation on phone fields in patron registration. Applies to all phone fields without their own setting.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Example for post_code field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The Example for validation on the post_code field in patron registration.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Horizontal layout for Volume/Copy Creator/Editor.</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Regex for day_phone field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The Regular Expression for validation on the day_phone field in patron registration.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Regex for email field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The Regular Expression for validation on the email field in patron registration.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Regex for evening_phone field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The Regular Expression for validation on the evening_phone field in patron registration.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Regex for other_phone field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The Regular Expression for validation on the other_phone field in patron registration.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Regex for phone fields on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The Regular Expression for validation on phone fields in patron registration. Applies to all phone fields without their own setting.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Regex for post_code field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The Regular Expression for validation on the post_code field in patron registration.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Require county field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The county field will be required on the patron registration screen.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Require day_phone field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The day_phone field will be required on the patron registration screen.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Require dob field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The dob field will be required on the patron registration screen.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Require email field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The email field will be required on the patron registration screen.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Require evening_phone field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The evening_phone field will be required on the patron registration screen.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Require other_phone field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>The other_phone field will be required on the patron registration screen.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show active field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show alert_message field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show alias field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show barred field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show calendar widget for dob field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>If set the calendar widget will appear when editing the dob field on the patron registration form.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show claims_never_checked_out_count field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show claims_returned_count field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show day_phone field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show dob field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show email field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show evening_phone field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show ident_value field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show ident_value2 field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show juvenile field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show master_account field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show other_phone field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show second_given_name field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Show suffix field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Suggest active field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Suggest alert_message field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Suggest alias field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Suggest barred field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Suggest claims_never_checked_out_count field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Suggest claims_returned_count field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Suggest day_phone field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Suggest dob field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Suggest email field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Suggest evening_phone field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Suggest ident_value field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Suggest ident_value2 field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Suggest juvenile field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Suggest master_account field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Suggest other_phone field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Suggest second_given_name field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Suggest suffix field on patron registration</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>GUI: Unified Volume/Item Creator/Editor</simpara></entry>\r
+<entry align="left" valign="top"><simpara>If true combines the Volume/Copy Creator and Item Attribute Editor in some instances.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>Printing: Custom Javascript File</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>Recalls: An array of fine amount, fine interval, and maximum fine.</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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]</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>Recalls: Circulation duration that triggers a recall.</simpara></entry>\r
+<entry align="left" valign="top"><simpara>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".</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>Recalls: Truncated loan period.</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Recalls: When a recall is triggered, this defines the adjusted loan period for the item. For example, "4 days" or "1 week".</simpara></entry>\r
+</row>\r
+</tbody>\r
+</tgroup>\r
+</informaltable>\r
+</simplesect>\r
+<simplesect id="_new_user_permissions">\r
+<title>New user permissions</title>\r
+<informaltable\r
+frame="all"\r
+rowsep="1" colsep="1"\r
+>\r
+<tgroup cols="2">\r
+<colspec colname="col_1" colwidth="50*"/>\r
+<colspec colname="col_2" colwidth="50*"/>\r
+<thead>\r
+<row>\r
+<entry align="left" valign="top"> Code </entry>\r
+<entry align="left" valign="top"> Description</entry>\r
+</row>\r
+</thead>\r
+<tbody>\r
+<row>\r
+<entry align="left" valign="top"><simpara>ADMIN_CODED_VALUE</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Create/Update/Delete SVF Record Attribute Coded Value Map</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>ADMIN_SERIAL_ITEM</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Create/Retrieve/Update/Delete Serial Item</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>ADMIN_SVF</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Create/Update/Delete SVF Record Attribute Defintion</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>CREATE_BIB_PTYPE</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Create Bibliographic Record Peer Type</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>CREATE_MONOGRAPH_PART</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Create monograph part definition.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>CREATE_PURCHASE_REQUEST</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Create User Purchase Request</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>CREATE_VOLUME_PREFIX</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Create prefix label definition.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>CREATE_VOLUME_SUFFIX</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Create suffix label definition.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>DEBUG_CLIENT</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Allows a user to use debug functions in the staff client</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>DELETE_BIB_PTYPE</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Delete Bibliographic Record Peer Type</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>DELETE_MONOGRAPH_PART</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Delete monograph part definition.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>DELETE_VOLUME_PREFIX</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Delete prefix label definition.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>DELETE_VOLUME_SUFFIX</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Delete suffix label definition.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>MAP_MONOGRAPH_PART</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Create/Update/Delete Copy Monograph Part Map</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>MARK_ITEM_MISSING_PIECES</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Allows the Mark Item Missing Pieces action.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>UPDATE_BIB_PTYPE</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Update Bibliographic Record Peer Type</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>UPDATE_HOLD_REQUEST_TIME</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Allows editing of a hold’s request time, and/or its Cut-in-line/Top-of-queue flag.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>UPDATE_MONOGRAPH_PART</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Update monograph part definition.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>UPDATE_PATRON_COLLECTIONS_EXEMPT</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Allows a user to indicate that a patron is exempt from collections processing</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>UPDATE_PICKLIST</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Allows update/re-use of an acquisitions pick/selection list.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>UPDATE_VOLUME_PREFIX</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Update prefix label definition.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>UPDATE_VOLUME_SUFFIX</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Update suffix label definition.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>UPDATE_WORKSTATION</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Allows update of a workstation during workstation registration override.</simpara></entry>\r
+</row>\r
+<row>\r
+<entry align="left" valign="top"><simpara>VIEW_USER_SETTING_TYPE</simpara></entry>\r
+<entry align="left" valign="top"><simpara>Allows viewing of configurable user setting types.</simpara></entry>\r
+</row>\r
+</tbody>\r
+</tgroup>\r
+</informaltable>\r
+</simplesect>\r
+</simplesect>\r
+</chapter>\r
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8"?>\r
-<chapter xml:id="releasenotes" xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="EN"\r
- xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink">\r
- <chapterinfo>\r
- <title>2.0 Feature List</title>\r
- </chapterinfo>\r
- \r
- \r
- <simplesect>\r
- <title>Circulation</title>\r
- <simplesect>\r
- <title>Patron Registration Enhancements</title>\r
- <itemizedlist>\r
- <listitem>Zip code information can be added to a local table which will pre-populate the City/State fields during patron registration. </listitem>\r
- <listitem>Added the ability to delete patrons by anonymizing the patron's personally identifiable data and purging the related data from other tables \r
- without destroying information important to the integrity of the database as a whole (does not delete the actor.usr row). </listitem>\r
- <listitem>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 \r
- 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 \r
- are not eligible for merging. </listitem>\r
- <listitem>Added quick links for staff to copy and paste patron address information. Information will paste in a standard mailing format. </listitem>\r
- <listitem>Patrons with an address alert (invalid/bad address) will be displayed at the top of a duplicates list. </listitem>\r
- <listitem>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 \r
- is done.</listitem>\r
- <listitem>The system recognizes certain categories of patrons like Card Canceled, Deceased, etc. and will not place holds for these categories. </listitem>\r
- \r
- <listitem>The patron record screen obscures certain information which can be considered sensitive. </listitem>\r
- <listitem>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 \r
- is done.</listitem>\r
- <listitem>Evergreen has the ability to automatically enter date, user, and location in messages and notes.</listitem>\r
- </itemizedlist> \r
- </simplesect>\r
- <simplesect>\r
- <title>Item Checkout enhancements</title>\r
- <itemizedlist>\r
- <listitem>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 \r
- screen. </listitem>\r
- <listitem>Evergreen has the ability to track hourly checkout stats. Self-check now operates by workstation and it's possible to gather statistics for checkouts \r
- between staff workstations and self-check workstations. (There is a workstation registration wizard built into the self-check UI.) </listitem>\r
- <listitem>Audible cue support, for successful and unsuccessful check-out, at self check-out stations has been added. This is customizable at the database level.</listitem>\r
- <listitem>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 \r
- such as library, ISBN and circ modifier to this pre-cat. </listitem>\r
- <listitem>The system supports sets or kits of items and has the ability to display the number of items and a list of descriptions. </listitem>\r
- <listitem>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 \r
- than there are unfrozen holds. This is an administration setting. </listitem>\r
- </itemizedlist> \r
- </simplesect>\r
- <simplesect>\r
- <title>Self Check module enhancements</title>\r
- <itemizedlist>\r
- <listitem>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 \r
- have configurable age-based parameters to prevent a double scan at checkout resulting in a renewal. </listitem>\r
- <listitem>For self check receipts, receipts include the same information for renewal as checkouts and includes notes on items that failed to renew. </listitem>\r
- <listitem>In the self-check UI, patrons can view holds and patron position vs. the number of circulating copies. </listitem>\r
- <listitem>The self check-out station displays holds ready for pickup, then removes each hold as the item is checked out. </listitem>\r
- <listitem>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 \r
- card processor like Paypal. The current supported processors include Authorize.net and Paypal.</listitem>\r
- </itemizedlist> \r
- </simplesect>\r
- <simplesect>\r
- <title>Item Check-in enhancements</title>\r
- <itemizedlist>\r
- <listitem>Evergreen supports a set number of claim returns allowed; beyond that, additional claim returns require supervisor authorization. This is based off the \r
- 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 \r
- returned count for a patron. In order to use this feature, staff needs to have the appropriate permission. </listitem>\r
- <listitem>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 \r
- 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, \r
- the item record retains both the actual date of check-in and backdate used. This information will display in the copy details interface. </listitem>\r
- <listitem>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. \r
- Staff is prompted with this amount, which can either be applied or modified or canceled. </listitem>\r
- </itemizedlist> \r
- </simplesect>\r
- <simplesect>\r
- <title>Holds Enhancements</title>\r
- <itemizedlist>\r
- <listitem>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 \r
- slip. Font, font size, and font weight are customizable. In addition, the hold slip may include a branch symbol (gif or jpg format) </listitem>\r
- <listitem>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 \r
- with public hold shelves.) </listitem>\r
- <listitem>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 \r
- to On Hold Shelf. </listitem>\r
- <listitem>Evergreen has the ability to ensure that manually edited copies (either deleting or changing to a non-holdable status) will have their holds \r
- retargeted. </listitem>\r
- <listitem>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 \r
- changed to On Hold Shelf. </listitem>\r
- <listitem>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 \r
- 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, \r
- 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 \r
- location.</listitem>\r
- <listitem>Staff can extend pickup deadlines for holds.</listitem>\r
- <listitem>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. \r
- 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 \r
- holds attached to a bibliographic record, including the ability to change the hold expiration date. This functionality is covered with current bib holds list \r
- interface. </listitem>\r
- <listitem>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 \r
- user that the item is already checked out to them and, if they have the permission, the system gives them the ability to override. </listitem>\r
- <listitem>The system supports the ability to place holds on titles with status on-order. For additional information, see the Acquisitions notes later in this \r
- document. </listitem>\r
- <listitem>Evergreen has the ability to designate specific org units that will not trigger a hold upon check-in. </listitem>\r
- <listitem>Evergreen added logic to hold targeting to skip branches that are closed at the time of hold placement and <varname>x</varname> time (<varname>x</varname> \r
- time being a set interval). This is \r
- 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 \r
- presumes there is another copy available at another branch. </listitem>\r
- <listitem>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 \r
- 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 \r
- 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. \r
- 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. </listitem>\r
- <listitem>The system offers the ability to secondarily sort the Holds Pull List by physical shelving location within the library.</listitem>\r
- <listitem>The system offers the ability to distinguish between staff-placed holds and patron-placed holds through a column in the holds interface. </listitem>\r
- <listitem>Hold cancellation can be displayed, along with information regarding the cancellation (e.g., cause, cancellation type, date, item, patron, etc.) </listitem>\r
- <listitem>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 \r
- searching. </listitem>\r
- <listitem>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. </listitem>\r
- <listitem>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 \r
- item was damaged. Since the patron had picked up the hold, it was considered filled. </listitem>\r
- <listitem>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 \r
- 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 \r
- in transit to the new location. A new holds slip is printed. </listitem>\r
- <listitem>The system supports a separate hold note field for staff use that can print on hold slip.</listitem>\r
- <listitem>Ability for patrons to view recently canceled holds and easily re-place holds.</listitem>\r
- </itemizedlist> \r
- </simplesect>\r
- </simplesect>\r
- <simplesect>\r
- <title>Staff Client Interface Enhancements</title>\r
- <itemizedlist>\r
- <listitem>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 \r
- in the OPAC to alert them to the bad address problem. System automatically blocks /unblocks a patron when an address is marked invalid/valid. </listitem>\r
- <listitem>Ability to have the staff client automatically minimize after a settable period of inactivity to protect patron privacy. This is controlled through an org \r
- unit setting.</listitem>\r
- <listitem>Summary of bills, checkouts, and holds are visible from all of the patron screens.</listitem>\r
- <listitem>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 \r
- payments. Fines history detail includes more information including location and time/date where item was returned and much more. </listitem>\r
- <listitem>More streamlined display of copy information including number of copies, copy status, and number of holds in both staff client interface and patron \r
- OPAC.</listitem>\r
- <listitem>The system supports the ability to edit item records from any item record access point. </listitem>\r
- <listitem>From holding maintenance or item status by barcode, you can retrieve more item details. For example, total circulations by current and previous year, last \r
- status change, last checkout date & works station, last checkin time and workstation, and more. </listitem>\r
- <listitem>The system includes a separate date field for the last change to the item in the item record. </listitem>\r
- <listitem>In the item record, the system displays total check-outs and renewals for year-to-date, previous year, and lifetime. </listitem>\r
- <listitem>Better audio signal handling.</listitem>\r
- <listitem>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 \r
- 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 \r
- color change) or audibly. </listitem>\r
- <listitem>The system supports two views of patron information: horizontal and vertical. </listitem>\r
- <listitem>From the patrons screen, under holds, clicking place hold will bring up an embedded catalog. Placing a hold from the embedded catalog will automatically \r
- generate a hold for the current account of the patron you are viewing. </listitem>\r
- <listitem>The system supports a new messages (notes) UI in the info tab of the patron screen. </listitem>\r
- <listitem>The system supports a new interface that shows the most recent activity on the workstation (checkout/checkin/ renewal/ patron-reg activity, with links to \r
- relevant patron from each item). This would be helpful to a supervisor trying to backtrack an issue to assist a staff member. </listitem>\r
- <listitem>The system now captures and displays check-in and workstation history. </listitem>\r
- <listitem>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 \r
- 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 \r
- display as an alert. </listitem>\r
- <listitem>Under grocery billings in Evergreen, billing type can be pre-populated with a list of common fine events (such as types and costs). </listitem>\r
- <listitem>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 \r
- by default. </listitem>\r
- <listitem>Backend support for other types of receipts (like holds/fines).</listitem>\r
- </itemizedlist> \r
- </simplesect>\r
- <simplesect>\r
- <title>OPAC and My Account Enhancements</title>\r
- <itemizedlist>\r
- <listitem>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 \r
- implementations for social networking features. </listitem>\r
- <listitem>Patron passwords are now more flexible in length and content (shorter and numeric-only passwords are now allowed). Libraries can set minimum and maximum \r
- limits on password length in Password format in the Library Settings Editor. </listitem>\r
- <listitem>Patrons can select a username, which can then be used to access OPAC and self check-out stations.</listitem>\r
- <listitem>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 \r
- will be marked as pending in the patron's file until a staff member verifies the new address and completes the change. </listitem>\r
- <listitem>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 \r
- 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 \r
- to take into consideration their avg circulation time, hold wait time or other factors like transit time which might influence hold wait estimates. </listitem>\r
- <listitem>Patrons can title their bookbags (aka reading list) and place holds from it. </listitem>\r
- <listitem>Backend support has been developed to allow patrons to waive certain kinds of notices. </listitem>\r
- <listitem>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 \r
- on an approximately daily basis.</listitem>\r
- </itemizedlist>\r
- </simplesect>\r
- <simplesect>\r
- <title>Billing, Collections and Fine/Fee Enhancements</title>\r
- <itemizedlist>\r
- <listitem>Fines now consistently link to item record details.</listitem>\r
- <listitem>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 \r
- type. When adding note, the current text shows as default in a pop-up window, so it can be appended or over-written. </listitem>\r
- <listitem>Staff and users can now only pay using the latest user data, which prevents accidental/duplicate payments against the same transaction or against stale \r
- data. </listitem>\r
- <listitem>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 \r
- 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. </listitem>\r
- <listitem>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 \r
- 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 \r
- any refundable transaction. </listitem>\r
- <listitem>Evergreen provides 3 distinct and independent types of blocks: system, manual and collections. Manual and collections are set manually by staff. </listitem>\r
- <listitem>A new penalty type of <varname>PATRON_IN_COLLECTIONS</varname> has been added. Its set when the collections agency puts the patron into collections, staff can define the blocks \r
- 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 \r
- CIRC desk).</listitem>\r
- </itemizedlist> \r
- </simplesect>\r
- <simplesect>\r
- <title>Action/Triggered Event and Notice Enhancements</title>\r
- <itemizedlist>\r
- <listitem>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 \r
- 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 \r
- SC to view all notices or cancel all pending notices.</listitem>\r
- <listitem>The system has the ability to cancel unsent notices before they are sent and the ability to search pending notices by item barcode.</listitem>\r
- <listitem>Administrators can choose to implement a collections warning prior to sending patrons to collections. When the account balance of the patron meets a \r
- 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 \r
- 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 \r
- <systemitem class="protocol">SCP</systemitem> and <systemitem class="protocol">FTP</systemitem>.</listitem>\r
- </itemizedlist> \r
- </simplesect>\r
- <simplesect>\r
- <title>Acquisitions</title>\r
- <itemizedlist>\r
- <listitem>From within the general acquisitions search page, users are able to search on many fields in the acquisitions /serials workflow. For example on attributes \r
- of invoices, purchase orders, selection lists, bib records, etc.</listitem>\r
- <listitem>General catalog searching is now supported for explicit truncation/wildcard searches.</listitem>\r
- <listitem>Acquisitions line item searches support NOT searches. </listitem>\r
- <listitem>Money can be transferred from one fund to another (or to none).</listitem>\r
- <listitem>All transactions (except batch EDI delivery to vendors) post in real time including: purchase orders, invoices, fund balances, vendors balances, vendor \r
- statistics and history. EDI delivery delay is configurable at the system level admin interface.</listitem>\r
- <listitem>In the User Interface, users now have access to all active funds, spanning multiple years, in the various ordering/invoicing/etc interfaces.</listitem>\r
- <listitem>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 \r
- to selectively roll certain funds over, while not rolling over others. </listitem>\r
- <listitem> Evergreen handles validation of ordering, receiving,and invoicing processes, using validated data, to satisfy auditor requirements. In the staff client, \r
- there is a menu option which allows staff to locate the PO that resulted in the purchase of that copy.</listitem>\r
- <listitem>Selection lists are collections of bibliographic records (short or full) that temporarily store titles being considered for purchase. Selection lists can be \r
- shared for collaborative input.</listitem> \r
- <listitem>Library staff have the ability to create distribution formulas for ease of receiving, processing and distributing materials. Branch, shelving location, and fund need \r
- 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 \r
- 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 \r
- 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 \r
- 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 \r
- dropdown for users to see.</listitem>\r
- <listitem>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 \r
- 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 \r
- 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. </listitem>\r
- <listitem>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 \r
- OPAC.</listitem>\r
- <listitem> The system supports claiming, specifically there is:\r
- <itemizedlist>\r
- <listitem>a place to store the default claim interval for each vendor</listitem>\r
- <listitem>a way to show the selected claim date during the order</listitem>\r
- ` <listitem>a way to show the selected claim date during the order</listitem>\r
- <listitem>a way to override the claim date during order</listitem>\r
- <listitem>a way to list items/orders that have reached the claim date.</listitem>\r
- </itemizedlist>\r
- A list of items that meet claims requirements can be generated, but claims must be initiated by librarians. </listitem>\r
- <listitem>From the UI, staff can access the lineitem and PO history. Entries in the history table are ordered from most recent to oldest.</listitem>\r
- <listitem>The purchase order printout is customizable, including the ability to break up a single order into separate purchase orders. Also, staff can print groups \r
- 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 \r
- in the PO interface of the existence/number of attached notes. </listitem>\r
- <listitem>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. \r
- The summary information includes: total price, total # lineitems, and total # of copies. Additionally, staff can do a PO search by vendor for all \r
- activated-but-not-yet-sent Pos (i.e., show me what we are about to order) and view the results.</listitem>\r
- <listitem>The system supports flagging prepaid orders so that invoicing is handled correctly.</listitem>\r
- <listitem>The system allows building orders based on templates (distribution formulas); by shelving location or owning library.</listitem>\r
- <listitem>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 \r
- 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 \r
- reports records from the vendor, which are then automatically inserted into the order records. </listitem>\r
- <listitem>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 \r
- menu entry for cancel cause.</listitem>\r
- <listitem>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 \r
- search interface (for the general case) which gives finer detail on EDI orders and the ability to reset failed outbound EDI deliveries. </listitem>\r
- <listitem>Pending final UI work in the OPAC, the system has the ability to allow patrons to place volume level and issue level holds. </listitem>\r
- <listitem>Ability to create and print routing worksheets for manual receiving processes.</listitem>\r
- <listitem>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 \r
- 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 \r
- 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 \r
- the public OPAC. This also applies to on-order records. </listitem>\r
- <listitem>Deleted bibs, callnumbers, copies, and patrons are retained for reporting purposes. Only patrons can be purged (by staff). “Deleted” items are more \r
- accurately described as “inactive.” However, patrons can now be complete purged, however this isn't recommended as you lose historical data.</listitem>\r
- <listitem> 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 \r
- via buckets in the copy edit interface.</listitem>\r
- <listitem>ACQ permissions control which workgroups have view/edit access to lineitem and catalog records while PO/PL and copy-level ownership and permission depths \r
- affect viewing in other, more location-specific interfaces. </listitem> \r
- <listitem>The system supports the ability to transfer patron holds queue from one bibliographic record to another, singly or in batch, while preserving the original \r
- hold order. </listitem>\r
- <listitem>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. \r
- Report templates can be built from this view for external processes.</listitem>\r
- <listitem>The system supports lineitem alerts, lineitem receive alerts, and lineitem detail alerts for EDI messaging.</listitem>\r
- <listitem>The system supports the ability to exclude some types of items from patron hold limits.</listitem>\r
- <listitem>There is support for new, locally defined, cancel reasons for EDI. There is also support for EG interpretation of EDI defined cancellation standards. </listitem>\r
- <listitem>The system supports the ability to send batches of orders to vendors, including orders for multiple accounts. The process of breaking outbound EDI messages \r
- into controlled and timed batch sizes is automated but settable to a specific, preferred, time interval.</listitem>\r
- <listitem>The system supports the ability to FTP orders directly to vendors and receive acknowledgements and status reports from vendors. More specifically, the \r
- system supports push and pull of files via <systemitem class="protocol">FTP</systemitem>, <systemitem class="protocol">SFTP</systemitem> and \r
- <systemitem class="protocol">SSH</systemitem>. </listitem>\r
- <listitem>The system supports MARC file import with PO data.</listitem>\r
- <listitem>The OPAC accepts enhanced content from the following vendors: ChiliFresh, Content Café & Novelist. (note that these are subscription services)\r
- </listitem>\r
- <listitem>You can set up vendor profiles and flag those that are active. Those that aren't can be saved for historical purposes.</listitem>\r
- <listitem>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 \r
- 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 \r
- is required, a confirmation dialog is inserted before sending the activate request. It indicates in the PO summary when a PO requires pre-payment. </listitem>\r
- <listitem>The system supports sequential barcode generation for ease of receiving and processing of new items and easily changing large groups of barcodes. There is \r
- 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 \r
- be entered in the admin interface to correctly calculate the barcodes.</listitem>\r
- <listitem>The system supports the ability to manually select libraries to receive items when partial orders are received or when items come in multiple deliveries. \r
- Orders with multiple copies will have an owning library per copy, so staff can pick which copies to mark as received.</listitem>\r
- <listitem>The system is compatible with Zebra Z4M thermal transfer printers. </listitem>\r
- <listitem>The system supports the ability to create, format and print spine labels. </listitem>\r
- <listitem>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 \r
- batch.</listitem>\r
- <listitem>The system has a configurable drop-down of alerts for line items that staff can control. </listitem>\r
- <listitem>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 \r
- record is updated automatically when the balance of a partial order is received. </listitem>\r
- <listitem>The system supports the ability to transfer item records from one bibliographic record to another. </listitem>\r
- <listitem>The system supports a worksheet for each title received, to include title, call number, number of copies received, distribution, and processing notes. </listitem>\r
- <listitem>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 \r
- <quote>real</quote> barcode.</listitem>\r
- <listitem>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 \r
- for all records while retaining the OCLC number in the record. The authority import now matches bib import in overlay/merge functionality.</listitem>\r
- <listitem>The system is fully compatible with OCLC Connexion for editing and transferring bibliographic and authority records (Z39.50). </listitem>\r
- <listitem>The system supports the ability to create a <quote>short bib</quote> record pending creation of the full MARC record. Short bibs can be created from a lineitem \r
- search. </listitem>\r
- <listitem>The system supports a utility to facilitate searching for full bibliographic records and create temporary <quote>short</quote> bibliographic records if no full \r
- records are found. </listitem>\r
- <listitem>Added the ability to perform electronic receiving and invoicing as follows: ability to receive electronic packing slips and invoices by purchase order or \r
- 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 \r
- amounts; ability to authorize payment within ILS.</listitem>\r
- <listitem>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 \r
- a fund).</listitem>\r
- <listitem>System supports simultaneous access to invoice interface.</listitem>\r
- <listitem>System supports a number of fields including: date, invoice number, invoice type, shipping vendor name, billing vendor, purchase order number, title, \r
- 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, \r
- invoice subtotal, freight charge, service charge, tax, invoice total, & vendor order was placed with. </listitem>\r
- <listitem>The system prevents overpayment in the invoice view page by linking invoices to PO/Lineitems. </listitem>\r
- <listitem>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 \r
- will print a voucher for whichever invoices have checked checkboxes.</listitem>\r
- <listitem>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.</listitem>\r
- <listitem>Staff can retrieve a PO or lineitem and access all the related invoicing data. </listitem>\r
- <listitem>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 \r
- a <guibutton>Reopen</guibutton> button, which requires permissions. </listitem>\r
- <listitem>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, \r
- the system supports invoicing extra copies when a vendor sends more copies than what staff ordered and staff decides to keep the extra copies. </listitem>\r
- <listitem>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 \r
- the owning library of the copies. </listitem>\r
- <listitem>When using full serials control, the default behavior for serials issue sorting and display in the holdings display will be reverse chronological order.</listitem>\r
- <listitem>Staff can label serials issuances with easily identifiable text such as <quote>YYYYMONTH</quote> or <quote>V.12 NO.1</quote>.</listitem>\r
- <listitem>In serials receiving staff are able to choose which issues to receive and distribute to which locations.</listitem> \r
- <listitem>Staff can add regular, supplemental, and index issues in the serials interface. </listitem>\r
- <listitem>The system supports purchase alert query (aka holds ratio report, holds alert report) compares holds to items and flags titles that need more copies. \r
- 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 \r
- 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 \r
- to generate a page of bib records that can have lineitems created from them to go into selection lists and/or POs.</listitem>\r
- </itemizedlist> \r
- </simplesect>\r
-</chapter>\r
</info>\r
<xi:include href="intro/intro_intro.xml"/>\r
<xi:include href="intro/about_evergreen.xml"/>\r
- <xi:include href="intro/releasenotes.xml"/>\r
+ <xi:include href="intro/release_notes.xml"/>\r
</part>\r
<part xml:id="opac">\r
<info>\r
<title>Core Staff Tasks</title>\r
</info>\r
<xi:include href="stafftasks/stafftasks_intro.xml"/>\r
- <xi:include href="stafftasks/booking.xml"/>\r
+ <!-- <xi:include href="stafftasks/booking.xml"/>\r
<xi:include href="stafftasks/acquisitions.xml"/>\r
<xi:include href="stafftasks/serials-gpls.xml"/>\r
<xi:include href="stafftasks/alternate_serial_control.xml"/>\r
- <xi:include href="stafftasks/cataloging.xml"/>\r
+ <xi:include href="stafftasks/cataloging.xml"/>-->\r
</part>\r
<part xml:id="admin">\r
<info>\r
<title>Administration</title>\r
</info>\r
<xi:include href="admin/admin-intro.xml"/> \r
- <xi:include href="admin/serversideinstallation_2.0.xml"/>\r
- <xi:include href="admin/staffclientinstallation.xml"/> \r
- <xi:include href="admin/Upgrading-Evergreen-2.0.xml"/>\r
- <xi:include href="admin/migratingdata_2.0.xml"/>\r
- <xi:include href="admin/AdminMisc.xml"/>\r
+ <!--<xi:include href="admin/AdminMisc.xml"/>\r
<xi:include href="admin/sip.xml"/>\r
<xi:include href="admin/z3950.xml"/>\r
<xi:include href="admin/troubleshooting.xml"/> \r
- <xi:include href="admin/admin-lsa_2.0.xml"/>\r
<xi:include href="admin/actiontriggers.xml"/>\r
<xi:include href="admin/admin-booking.xml"/>\r
<xi:include href="admin/acquisitions_admin_functions.xml"/>\r
- <xi:include href="admin/localization.xml"/>\r
+ <xi:include href="admin/localization.xml"/>-->\r
\r
</part>\r
<part xml:id="reports">\r
<title>Reports</title>\r
</info>\r
<xi:include href="reports/report-intro.xml"/>\r
- <xi:include href="reports/report-startingreporter.xml"/>\r
+ <!-- <xi:include href="reports/report-startingreporter.xml"/>\r
<xi:include href="reports/report-folder.xml"/>\r
<xi:include href="reports/report-create-template.xml"/>\r
<xi:include href="reports/report-generate-report.xml"/>\r
<xi:include href="reports/report-add-data-source.xml"/>\r
<xi:include href="reports/report-recurring-report.xml"/>\r
<xi:include href="reports/report-template-terminology.xml"/>\r
- <xi:include href="reports/report-exporting-report-templates-using-phppgadmin.xml"/>\r
+ <xi:include href="reports/report-exporting-report-templates-using-phppgadmin.xml"/>-->\r
</part>\r
\r
<part xml:id="software_integration">\r
<title>Development</title>\r
</info>\r
<xi:include href="development/development_intro.xml"/>\r
- <xi:include href="development/directoriesandFiles.xml"/> \r
+ <!-- <xi:include href="development/directoriesandFiles.xml"/> \r
<xi:include href="development/customizingstaffclient.xml"/>\r
<xi:include href="development/customize_opac.xml"/>\r
<xi:include href="development/OpenSRF_intro.xml"/>\r
<xi:include href="development/introduction_to_sql.xml"/>\r
<xi:include href="development/json.xml"/> \r
<xi:include href="development/supercat.xml"/>\r
-\r
+-->\r
</part>\r
<part xml:id="Appendices">\r
<info>\r
projects / working / Evergreen.git / commitdiff