+++ /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>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
projects / Evergreen-DocBook.git / commitdiff