From 91b64e636c461456a4cbd2073b57064504d27532 Mon Sep 17 00:00:00 2001 From: rsoulliere Date: Mon, 23 Jan 2012 12:14:56 -0500 Subject: [PATCH] Structure root.txt as book. Add release notes from 2.2 code repo. --- release_notes.txt | 80 ++++++++++++++++++++++++++++++++++- root.txt | 123 ++++++++++++++++++++++++++++++++++-------------------- 2 files changed, 156 insertions(+), 47 deletions(-) diff --git a/release_notes.txt b/release_notes.txt index f640439a3d..c80b0b769a 100644 --- a/release_notes.txt +++ b/release_notes.txt @@ -1,2 +1,78 @@ -Release Notes -~~~~~~~~~~~~~ +Release notes +============= + +Upgrade notes +------------- + +Located URI search scope +~~~~~~~~~~~~~~~~~~~~~~~ +Recognizing that electronic resources are often licensed for an entire library +system rather than just a single library, the search scope for located URIs has +changed to match from the highest point in the hierarchy down, rather than from +the bottom up. In previous releases of Evergreen, if you had a MARC record with +a URI located at 'BR1', a search for that record at the 'SYS1' scope would +include the record in its results. The current release of Evergreen would not +include the record in its results; the scope needs to be set at the level of +'BR1' in the hierarchy or below. + +Therefore, you may want to run a SQL statement like the following, edited to +match the short names of your branches and systems, to change the located +URIs so that searches at the system level continue to return results for +located URIs: + +------------------------------------------------------------------------------ +UPDATE biblio.record_entry + SET marc = replace( + replace( + marc, + 'BR1', + 'SYS1' + ), + 'BR3', + 'SYS2' + ) WHERE marc LIKE 'BR1' + OR marc LIKE 'BR3' +; +------------------------------------------------------------------------------ + +New features +------------ + +Cataloging +~~~~~~~~~ + +Prevent bibliographic records from having attached copies +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +To enable libraries to designate specific sets of records as only for use +as electronic resources, it is possible to configure a bibliographic source +such that physical copies or MFHD records may not be attached to records +from that source. The `config.bib_source` table now includes a new Boolean +column, `can_have_copies`, that controls this behavior. If `can_have_copies` +for a given bibliographic source is `TRUE`, then the staff client will prevent +a cataloger from adding volumes or MFHD records to records belonging to that +source. + +Switch copy location name and library short name in copy editor +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +By default, the copy editor shows the library shortname ('BR1' or 'CONS') +followed by the copy location name ('Stacks', 'Reference'). A new workstation +setting, under *Admin -> Workstation Administration -> Copy Editor: Copy +Location Name First*, enables staff to change the display so that the copy +location name is displayed first, followed by the library shortname. This +may be particularly useful for libraries that have defined one set of copy +locations at the consortial level and want to enable quick keyboard navigation +to copy locations by typing just the first letters of the copy location. + +Reports +~~~~~~ + +New views for reporting sources +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +To support the creation of collection development reports, the following +reporting sources have been added: + + * 'Last Circulation or Creation Date' is a source that offers the copy ID, + the last circulation date or creation date, and the last circulation date + * 'Hold/Copy Ratio per Bib and Pickup Library' is a source that calculates + the number of holds per copy per bibliographic record, with granularity + by pickup library. diff --git a/root.txt b/root.txt index e26fa7de9c..afbd4f7b1a 100644 --- a/root.txt +++ b/root.txt @@ -1,8 +1,9 @@ Evergreen Documentation ======================= + Introduction ------------- +============ This guide was produced by the Evergreen Documentation Interest Group (DIG), consisting of numerous volunteers from many different organizations. The DIG has drawn together, edited, and supplemented pre-existing documentation contributed by libraries and consortia running Evergreen that were kind enough to release their documentation into the creative commons. For a full list of authors and contributing organizations, see Appendix B, About this Documentation. Just like the software it describes, this guide is a work in progress, continually revised to meet the needs of its users, so if you find errors or omissions, please let us know, by contacting the DIG facilitators at docs@evergreen-ils.org. @@ -11,7 +12,8 @@ This guide to Evergreen is intended to meet the needs of front-line library staf Copies of this guide can be accessed in PDF and HTML formats from http://docs.evergreen-ils.org/. About Evergreen -~~~~~~~~~~~~~~~ +--------------- + Evergreen is an open source library automation software designed to meet the needs of the very smallest to the very largest libraries and consortia. Through its staff interface, it facilitates the management, cataloging, and circulation of library materials, and through its online public access interface it helps patrons find those materials. The Evergreen software is freely licensed under the GNU General Public License, meaning that it is free to download, use, view, modify, and share. It has an active development and user community, as well as several companies offering migration, support, hosting, and development services. @@ -28,85 +30,116 @@ Evergreen, which first launched in 2006 now powers over 544 libraries of every t include::release_notes.txt[] - - Software Installation ---------------------- +===================== -Introduction -~~~~~~~~~~~~ +[partintro] +-- +This part will guide you through the installation steps installation or upgrading your Evergreen system. It is intended for system administrators. +-- + +// include::system_requirements.txt[] +// include::server_installation.txt[] +// include::server_upgrade.txt[] +// include::system_troubleshooting.txt[] +// include::staff_client_installation.txt[] +// include::org_unit_structure_initialization.txt[] +// include::loading_data.txt[] System Configuration and Customization --------------------------------------- +====================================== -Introduction -~~~~~~~~~~~~ +[partintro] +-- +The Evergreen system allows a free range of customizations to every aspect of the system. Use this part of the documentation to become familiar with the tools for configuring the system as well as customizing the OPAC and staff client. +-- + +// include::global_system_configuration.txt[] +// include::opac_customization.txt[] +//include::staff_client_customization.txt[] +// include::backing_up.txt[] + System Administration From the Staff Client -------------------------------------------- +=========================================== -Introduction -~~~~~~~~~~~~ +[partintro] +-- +This part deals with the options in the Server Administration menu found in the staff client. +-- +// Follow structure from staff client system admin menu. Local Administration --------------------- +==================== -Introduction -~~~~~~~~~~~~ +[partintro] +-- +This part covers the options in the Local Administration menu found in the staff client. +-- +// Follow structure from staff client local admin menu. -Acqiostions ------------ -Introduction -~~~~~~~~~~~~ +Acuisitions +=========== +[partintro] +-- +This part is intended for staff who are involved in managing and processing acquisitions. +-- Cataloging ----------- - -Intrododuction -~~~~~~~~~~~~~~ +========== -\Serials -------- +[partintro] +-- +Cataloguers should use this part for understanding the cataloguing procedures used in Evergreen. +-- -Introduction -~~~~~~~~~~~~ +Serials +======= +[partintro] +-- +This part is intended for staff involved in Serials management and processing. +-- Circulation ------------ - -Introduction -~~~~~~~~~~~~ +=========== +[partintro] +-- +Use this section for understanding the circulation procedures in the Evergreen system. +-- Reports -------- - -Introduction -~~~~~~~~~~~~ +======= +[partintro] +-- +Learn how to create and use reports in Evergreen. +-- Using the Public Access Catalog -------------------------------- - -Introduction -~~~~~~~~~~~~ +=============================== +[partintro] +-- +Use this part for information about searching the Evergreen public access catalog. +-- Developer Resources -------------------- +=================== -Introduction -~~~~~~~~~~~~ +[partintro] +-- +Developers can use this part to learn more about the programming languages, communication protocols and standards used in Evergreen. +-- +[appendix] -Appendices ----------- -- 2.11.0