From: Mike Rylander Date: Mon, 1 Apr 2013 16:44:25 +0000 (-0400) Subject: Proposed release-note-generator. Currently rough, but at least not entirely manual. X-Git-Url: https://old-git.evergreen-ils.org/?a=commitdiff_plain;h=refs%2Fheads%2Fcollab%2Fmiker%2Frelease-notes-proposal;p=working%2FEvergreen.git Proposed release-note-generator. Currently rough, but at least not entirely manual. Signed-off-by: Mike Rylander --- diff --git a/docs/RELEASE_NOTES_NEXT/Acquisitions/acq-interface-improvements.txt b/docs/RELEASE_NOTES_NEXT/Acquisitions/acq-interface-improvements.txt new file mode 100644 index 0000000000..303941cd09 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Acquisitions/acq-interface-improvements.txt @@ -0,0 +1,33 @@ +Acquisitions Purchase Order and other Interface Improvements +============================================================ + +Feature Summary +--------------- + +The following features, which primarily affect the user interface layer, +improve Acquisitions work flows. + + * Avoid double-activation of POs + * Disable invoice and cancel options for pending POs + * Disable zero-copy checkbox for activated POs + * Disable new charges for activated POs + * Replace "Shelving Location" with Copy Location + + * Rearranging "actions" drop-down + ** More consitency in actions applying to selected lineitems specifically + ** Things moved from the per-lineitem dropdown to the main one when + sensible. + ** Add to PO dialog added + ** You can no longer add lineitems to a PO if they're already on one. + ** Actions in dropdown now enabled/disabled differently depending on + the interface where it appears (PO vs Selection List vs Acq Search etc.) + + * Batch update for line items + ** Apply updates to all copies of all selected line items at once + ** Relies on a middle layer method that streams back information that + would suit a more asynchronous display in the future (rather than + simply reloading the page upon success, which it does now) + ** For failure cases, specific information about which line item cannot + be updated, and why, is available to the client, although taking + best advantage of this information for user-friendly display is left + to the future. diff --git a/docs/RELEASE_NOTES_NEXT/Acquisitions/acq_default_copy_count.txt b/docs/RELEASE_NOTES_NEXT/Acquisitions/acq_default_copy_count.txt new file mode 100644 index 0000000000..4ff5cc42d0 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Acquisitions/acq_default_copy_count.txt @@ -0,0 +1,8 @@ +New Feature: Default Number of Acquisistions Copies to Order +============================================================ +Acquisitions providers have a new "Default # Copies" field. When the value +is set, this number of copies will be automatically added to each lineitem +added to a purchase order for the provider. This takes place during PO +creation from a selection list or existing bib record and when a lineitem is +added to an existing purchase order. If a lineitem already has copies +attached, no default copies are added. diff --git a/docs/RELEASE_NOTES_NEXT/Acquisitions/acq_lineitem_order_ident.txt b/docs/RELEASE_NOTES_NEXT/Acquisitions/acq_lineitem_order_ident.txt new file mode 100644 index 0000000000..9315a3b8b1 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Acquisitions/acq_lineitem_order_ident.txt @@ -0,0 +1,22 @@ +Acquisitions Lineitem Order Identifiers +======================================= + +Staff now have the ability to specify the identifier value to use for +lineitems when communicating order information to vendors. This is +particularly important when a lineitem has, for example, multiple ISBNs. +Determining which ISBN is to act as the "order identifier" allows staff +to provide the most accurate order information to vendors. + +Supported identifier types include ISBN, ISSN, and UPC. Order identifier +values are relayed to vendors via EDI and print PO. + +Upgrade Notes +============= + +Two new permissions are added for this feature: + + * ACQ_SET_LINEITEM_IDENTIFIER + ** Allows staff to apply order identifiers to lineitems + * ACQ_ADD_LINEITEM_IDENTIFIER + ** Implies that new identifiers shall be added to linked bib records, + when a linkage exists. diff --git a/docs/RELEASE_NOTES_NEXT/Acquisitions/acq_marc_upload_defaults.txt b/docs/RELEASE_NOTES_NEXT/Acquisitions/acq_marc_upload_defaults.txt new file mode 100644 index 0000000000..e0e709fd6a --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Acquisitions/acq_marc_upload_defaults.txt @@ -0,0 +1,7 @@ +Acquisitions MARC Upload Form Persistence +========================================= +Adds a two-layer persistence mechanism for the acquisitions MARC file upload +interface. A set of org unit settings now exist for managing default values +for the interface. Additionally, for each field where no org unit setting +value is configured, the last-used value will be persisted locally and re- +used with subsequent loads of the interface. diff --git a/docs/RELEASE_NOTES_NEXT/Acquisitions/acq_po_detail_view.txt b/docs/RELEASE_NOTES_NEXT/Acquisitions/acq_po_detail_view.txt new file mode 100644 index 0000000000..001679483e --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Acquisitions/acq_po_detail_view.txt @@ -0,0 +1,12 @@ +Acquisitions Inline Item Detail View +==================================== + +Acquisitions selection lists and purchase order interfaces contain a new link +beside each lineitem which, when clicked, creates an inline grid of copies +linked to the lineitem. The grid contains the same information that displays +in the full copy edit grid (from clicking on the Copies(n) link). However, +the inline grid is read-only, so it displays much faster and does not require +the user to change visual contexts. + +Included along the top of the lineitem table is a new '✓ Expand' link which, +when clicked, expands or collapses the inline grid for all visible lineitems. diff --git a/docs/RELEASE_NOTES_NEXT/Administration/item-attribute-editor.txt b/docs/RELEASE_NOTES_NEXT/Administration/item-attribute-editor.txt new file mode 100644 index 0000000000..024429282e --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Administration/item-attribute-editor.txt @@ -0,0 +1,7 @@ +Direct access to Item Attribute Editor +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +You can now access the item attribute editor via Admin -> Local Admin -> Item +Attribute Editor. No copy record is loaded into the editor, but it is available to without first finding an item and loading it into the editor: + + * Configure copy templates. + * Hide fields in the copy editor. diff --git a/docs/RELEASE_NOTES_NEXT/Cataloging/marc-import-tag-stripping.txt b/docs/RELEASE_NOTES_NEXT/Cataloging/marc-import-tag-stripping.txt new file mode 100644 index 0000000000..7470dc09c5 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Cataloging/marc-import-tag-stripping.txt @@ -0,0 +1,28 @@ +MARC Import Tag Stripping +========================= + +Administrators can configure MARC tags which are removed from MARC records +imported via Z39.50 and the Vandelay MARC Import/Export UI (ACQ and non-ACQ). +Tags are organized into groups. Groups can be marked as optional or required. +For each tag, every instance of the tag (including all subfields) are removed +from the record. + +MARC fields which are contained within required ('always_apply') tag groups +are always removed from inbound records. No action is needed. Tag groups +which are optional will appear in MARC import interfaces (see below) allowing +staff to select which groups of tags to strip from incoming records at import +time. + +Interfaces Affected +------------------- + + * Admin UI + ** Admin => Server Administration => MARC Import Remove Fields + * Z39.50 Import + ** Cataloging => Import Record from Z39.50 + ** Optional groups appear with the other import options + * Vandelay + ** Cataloging => MARC Import/ExportVandelay + ** Acquisistions => Load Order Records + ** Optional groups appear with the other import options + diff --git a/docs/RELEASE_NOTES_NEXT/Cataloging/vandelay_default_match_set.txt b/docs/RELEASE_NOTES_NEXT/Cataloging/vandelay_default_match_set.txt new file mode 100644 index 0000000000..836b2e5f9d --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Cataloging/vandelay_default_match_set.txt @@ -0,0 +1,11 @@ +Vandelay Default Match Set +========================== +A new org unit setting to specify a default Record Match Set when +importing MARC records through the MARC Batch Import/Export interface. It does +not affect the default match set selected in acquisitions. If this +is set, it will not be possible to leave the Record Match Set field blank; +it may be necessary to define a default match set that replicates the current +default behavior. + +A new "Vandelay" org unit settings group is also created. + diff --git a/docs/RELEASE_NOTES_NEXT/Cataloging/z39_source_credentials.txt b/docs/RELEASE_NOTES_NEXT/Cataloging/z39_source_credentials.txt new file mode 100644 index 0000000000..eb74bcc6f6 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Cataloging/z39_source_credentials.txt @@ -0,0 +1,13 @@ +Storing Z39.50 Server Credentials +================================= + +In the Z39.50 configuration interface, staff now have the option to apply +z39.50 login credentials to each Z39.50 server at different levels of the +org unit hierarchy (similar to org unit settings). When credentials are set +for a Z39 server, searches against the z39 server will used the stored +credentials, unless other credentials are provided by the caller, in which +case the caller credentials are used. + +For security purposes, passwords may not be retrieved or reported on by staff. +Staff can only apply new values for credentials or clear existing ones. + diff --git a/docs/RELEASE_NOTES_NEXT/Circulation/calculated-proximity-adjustments.txt b/docs/RELEASE_NOTES_NEXT/Circulation/calculated-proximity-adjustments.txt new file mode 100644 index 0000000000..61a81a709b --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Circulation/calculated-proximity-adjustments.txt @@ -0,0 +1,10 @@ +Calculated Proximity Adjustments +================================ + +Allows customization to the way that Evergreen measures the distance between +org units for the purposes of 1) determining what copy at what org unit is best +suited for targeting a title-level hold, and 2) determining what hold is best +suited for fulfillment by a copy-in-hand at capture (checkin) time. The +customization is based on a table 'actor.org_unit_proximity_adjustment', with +certain matching criteria that the system compares to properties of the holds +and copies in question. diff --git a/docs/RELEASE_NOTES_NEXT/Circulation/circulation_patron_expiry_warning.txt b/docs/RELEASE_NOTES_NEXT/Circulation/circulation_patron_expiry_warning.txt new file mode 100644 index 0000000000..eebe3eb869 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Circulation/circulation_patron_expiry_warning.txt @@ -0,0 +1,9 @@ +New feature: "Warn patrons when their account is about to expire" +================================================================= +To give staff the ability to warn patrons when their account is about to +expire, the staff client can display an alert message on the patron information +window. A new library setting, `Warn patrons when their account is about to +expire` in the *Circulation* section of the *Library Settings Editor*, +determines how many days in advance of a patron's account expiry date the alert +should be displayed. By default, warnings about upcoming patron account expiry +dates are not displayed. diff --git a/docs/RELEASE_NOTES_NEXT/Circulation/custom-best-hold-selection.txt b/docs/RELEASE_NOTES_NEXT/Circulation/custom-best-hold-selection.txt new file mode 100644 index 0000000000..4fb440a9f8 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Circulation/custom-best-hold-selection.txt @@ -0,0 +1,16 @@ +Custom best-hold selection sort order +===================================== + +The ranking algorithm that chooses the best hold to target a copy in +hand at a capture time used to be fairly simple. It had two modes, FIFO +and not-FIFO, and that was it. + +This change allows full configuration of that algorithm. In other +words, when the system captures a copy and sets out to evaluate what +hold, if any, that copy might best fulfull, site staff of sufficient +permission level are now empowered to choose exactly which comparisons +the systems makes in what order. This gives said staff much greater +flexibililty than they have today over holds policy. + +For more information, see the included tech spec documents. + diff --git a/docs/RELEASE_NOTES_NEXT/Client/about_about.txt b/docs/RELEASE_NOTES_NEXT/Client/about_about.txt new file mode 100644 index 0000000000..32b716dae9 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Client/about_about.txt @@ -0,0 +1,13 @@ +New feature: add "about:about" to developer menu in staff client +================================================================= + +about:about gives access to various XULRunner diagnostic tools. +Useful ones include: + +about:buildconfig:: + Get information about how the staff client is built. +about:config:: + Tweak XULRunner settings. +about:memory:: + Get detailed information about the memory usage of the staff + client. diff --git a/docs/RELEASE_NOTES_NEXT/Client/clickable_patron_indicators.txt b/docs/RELEASE_NOTES_NEXT/Client/clickable_patron_indicators.txt new file mode 100644 index 0000000000..4d0baeec0b --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Client/clickable_patron_indicators.txt @@ -0,0 +1,6 @@ +New feature: Clickable Patron Indicators +======================================== +When retrieving a patron record, staff can now click on the indicators listed +beneath the patron's name and launch the related tabs. + +For example, clicking on (See Notes) will open the associated patron's notes. diff --git a/docs/RELEASE_NOTES_NEXT/Client/hold_patron_name.txt b/docs/RELEASE_NOTES_NEXT/Client/hold_patron_name.txt new file mode 100644 index 0000000000..30891c7b52 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Client/hold_patron_name.txt @@ -0,0 +1,7 @@ +Show Hold Patron Name in TPac +============================= + +When looking up patron information for hold placement via the staff client in +TPac the hold patron name is now shown next to the entered barcode. In the event +that the barcode is not found a notice is displayed and the submit button is +disabled until a valid barcode is entered or the staff member is switched to. diff --git a/docs/RELEASE_NOTES_NEXT/Client/notify_csv.txt b/docs/RELEASE_NOTES_NEXT/Client/notify_csv.txt new file mode 100644 index 0000000000..0529726925 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Client/notify_csv.txt @@ -0,0 +1,78 @@ +New Feature: Generic CVS Notification Generator/Receiver +======================================================== + +New Action/Trigger template and sample event definitions for creating a CSV +export file for various patron actions, primarily for the purpose of creating +patron notices via external notification mechanisms. + +The reference implementation for this development is the TalkingTech iTiva +product, which consumes CSV files for generating phone/text notifications and +produces CSV results files for informing the ILS of notification statuses. +The template and send/receive scripts, however, should be generic enough to +create CSV for any type of 3rd-party notification product. + +Action/Trigger Event Definition Configuration +--------------------------------------------- + + * Supported hook core types include *circ*, *ahr*, *ausp*, and *au* + * Reactor is *ProcessTemplate* + +Event Environment Requirements +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + + * Patron object with card + * copy object + ** circ.target_copy + ** hold.current_copy + * Org unit + ** circ.circ_lib + ** ahr.pickup_lib + ** ausp.org_unit + ** patron.home_ou + +Not all fields are relevent to all notice types. + +Required Event Parameters +~~~~~~~~~~~~~~~~~~~~~~~~~ + + * notify_media (e.g. phone) + * notify_type (e.g. overdue) + * notify_level (e.g. "1" -- first overdue) + +The set of options for each event parameter is dependent on the 3rd-party +processing the CSV file. + +iTiva Event Parameter Options +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + + * notify_media + ** V (voice) + ** T (text) + * notify_level + ** 1 (1st notice) + ** 2 (2nd notice) + ** 3 (3rd notice) + * notify_type + ** FINES + ** OVERDUE + ** PREOVERDUE + ** PRERESERVE + ** RECALL + ** RESERVE + ** RESERVECANCEL + ** RESERVEEXPIRE + ** SUSPEND + +Push/Fetch Scripts +------------------ + + * action_trigger_aggregator.pl collects event output from requested event + definitions and stitches them together into a single file, which is sent + via (s)FTP to the 3rd party. + * Why don't we use the SendFile reactor directly? + ** The final file is meant to be a collection of event-def outputs, not + the output from a single event def + ** The final file may be too large to reasonably store directly in a + single action/trigger event_output row. + * csv_notify_fetcher.pl retrieves responses from the 3rd party and applies + the statuses to the async_output of each notified event. diff --git a/docs/RELEASE_NOTES_NEXT/Client/search-prefs.txt b/docs/RELEASE_NOTES_NEXT/Client/search-prefs.txt new file mode 100644 index 0000000000..0b61f64fa5 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Client/search-prefs.txt @@ -0,0 +1,14 @@ +Staff client search preferences +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +Staff can now set workstation-level search preferences through Admin -> +Workstation Administration -> Set Search Preferences. + + * Default Search Library sets the library that is searched by default from + the advanced search page and the portal page. + * Preferred library is used to identify copies that should display first. + * Advanced search default pane allows staff to set the numeric or expert + searches as the default search tab. + +The option to change the preferred search library from the search results page +is no longer available when logged into the staff client. + diff --git a/docs/RELEASE_NOTES_NEXT/Client/show_holds_on_bib.txt b/docs/RELEASE_NOTES_NEXT/Client/show_holds_on_bib.txt new file mode 100644 index 0000000000..27b69bd2f6 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Client/show_holds_on_bib.txt @@ -0,0 +1,7 @@ +Show Holds On Bib Menu Option +============================= + +Add direct "Show holds on bibs" menu option from item checkin, item status, +and patron hold interfaces. This gives staff a quicker way of viewing who +else has holds on an item instead of having to click an option to view the +bib record, then clicking into the menus to view holds. diff --git a/docs/RELEASE_NOTES_NEXT/Client/toolbar_perms.txt b/docs/RELEASE_NOTES_NEXT/Client/toolbar_perms.txt new file mode 100644 index 0000000000..111ab52a36 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Client/toolbar_perms.txt @@ -0,0 +1,12 @@ +Upgrade Notes +------------- +Custom toolbar permissions +~~~~~~~~~~~~~~~~~~~~~~~~~~ +With the addition of more granular permissions for configuring a custom +toolbars, the ADMIN_TOOLBAR permission alone will not allow users to +configure a custom toolbar. This permission must now be used in conjunction +with one or more of the following permissions: + +* ADMIN_TOOLBAR_FOR_ORG +* ADMIN_TOOLBAR_FOR_USER +* ADMIN_TOOLBAR_FOR_WORKSTATION diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/alternate_graphic_fields.txt b/docs/RELEASE_NOTES_NEXT/OPAC/alternate_graphic_fields.txt new file mode 100644 index 0000000000..82729cd584 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/OPAC/alternate_graphic_fields.txt @@ -0,0 +1,67 @@ +Display alternate graphic (880) fields +====================================== + +By default, Evergreen displays alternate graphic fields, if any, for +contributors (1xx / 7xx), titles (245), edition statements (250), imprints +(260), notes (5xx), subjects (6xx), and series (4xx / 8xx) in search results and record details +per the Library of Congress MARC21 specifications: + +* http://www.loc.gov/marc/bibliographic/bd880.html +* http://www.loc.gov/marc/bibliographic/ecbdcntf.html +* http://www.loc.gov/marc/bibliographic/ecbdmulti.html (Model A) + +Default display +--------------- +In general, alternate graphic fields display below the corresponding +primary field. One exception is the attribution summary on the record details +page, in which the alternate graphic field contents display between the +primary field content and the attribution statement. To support CSS +customizations, HTML elements for the graphic fields have the class attribute +value `graphic880`. + +Implementation details +---------------------- +The template file `parts/misc_util.tt2` defines two macros for retrieving +linked 880 fields: + +* `get_graphic_880s`: given a _target_field_ scalar value representing a MARC + field tag, populate the _graphic_880s_ list with hashes containing the + target field tag and any graphic fields linked to that particular tag, with + the values for each being a simple concatenation of all subfields that are + not control subfields (per + http://www.loc.gov/marc/bibliographic/ecbdcntf.html). The structure of the + `graphic_880s` list is as follows: ++ +------------------------------------------------------------------------ +[ + { + "primary": {"occur": 01, "value": "foo foo"}, + "graphic": [ + { + "occur": 01, + "value": "bar bar", + "orient": "rtl", + "script": "CJK" + } + ] + } +] +------------------------------------------------------------------------ +* `get_linked_880s` macro iterates over the content of the `linked_fields` + list, in which each element of the list to be a scalar representing the $6 + control subfield link info. The macro populates the `graphics` list with a + set of graphic field hashes with the following structure: ++ +------------------------------------------------------------------------ +[ + { + "occur": 01, + "value": "bar bar", + "orient": "rtl", + "script": "CJK" + } +] +------------------------------------------------------------------------ + +`misc_util.tt2` preserves legacy attribute lists to enable previous TPAC +customizations to continue to function normally. diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/deprecate-jspac.txt b/docs/RELEASE_NOTES_NEXT/OPAC/deprecate-jspac.txt new file mode 100644 index 0000000000..cca48ab5c6 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/OPAC/deprecate-jspac.txt @@ -0,0 +1,5 @@ +Removal of JSPAC +^^^^^^^^^^^^^^^^ +TPAC is now the default catalog in Evergreen. The default apache configuration +now points to TPAC, staff client OPAC options now point to TPAC, and the JSPAC +to TPAC toggle has been removed from the portal page. diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/hide-user-prefs.txt b/docs/RELEASE_NOTES_NEXT/OPAC/hide-user-prefs.txt new file mode 100644 index 0000000000..e54894cc0e --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/OPAC/hide-user-prefs.txt @@ -0,0 +1,8 @@ +Options to Hide Some User Preferences +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +The config.tt2 file now provides options to disable phone notification options, password changes, and e-mail address changes in TPAC. These options are useful +for libraries that do not do phone notifications and for those that use +centralized authentication. + +Note the ability to disable user name changes is already available through the +Library Settings editor. diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/marc21-feeds.txt b/docs/RELEASE_NOTES_NEXT/OPAC/marc21-feeds.txt new file mode 100644 index 0000000000..0b861a90e2 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/OPAC/marc21-feeds.txt @@ -0,0 +1,8 @@ +MARC21 Feeds from OpenSearch +============================ + +In addition to the already supported formats, you can now get raw MARC21 from +OpenSearch feeds, à la: + + http:///opac/extras/opensearch/1.1/-/marc21?searchTerms=piano + diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/public-copy-notes.txt b/docs/RELEASE_NOTES_NEXT/OPAC/public-copy-notes.txt new file mode 100644 index 0000000000..b0a38c8d76 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/OPAC/public-copy-notes.txt @@ -0,0 +1,3 @@ +Public Copy Notes +^^^^^^^^^^^^^^^^^ +Public copy notes are now visible in TPAC. diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/queryparser_changes.txt b/docs/RELEASE_NOTES_NEXT/OPAC/queryparser_changes.txt new file mode 100644 index 0000000000..d25609658b --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/OPAC/queryparser_changes.txt @@ -0,0 +1,25 @@ +Search Changes +============== +A number of changes have been made to search to allow more control and improve +performance. These changes and their associated configurations are global to +the entire system and can not be configured on a per-library basis. + +Amongst other things the new search code fixes: + +* Inability to use statuses and locations as part of a larger query +* Invalid queries being generated from advanced searches +* Some timeouts from backend code taking too long to preform a search +* Some filters being one-use only +* Negations not working properly where multiple indexes are involved + +Improvements include: + +* Exact matches on input should be more likely to float to the top of results +* Non-English stemming can be used, alongside or instead of English stemming +* Entered search terms can be found across multiple indexes + +Default configuration is geared towards English but is easily changed. In a +production environment changes will likely require re-indexing, however. + +The upgrade script could be pre-tweaked to install desired configuration before +it builds and/or re-builds many of the indexes. diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/search-deleted.txt b/docs/RELEASE_NOTES_NEXT/OPAC/search-deleted.txt new file mode 100644 index 0000000000..5e1d8a0735 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/OPAC/search-deleted.txt @@ -0,0 +1,11 @@ +Searching for deleted records +============================= + +Evergreen now supports searching for deleted records via the '#deleted' +QP modifier. + +In order to support this, sites must enable the +'ingest.metarecord_mapping.preserve_on_delete' internal flag. It is off by +default since the ability to search for deleted records requires keeping +metarecord mappings around when bibs are deleted, which may not be desirable +for the typical site. diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/search-record-date-filters.txt b/docs/RELEASE_NOTES_NEXT/OPAC/search-record-date-filters.txt new file mode 100644 index 0000000000..84dea19daa --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/OPAC/search-record-date-filters.txt @@ -0,0 +1,11 @@ +Two new QP filters: create_date and edit_date +============================================= + +These filter on the fields of the same name in biblio.record_entry. + +e.g. + * create_date(,2013-02-01) => records created before 2013-02-01 + * create_date(2013-02-01) => records created since 2013-02-01 + * create_date(2013-02-01,2013-02-28) => records created in Feb 2013 + * create_date(yesterday) => records since created yesterday + diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/tpac-ou-hiding.txt b/docs/RELEASE_NOTES_NEXT/OPAC/tpac-ou-hiding.txt new file mode 100644 index 0000000000..adebd77129 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/OPAC/tpac-ou-hiding.txt @@ -0,0 +1,20 @@ +TPAC Org Unit Hiding +==================== + +Adds support for the opac.org_unit_hiding.depth org unit setting to +TPAC, which makes out-of-scope org units disappear (except when +explicitly requested). + +Org unit hiding is based on the physical_loc (Physical Location) param / +cookie, which is the closest analog to 'ol' (original location), from +which it was based in the JSPAC. + +UI Changes +---------- + + * All search org unit selectors + * Holds pickup lib selector + * Copy summary in search results page + * Copy list in search results page + * Copy summary in record detail page (which controls the copy grid). + * Hold summary in record detail page diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/tpac_bookbag_callnumbers.txt b/docs/RELEASE_NOTES_NEXT/OPAC/tpac_bookbag_callnumbers.txt new file mode 100644 index 0000000000..a6a53c5584 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/OPAC/tpac_bookbag_callnumbers.txt @@ -0,0 +1,15 @@ +New Feature: Show local call number in TPAC My Lists display +============================================================ + +If an opac-visible call number exists that is owned by an org unit +relevant to the patron, show the most relevant call number label +and owning branch name in the My Lists display for each record in +the list. Call number is displayed in both saved and temporary lists. + +A call number is considered relevant if its owner is one of: + +physical location library +preferred library (plib, home, etc.) +search library + +If no relevant call number is found, no call number is diplayed. diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/tpac_google_books_preview.txt b/docs/RELEASE_NOTES_NEXT/OPAC/tpac_google_books_preview.txt new file mode 100644 index 0000000000..c56582572c --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/OPAC/tpac_google_books_preview.txt @@ -0,0 +1,12 @@ +TPAC: Google Books preview +========================== + +Setting `ctx.google_books_preview` to `1` in the TPAC `config.tt2` +configuration file will cause the TPAC to check to see, as part of the record +details view, if Google Books has an online preview available. If it does, +then a preview button will be displayed in the book cover image location. +If the user then clicks the preview button, the preview will load below the +title of the book in the record details page. + +By default, this functionality is disabled to protect the privacy of users +who might not want to share their browsing behaviour with Google. diff --git a/docs/RELEASE_NOTES_NEXT/README b/docs/RELEASE_NOTES_NEXT/README index c23186623e..4f3120863f 100644 --- a/docs/RELEASE_NOTES_NEXT/README +++ b/docs/RELEASE_NOTES_NEXT/README @@ -1,6 +1,10 @@ -New features should be accompanied by a file in this directory. The file should -be in asciidoc format and contain enough description to enable the -documentation team to write something coherent about the new functionality. The -name of the file should match the feature. No numbering, etc. is required. With -each release, the contents of this directory will be appended to the release -notes and removed from this directory. +New features should be accompanied by a file in this directory for general +features, infrastructure, performance enhancements or the like, or a +directory below this for area- or "module"-specific addtions and changes. + +The file should be in asciidoc format and contain enough description to +enable the documentation team to write something coherent about the new +functionality. The name of the file should match the feature. No numbering, +etc. is required. With each release, the contents of this directory will be +appended to the release notes and removed from this directory. + diff --git a/docs/RELEASE_NOTES_NEXT/Serials/serial_control_embedded_alt_interfaces.txt b/docs/RELEASE_NOTES_NEXT/Serials/serial_control_embedded_alt_interfaces.txt new file mode 100644 index 0000000000..f0986fed21 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Serials/serial_control_embedded_alt_interfaces.txt @@ -0,0 +1,13 @@ +Serial Control: Embed Alternate Interfaces +========================================== +As another step toward a unified interface, the serial control subscription +editor now consists of an embedded version of the alternate control. This +reduces duplication of both code and documentation, and smoothes the eventual +transition to a single interface. + +In order to not lose any essential features, the following additions were made +to the new combination editor: + +* note editors on subscriptions and distributions +* labeled dropdown for distribution summary options ("Add to record entry", "Use record entry only", etc.) +* legacy record entry linkage setup (Allows one to tie a distribution's information to a particular serial record entry (i.e. a MFHD record)) diff --git a/docs/RELEASE_NOTES_NEXT/Serials/serial_control_special_statuses.txt b/docs/RELEASE_NOTES_NEXT/Serials/serial_control_special_statuses.txt new file mode 100644 index 0000000000..5b4e3c3463 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Serials/serial_control_special_statuses.txt @@ -0,0 +1,7 @@ +Serial Control: Set Special Statuses +==================================== +The Serial Control interface prevents direct editing of serial item statuses +for data integrity reasons. As an alternative to direct control, the interface +now offers new menu options for setting items to 'claimed', 'not held', and +'not published'. Note that these statuses are still currently useful for +reporting and display purposes only. diff --git a/docs/RELEASE_NOTES_NEXT/about_about.txt b/docs/RELEASE_NOTES_NEXT/about_about.txt deleted file mode 100644 index 32b716dae9..0000000000 --- a/docs/RELEASE_NOTES_NEXT/about_about.txt +++ /dev/null @@ -1,13 +0,0 @@ -New feature: add "about:about" to developer menu in staff client -================================================================= - -about:about gives access to various XULRunner diagnostic tools. -Useful ones include: - -about:buildconfig:: - Get information about how the staff client is built. -about:config:: - Tweak XULRunner settings. -about:memory:: - Get detailed information about the memory usage of the staff - client. diff --git a/docs/RELEASE_NOTES_NEXT/acq-interface-improvements.txt b/docs/RELEASE_NOTES_NEXT/acq-interface-improvements.txt deleted file mode 100644 index 303941cd09..0000000000 --- a/docs/RELEASE_NOTES_NEXT/acq-interface-improvements.txt +++ /dev/null @@ -1,33 +0,0 @@ -Acquisitions Purchase Order and other Interface Improvements -============================================================ - -Feature Summary ---------------- - -The following features, which primarily affect the user interface layer, -improve Acquisitions work flows. - - * Avoid double-activation of POs - * Disable invoice and cancel options for pending POs - * Disable zero-copy checkbox for activated POs - * Disable new charges for activated POs - * Replace "Shelving Location" with Copy Location - - * Rearranging "actions" drop-down - ** More consitency in actions applying to selected lineitems specifically - ** Things moved from the per-lineitem dropdown to the main one when - sensible. - ** Add to PO dialog added - ** You can no longer add lineitems to a PO if they're already on one. - ** Actions in dropdown now enabled/disabled differently depending on - the interface where it appears (PO vs Selection List vs Acq Search etc.) - - * Batch update for line items - ** Apply updates to all copies of all selected line items at once - ** Relies on a middle layer method that streams back information that - would suit a more asynchronous display in the future (rather than - simply reloading the page upon success, which it does now) - ** For failure cases, specific information about which line item cannot - be updated, and why, is available to the client, although taking - best advantage of this information for user-friendly display is left - to the future. diff --git a/docs/RELEASE_NOTES_NEXT/acq_default_copy_count.txt b/docs/RELEASE_NOTES_NEXT/acq_default_copy_count.txt deleted file mode 100644 index 4ff5cc42d0..0000000000 --- a/docs/RELEASE_NOTES_NEXT/acq_default_copy_count.txt +++ /dev/null @@ -1,8 +0,0 @@ -New Feature: Default Number of Acquisistions Copies to Order -============================================================ -Acquisitions providers have a new "Default # Copies" field. When the value -is set, this number of copies will be automatically added to each lineitem -added to a purchase order for the provider. This takes place during PO -creation from a selection list or existing bib record and when a lineitem is -added to an existing purchase order. If a lineitem already has copies -attached, no default copies are added. diff --git a/docs/RELEASE_NOTES_NEXT/acq_lineitem_order_ident.txt b/docs/RELEASE_NOTES_NEXT/acq_lineitem_order_ident.txt deleted file mode 100644 index 9315a3b8b1..0000000000 --- a/docs/RELEASE_NOTES_NEXT/acq_lineitem_order_ident.txt +++ /dev/null @@ -1,22 +0,0 @@ -Acquisitions Lineitem Order Identifiers -======================================= - -Staff now have the ability to specify the identifier value to use for -lineitems when communicating order information to vendors. This is -particularly important when a lineitem has, for example, multiple ISBNs. -Determining which ISBN is to act as the "order identifier" allows staff -to provide the most accurate order information to vendors. - -Supported identifier types include ISBN, ISSN, and UPC. Order identifier -values are relayed to vendors via EDI and print PO. - -Upgrade Notes -============= - -Two new permissions are added for this feature: - - * ACQ_SET_LINEITEM_IDENTIFIER - ** Allows staff to apply order identifiers to lineitems - * ACQ_ADD_LINEITEM_IDENTIFIER - ** Implies that new identifiers shall be added to linked bib records, - when a linkage exists. diff --git a/docs/RELEASE_NOTES_NEXT/acq_marc_upload_defaults.txt b/docs/RELEASE_NOTES_NEXT/acq_marc_upload_defaults.txt deleted file mode 100644 index e0e709fd6a..0000000000 --- a/docs/RELEASE_NOTES_NEXT/acq_marc_upload_defaults.txt +++ /dev/null @@ -1,7 +0,0 @@ -Acquisitions MARC Upload Form Persistence -========================================= -Adds a two-layer persistence mechanism for the acquisitions MARC file upload -interface. A set of org unit settings now exist for managing default values -for the interface. Additionally, for each field where no org unit setting -value is configured, the last-used value will be persisted locally and re- -used with subsequent loads of the interface. diff --git a/docs/RELEASE_NOTES_NEXT/acq_po_detail_view.txt b/docs/RELEASE_NOTES_NEXT/acq_po_detail_view.txt deleted file mode 100644 index 001679483e..0000000000 --- a/docs/RELEASE_NOTES_NEXT/acq_po_detail_view.txt +++ /dev/null @@ -1,12 +0,0 @@ -Acquisitions Inline Item Detail View -==================================== - -Acquisitions selection lists and purchase order interfaces contain a new link -beside each lineitem which, when clicked, creates an inline grid of copies -linked to the lineitem. The grid contains the same information that displays -in the full copy edit grid (from clicking on the Copies(n) link). However, -the inline grid is read-only, so it displays much faster and does not require -the user to change visual contexts. - -Included along the top of the lineitem table is a new '✓ Expand' link which, -when clicked, expands or collapses the inline grid for all visible lineitems. diff --git a/docs/RELEASE_NOTES_NEXT/alternate_graphic_fields.txt b/docs/RELEASE_NOTES_NEXT/alternate_graphic_fields.txt deleted file mode 100644 index 82729cd584..0000000000 --- a/docs/RELEASE_NOTES_NEXT/alternate_graphic_fields.txt +++ /dev/null @@ -1,67 +0,0 @@ -Display alternate graphic (880) fields -====================================== - -By default, Evergreen displays alternate graphic fields, if any, for -contributors (1xx / 7xx), titles (245), edition statements (250), imprints -(260), notes (5xx), subjects (6xx), and series (4xx / 8xx) in search results and record details -per the Library of Congress MARC21 specifications: - -* http://www.loc.gov/marc/bibliographic/bd880.html -* http://www.loc.gov/marc/bibliographic/ecbdcntf.html -* http://www.loc.gov/marc/bibliographic/ecbdmulti.html (Model A) - -Default display ---------------- -In general, alternate graphic fields display below the corresponding -primary field. One exception is the attribution summary on the record details -page, in which the alternate graphic field contents display between the -primary field content and the attribution statement. To support CSS -customizations, HTML elements for the graphic fields have the class attribute -value `graphic880`. - -Implementation details ----------------------- -The template file `parts/misc_util.tt2` defines two macros for retrieving -linked 880 fields: - -* `get_graphic_880s`: given a _target_field_ scalar value representing a MARC - field tag, populate the _graphic_880s_ list with hashes containing the - target field tag and any graphic fields linked to that particular tag, with - the values for each being a simple concatenation of all subfields that are - not control subfields (per - http://www.loc.gov/marc/bibliographic/ecbdcntf.html). The structure of the - `graphic_880s` list is as follows: -+ ------------------------------------------------------------------------- -[ - { - "primary": {"occur": 01, "value": "foo foo"}, - "graphic": [ - { - "occur": 01, - "value": "bar bar", - "orient": "rtl", - "script": "CJK" - } - ] - } -] ------------------------------------------------------------------------- -* `get_linked_880s` macro iterates over the content of the `linked_fields` - list, in which each element of the list to be a scalar representing the $6 - control subfield link info. The macro populates the `graphics` list with a - set of graphic field hashes with the following structure: -+ ------------------------------------------------------------------------- -[ - { - "occur": 01, - "value": "bar bar", - "orient": "rtl", - "script": "CJK" - } -] ------------------------------------------------------------------------- - -`misc_util.tt2` preserves legacy attribute lists to enable previous TPAC -customizations to continue to function normally. diff --git a/docs/RELEASE_NOTES_NEXT/calculated-proximity-adjustments.txt b/docs/RELEASE_NOTES_NEXT/calculated-proximity-adjustments.txt deleted file mode 100644 index 61a81a709b..0000000000 --- a/docs/RELEASE_NOTES_NEXT/calculated-proximity-adjustments.txt +++ /dev/null @@ -1,10 +0,0 @@ -Calculated Proximity Adjustments -================================ - -Allows customization to the way that Evergreen measures the distance between -org units for the purposes of 1) determining what copy at what org unit is best -suited for targeting a title-level hold, and 2) determining what hold is best -suited for fulfillment by a copy-in-hand at capture (checkin) time. The -customization is based on a table 'actor.org_unit_proximity_adjustment', with -certain matching criteria that the system compares to properties of the holds -and copies in question. diff --git a/docs/RELEASE_NOTES_NEXT/circulation_patron_expiry_warning.txt b/docs/RELEASE_NOTES_NEXT/circulation_patron_expiry_warning.txt deleted file mode 100644 index eebe3eb869..0000000000 --- a/docs/RELEASE_NOTES_NEXT/circulation_patron_expiry_warning.txt +++ /dev/null @@ -1,9 +0,0 @@ -New feature: "Warn patrons when their account is about to expire" -================================================================= -To give staff the ability to warn patrons when their account is about to -expire, the staff client can display an alert message on the patron information -window. A new library setting, `Warn patrons when their account is about to -expire` in the *Circulation* section of the *Library Settings Editor*, -determines how many days in advance of a patron's account expiry date the alert -should be displayed. By default, warnings about upcoming patron account expiry -dates are not displayed. diff --git a/docs/RELEASE_NOTES_NEXT/clickable_patron_indicators.txt b/docs/RELEASE_NOTES_NEXT/clickable_patron_indicators.txt deleted file mode 100644 index 4d0baeec0b..0000000000 --- a/docs/RELEASE_NOTES_NEXT/clickable_patron_indicators.txt +++ /dev/null @@ -1,6 +0,0 @@ -New feature: Clickable Patron Indicators -======================================== -When retrieving a patron record, staff can now click on the indicators listed -beneath the patron's name and launch the related tabs. - -For example, clicking on (See Notes) will open the associated patron's notes. diff --git a/docs/RELEASE_NOTES_NEXT/create_release_notes.sh b/docs/RELEASE_NOTES_NEXT/create_release_notes.sh new file mode 100755 index 0000000000..bb546e8e47 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/create_release_notes.sh @@ -0,0 +1,60 @@ +#!/bin/bash + +ver= +while getopts r: opt; do + case $opt in + r) + ver=$OPTARG + ;; + esac +done + +if [ -z "$ver" ]; then echo "I need a version: -r"; exit; fi + +outfile="../RELEASE_NOTES_$ver.txt" + +title="Evergreen $ver Release Notes" + +echo $title > $outfile; +for j in `seq 1 ${#title}`; do echo -n '='; done >> $outfile + +echo >> $outfile +echo ':toc:' >> $outfile +echo ':numbered:' >> $outfile +echo >> $outfile +echo Upgrade notes >> $outfile +echo ------------- >> $outfile +echo >> $outfile + + +for i in `ls -l|grep ^d|awk '{print $9}'`; do + files=$(ls $i/*txt 2>/dev/null) + if [ "_$files" != "_" ]; then + echo >> $outfile + echo >> $outfile + echo $i >> $outfile + for j in `seq 1 ${#i}`; do echo -n '~'; done >> $outfile + echo >> $outfile + echo >> $outfile + + for j in $files; do + echo >> $outfile + echo >> $outfile + cat $j >> $outfile + echo >> $outfile + echo >> $outfile + done + fi +done + +files=$(ls *txt 2>/dev/null) +if [ "_$files" != "_" ]; then + echo >> $outfile + echo Miscellaneous >> $outfile + echo ------------- >> $outfile + echo >> $outfile + for j in $files; do + cat $j >> $outfile + done +fi + diff --git a/docs/RELEASE_NOTES_NEXT/custom-best-hold-selection.txt b/docs/RELEASE_NOTES_NEXT/custom-best-hold-selection.txt deleted file mode 100644 index 4fb440a9f8..0000000000 --- a/docs/RELEASE_NOTES_NEXT/custom-best-hold-selection.txt +++ /dev/null @@ -1,16 +0,0 @@ -Custom best-hold selection sort order -===================================== - -The ranking algorithm that chooses the best hold to target a copy in -hand at a capture time used to be fairly simple. It had two modes, FIFO -and not-FIFO, and that was it. - -This change allows full configuration of that algorithm. In other -words, when the system captures a copy and sets out to evaluate what -hold, if any, that copy might best fulfull, site staff of sufficient -permission level are now empowered to choose exactly which comparisons -the systems makes in what order. This gives said staff much greater -flexibililty than they have today over holds policy. - -For more information, see the included tech spec documents. - diff --git a/docs/RELEASE_NOTES_NEXT/hold_patron_name.txt b/docs/RELEASE_NOTES_NEXT/hold_patron_name.txt deleted file mode 100644 index 30891c7b52..0000000000 --- a/docs/RELEASE_NOTES_NEXT/hold_patron_name.txt +++ /dev/null @@ -1,7 +0,0 @@ -Show Hold Patron Name in TPac -============================= - -When looking up patron information for hold placement via the staff client in -TPac the hold patron name is now shown next to the entered barcode. In the event -that the barcode is not found a notice is displayed and the submit button is -disabled until a valid barcode is entered or the staff member is switched to. diff --git a/docs/RELEASE_NOTES_NEXT/marc-import-tag-stripping.txt b/docs/RELEASE_NOTES_NEXT/marc-import-tag-stripping.txt deleted file mode 100644 index 7470dc09c5..0000000000 --- a/docs/RELEASE_NOTES_NEXT/marc-import-tag-stripping.txt +++ /dev/null @@ -1,28 +0,0 @@ -MARC Import Tag Stripping -========================= - -Administrators can configure MARC tags which are removed from MARC records -imported via Z39.50 and the Vandelay MARC Import/Export UI (ACQ and non-ACQ). -Tags are organized into groups. Groups can be marked as optional or required. -For each tag, every instance of the tag (including all subfields) are removed -from the record. - -MARC fields which are contained within required ('always_apply') tag groups -are always removed from inbound records. No action is needed. Tag groups -which are optional will appear in MARC import interfaces (see below) allowing -staff to select which groups of tags to strip from incoming records at import -time. - -Interfaces Affected -------------------- - - * Admin UI - ** Admin => Server Administration => MARC Import Remove Fields - * Z39.50 Import - ** Cataloging => Import Record from Z39.50 - ** Optional groups appear with the other import options - * Vandelay - ** Cataloging => MARC Import/ExportVandelay - ** Acquisistions => Load Order Records - ** Optional groups appear with the other import options - diff --git a/docs/RELEASE_NOTES_NEXT/marc21-feeds.txt b/docs/RELEASE_NOTES_NEXT/marc21-feeds.txt deleted file mode 100644 index 0b861a90e2..0000000000 --- a/docs/RELEASE_NOTES_NEXT/marc21-feeds.txt +++ /dev/null @@ -1,8 +0,0 @@ -MARC21 Feeds from OpenSearch -============================ - -In addition to the already supported formats, you can now get raw MARC21 from -OpenSearch feeds, à la: - - http:///opac/extras/opensearch/1.1/-/marc21?searchTerms=piano - diff --git a/docs/RELEASE_NOTES_NEXT/notify_csv.txt b/docs/RELEASE_NOTES_NEXT/notify_csv.txt deleted file mode 100644 index 0529726925..0000000000 --- a/docs/RELEASE_NOTES_NEXT/notify_csv.txt +++ /dev/null @@ -1,78 +0,0 @@ -New Feature: Generic CVS Notification Generator/Receiver -======================================================== - -New Action/Trigger template and sample event definitions for creating a CSV -export file for various patron actions, primarily for the purpose of creating -patron notices via external notification mechanisms. - -The reference implementation for this development is the TalkingTech iTiva -product, which consumes CSV files for generating phone/text notifications and -produces CSV results files for informing the ILS of notification statuses. -The template and send/receive scripts, however, should be generic enough to -create CSV for any type of 3rd-party notification product. - -Action/Trigger Event Definition Configuration ---------------------------------------------- - - * Supported hook core types include *circ*, *ahr*, *ausp*, and *au* - * Reactor is *ProcessTemplate* - -Event Environment Requirements -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - - * Patron object with card - * copy object - ** circ.target_copy - ** hold.current_copy - * Org unit - ** circ.circ_lib - ** ahr.pickup_lib - ** ausp.org_unit - ** patron.home_ou - -Not all fields are relevent to all notice types. - -Required Event Parameters -~~~~~~~~~~~~~~~~~~~~~~~~~ - - * notify_media (e.g. phone) - * notify_type (e.g. overdue) - * notify_level (e.g. "1" -- first overdue) - -The set of options for each event parameter is dependent on the 3rd-party -processing the CSV file. - -iTiva Event Parameter Options -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - - * notify_media - ** V (voice) - ** T (text) - * notify_level - ** 1 (1st notice) - ** 2 (2nd notice) - ** 3 (3rd notice) - * notify_type - ** FINES - ** OVERDUE - ** PREOVERDUE - ** PRERESERVE - ** RECALL - ** RESERVE - ** RESERVECANCEL - ** RESERVEEXPIRE - ** SUSPEND - -Push/Fetch Scripts ------------------- - - * action_trigger_aggregator.pl collects event output from requested event - definitions and stitches them together into a single file, which is sent - via (s)FTP to the 3rd party. - * Why don't we use the SendFile reactor directly? - ** The final file is meant to be a collection of event-def outputs, not - the output from a single event def - ** The final file may be too large to reasonably store directly in a - single action/trigger event_output row. - * csv_notify_fetcher.pl retrieves responses from the 3rd party and applies - the statuses to the async_output of each notified event. diff --git a/docs/RELEASE_NOTES_NEXT/queryparser_changes.txt b/docs/RELEASE_NOTES_NEXT/queryparser_changes.txt deleted file mode 100644 index d25609658b..0000000000 --- a/docs/RELEASE_NOTES_NEXT/queryparser_changes.txt +++ /dev/null @@ -1,25 +0,0 @@ -Search Changes -============== -A number of changes have been made to search to allow more control and improve -performance. These changes and their associated configurations are global to -the entire system and can not be configured on a per-library basis. - -Amongst other things the new search code fixes: - -* Inability to use statuses and locations as part of a larger query -* Invalid queries being generated from advanced searches -* Some timeouts from backend code taking too long to preform a search -* Some filters being one-use only -* Negations not working properly where multiple indexes are involved - -Improvements include: - -* Exact matches on input should be more likely to float to the top of results -* Non-English stemming can be used, alongside or instead of English stemming -* Entered search terms can be found across multiple indexes - -Default configuration is geared towards English but is easily changed. In a -production environment changes will likely require re-indexing, however. - -The upgrade script could be pre-tweaked to install desired configuration before -it builds and/or re-builds many of the indexes. diff --git a/docs/RELEASE_NOTES_NEXT/search-deleted.txt b/docs/RELEASE_NOTES_NEXT/search-deleted.txt deleted file mode 100644 index 5e1d8a0735..0000000000 --- a/docs/RELEASE_NOTES_NEXT/search-deleted.txt +++ /dev/null @@ -1,11 +0,0 @@ -Searching for deleted records -============================= - -Evergreen now supports searching for deleted records via the '#deleted' -QP modifier. - -In order to support this, sites must enable the -'ingest.metarecord_mapping.preserve_on_delete' internal flag. It is off by -default since the ability to search for deleted records requires keeping -metarecord mappings around when bibs are deleted, which may not be desirable -for the typical site. diff --git a/docs/RELEASE_NOTES_NEXT/search-record-date-filters.txt b/docs/RELEASE_NOTES_NEXT/search-record-date-filters.txt deleted file mode 100644 index 84dea19daa..0000000000 --- a/docs/RELEASE_NOTES_NEXT/search-record-date-filters.txt +++ /dev/null @@ -1,11 +0,0 @@ -Two new QP filters: create_date and edit_date -============================================= - -These filter on the fields of the same name in biblio.record_entry. - -e.g. - * create_date(,2013-02-01) => records created before 2013-02-01 - * create_date(2013-02-01) => records created since 2013-02-01 - * create_date(2013-02-01,2013-02-28) => records created in Feb 2013 - * create_date(yesterday) => records since created yesterday - diff --git a/docs/RELEASE_NOTES_NEXT/serial_control_embedded_alt_interfaces.txt b/docs/RELEASE_NOTES_NEXT/serial_control_embedded_alt_interfaces.txt deleted file mode 100644 index f0986fed21..0000000000 --- a/docs/RELEASE_NOTES_NEXT/serial_control_embedded_alt_interfaces.txt +++ /dev/null @@ -1,13 +0,0 @@ -Serial Control: Embed Alternate Interfaces -========================================== -As another step toward a unified interface, the serial control subscription -editor now consists of an embedded version of the alternate control. This -reduces duplication of both code and documentation, and smoothes the eventual -transition to a single interface. - -In order to not lose any essential features, the following additions were made -to the new combination editor: - -* note editors on subscriptions and distributions -* labeled dropdown for distribution summary options ("Add to record entry", "Use record entry only", etc.) -* legacy record entry linkage setup (Allows one to tie a distribution's information to a particular serial record entry (i.e. a MFHD record)) diff --git a/docs/RELEASE_NOTES_NEXT/serial_control_special_statuses.txt b/docs/RELEASE_NOTES_NEXT/serial_control_special_statuses.txt deleted file mode 100644 index 5b4e3c3463..0000000000 --- a/docs/RELEASE_NOTES_NEXT/serial_control_special_statuses.txt +++ /dev/null @@ -1,7 +0,0 @@ -Serial Control: Set Special Statuses -==================================== -The Serial Control interface prevents direct editing of serial item statuses -for data integrity reasons. As an alternative to direct control, the interface -now offers new menu options for setting items to 'claimed', 'not held', and -'not published'. Note that these statuses are still currently useful for -reporting and display purposes only. diff --git a/docs/RELEASE_NOTES_NEXT/show_holds_on_bib.txt b/docs/RELEASE_NOTES_NEXT/show_holds_on_bib.txt deleted file mode 100644 index 27b69bd2f6..0000000000 --- a/docs/RELEASE_NOTES_NEXT/show_holds_on_bib.txt +++ /dev/null @@ -1,7 +0,0 @@ -Show Holds On Bib Menu Option -============================= - -Add direct "Show holds on bibs" menu option from item checkin, item status, -and patron hold interfaces. This gives staff a quicker way of viewing who -else has holds on an item instead of having to click an option to view the -bib record, then clicking into the menus to view holds. diff --git a/docs/RELEASE_NOTES_NEXT/toolbar_perms.txt b/docs/RELEASE_NOTES_NEXT/toolbar_perms.txt deleted file mode 100644 index 111ab52a36..0000000000 --- a/docs/RELEASE_NOTES_NEXT/toolbar_perms.txt +++ /dev/null @@ -1,12 +0,0 @@ -Upgrade Notes -------------- -Custom toolbar permissions -~~~~~~~~~~~~~~~~~~~~~~~~~~ -With the addition of more granular permissions for configuring a custom -toolbars, the ADMIN_TOOLBAR permission alone will not allow users to -configure a custom toolbar. This permission must now be used in conjunction -with one or more of the following permissions: - -* ADMIN_TOOLBAR_FOR_ORG -* ADMIN_TOOLBAR_FOR_USER -* ADMIN_TOOLBAR_FOR_WORKSTATION diff --git a/docs/RELEASE_NOTES_NEXT/tpac-ou-hiding.txt b/docs/RELEASE_NOTES_NEXT/tpac-ou-hiding.txt deleted file mode 100644 index adebd77129..0000000000 --- a/docs/RELEASE_NOTES_NEXT/tpac-ou-hiding.txt +++ /dev/null @@ -1,20 +0,0 @@ -TPAC Org Unit Hiding -==================== - -Adds support for the opac.org_unit_hiding.depth org unit setting to -TPAC, which makes out-of-scope org units disappear (except when -explicitly requested). - -Org unit hiding is based on the physical_loc (Physical Location) param / -cookie, which is the closest analog to 'ol' (original location), from -which it was based in the JSPAC. - -UI Changes ----------- - - * All search org unit selectors - * Holds pickup lib selector - * Copy summary in search results page - * Copy list in search results page - * Copy summary in record detail page (which controls the copy grid). - * Hold summary in record detail page diff --git a/docs/RELEASE_NOTES_NEXT/tpac_bookbag_callnumbers.txt b/docs/RELEASE_NOTES_NEXT/tpac_bookbag_callnumbers.txt deleted file mode 100644 index a6a53c5584..0000000000 --- a/docs/RELEASE_NOTES_NEXT/tpac_bookbag_callnumbers.txt +++ /dev/null @@ -1,15 +0,0 @@ -New Feature: Show local call number in TPAC My Lists display -============================================================ - -If an opac-visible call number exists that is owned by an org unit -relevant to the patron, show the most relevant call number label -and owning branch name in the My Lists display for each record in -the list. Call number is displayed in both saved and temporary lists. - -A call number is considered relevant if its owner is one of: - -physical location library -preferred library (plib, home, etc.) -search library - -If no relevant call number is found, no call number is diplayed. diff --git a/docs/RELEASE_NOTES_NEXT/tpac_google_books_preview.txt b/docs/RELEASE_NOTES_NEXT/tpac_google_books_preview.txt deleted file mode 100644 index c56582572c..0000000000 --- a/docs/RELEASE_NOTES_NEXT/tpac_google_books_preview.txt +++ /dev/null @@ -1,12 +0,0 @@ -TPAC: Google Books preview -========================== - -Setting `ctx.google_books_preview` to `1` in the TPAC `config.tt2` -configuration file will cause the TPAC to check to see, as part of the record -details view, if Google Books has an online preview available. If it does, -then a preview button will be displayed in the book cover image location. -If the user then clicks the preview button, the preview will load below the -title of the book in the record details page. - -By default, this functionality is disabled to protect the privacy of users -who might not want to share their browsing behaviour with Google. diff --git a/docs/RELEASE_NOTES_NEXT/vandelay_default_match_set.txt b/docs/RELEASE_NOTES_NEXT/vandelay_default_match_set.txt deleted file mode 100644 index 836b2e5f9d..0000000000 --- a/docs/RELEASE_NOTES_NEXT/vandelay_default_match_set.txt +++ /dev/null @@ -1,11 +0,0 @@ -Vandelay Default Match Set -========================== -A new org unit setting to specify a default Record Match Set when -importing MARC records through the MARC Batch Import/Export interface. It does -not affect the default match set selected in acquisitions. If this -is set, it will not be possible to leave the Record Match Set field blank; -it may be necessary to define a default match set that replicates the current -default behavior. - -A new "Vandelay" org unit settings group is also created. - diff --git a/docs/RELEASE_NOTES_NEXT/z39_source_credentials.txt b/docs/RELEASE_NOTES_NEXT/z39_source_credentials.txt deleted file mode 100644 index eb74bcc6f6..0000000000 --- a/docs/RELEASE_NOTES_NEXT/z39_source_credentials.txt +++ /dev/null @@ -1,13 +0,0 @@ -Storing Z39.50 Server Credentials -================================= - -In the Z39.50 configuration interface, staff now have the option to apply -z39.50 login credentials to each Z39.50 server at different levels of the -org unit hierarchy (similar to org unit settings). When credentials are set -for a Z39 server, searches against the z39 server will used the stored -credentials, unless other credentials are provided by the caller, in which -case the caller credentials are used. - -For security purposes, passwords may not be retrieved or reported on by staff. -Staff can only apply new values for credentials or clear existing ones. -