[open-ils-commits] [GIT] Evergreen ILS branch master updated. 293df1f82290c99346028e03f2984e21811eee3a
Evergreen Git
git at git.evergreen-ils.org
Fri Jan 20 14:59:21 EST 2012
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Evergreen ILS".
The branch, master has been updated
via 293df1f82290c99346028e03f2984e21811eee3a (commit)
via 1fc33daaa509e61313bd309ea5334cb562b5f38d (commit)
via 3a32e75238fc625c6e91b124bfdcc957f3b2b55b (commit)
via a0e384a033536b23112e635b7cd9f53d4b912b5b (commit)
via 504263a31a1861db594ebd65d39b657d6f386f40 (commit)
via b541a02d86ea81e7623ce40cc756082eb906fc75 (commit)
via 1698f622e91652697b25ce839db131fd7485d2ea (commit)
from c5716450f3fd01f13ccd68006fdd577df4e7d709 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 293df1f82290c99346028e03f2984e21811eee3a
Author: Bill Erickson <berick at esilibrary.com>
Date: Fri Jan 20 14:58:05 2012 -0500
Remove RELEASE_NOTES reference from README
...pending further discussion
Signed-off-by: Bill Erickson <berick at esilibrary.com>
diff --git a/README b/README
index 3339df7..e476035 100644
--- a/README
+++ b/README
@@ -1,9 +1,6 @@
README for Evergreen master
===========================
-See `docs/RELEASE_NOTES_2_2.txt` for new features, changes to behavior, and
-bug fixes for the 2.2 release series.
-
Preamble: referenced user accounts
----------------------------------
commit 1fc33daaa509e61313bd309ea5334cb562b5f38d
Author: Dan Scott <dscott at laurentian.ca>
Date: Fri Dec 23 12:57:37 2011 -0500
Release Notes: Add CC-BY-SA 3.0 license to footer
Signed-off-by: Dan Scott <dscott at laurentian.ca>
Signed-off-by: Bill Erickson <berick at esilibrary.com>
diff --git a/docs/RELEASE_NOTES_2_2.txt b/docs/RELEASE_NOTES_2_2.txt
index fcb33ad..3ad4ace 100644
--- a/docs/RELEASE_NOTES_2_2.txt
+++ b/docs/RELEASE_NOTES_2_2.txt
@@ -76,3 +76,10 @@ reporting sources have been added:
* '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.
+
+License
+-------
+This work is licensed under the Creative Commons Attribution-ShareAlike 3.0
+Unported License. To view a copy of this license, visit
+http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative
+Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA.
commit 3a32e75238fc625c6e91b124bfdcc957f3b2b55b
Author: Dan Scott <dscott at laurentian.ca>
Date: Fri Dec 23 12:55:34 2011 -0500
Release notes: document copy location display option
Signed-off-by: Dan Scott <dscott at laurentian.ca>
Signed-off-by: Bill Erickson <berick at esilibrary.com>
diff --git a/docs/RELEASE_NOTES_2_2.txt b/docs/RELEASE_NOTES_2_2.txt
index 4045dc8..fcb33ad 100644
--- a/docs/RELEASE_NOTES_2_2.txt
+++ b/docs/RELEASE_NOTES_2_2.txt
@@ -52,6 +52,17 @@ 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
~~~~~~~
commit a0e384a033536b23112e635b7cd9f53d4b912b5b
Author: Dan Scott <dscott at laurentian.ca>
Date: Wed Dec 21 11:56:55 2011 -0500
Release notes: document new reporting views
Introduce 'Last Circulation or Creation Date' and 'Hold/Copy Ratio per Bib
and Pickup Library' reporting sources.
Signed-off-by: Dan Scott <dscott at laurentian.ca>
Signed-off-by: Bill Erickson <berick at esilibrary.com>
diff --git a/docs/RELEASE_NOTES_2_2.txt b/docs/RELEASE_NOTES_2_2.txt
index 61d0a7a..4045dc8 100644
--- a/docs/RELEASE_NOTES_2_2.txt
+++ b/docs/RELEASE_NOTES_2_2.txt
@@ -46,8 +46,22 @@ 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
+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.
+
+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.
commit 504263a31a1861db594ebd65d39b657d6f386f40
Author: Dan Scott <dscott at laurentian.ca>
Date: Tue Dec 20 11:54:30 2011 -0500
Move RELEASE_NOTES into the docs subdirectory
We will begin maintaining release notes inside the source directory,
with one RELEASE_NOTES.txt file per major release series (2.2, 2.3,
etc). The release notes will primarily consist of an overview of new
features and important behaviour changes in that particular release
series, as well as a cumulative list of bugs that have been fixed in the
point releases for that series.
Also, mention the existence of the release notes in the top-level
README.
Signed-off-by: Dan Scott <dscott at laurentian.ca>
Signed-off-by: Bill Erickson <berick at esilibrary.com>
diff --git a/README b/README
index e476035..3339df7 100644
--- a/README
+++ b/README
@@ -1,6 +1,9 @@
README for Evergreen master
===========================
+See `docs/RELEASE_NOTES_2_2.txt` for new features, changes to behavior, and
+bug fixes for the 2.2 release series.
+
Preamble: referenced user accounts
----------------------------------
diff --git a/RELEASE_NOTES b/docs/RELEASE_NOTES_2_2.txt
similarity index 100%
rename from RELEASE_NOTES
rename to docs/RELEASE_NOTES_2_2.txt
commit b541a02d86ea81e7623ce40cc756082eb906fc75
Author: Dan Scott <dscott at laurentian.ca>
Date: Mon Dec 5 13:56:36 2011 -0500
Release notes: "cbs prevents records from having copies"
The new "can_have_copies" column on config.bib_source prevents
associated records from having copies or MFHD records attached via the
staff client.
Signed-off-by: Dan Scott <dscott at laurentian.ca>
Signed-off-by: Bill Erickson <berick at esilibrary.com>
diff --git a/RELEASE_NOTES b/RELEASE_NOTES
index 2010c99..61d0a7a 100644
--- a/RELEASE_NOTES
+++ b/RELEASE_NOTES
@@ -34,3 +34,20 @@ UPDATE biblio.record_entry
OR marc LIKE '<subfield code="9">BR3</subfield>'
;
------------------------------------------------------------------------------
+
+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.
commit 1698f622e91652697b25ce839db131fd7485d2ea
Author: Dan Scott <dscott at laurentian.ca>
Date: Tue Nov 29 15:11:55 2011 -0500
Note located URI changes in Release Notes
Located URIs now define what org unit and below in the hierarchy will be
matched for a given search scope, rather than the copy-like behaviour
from before; for example, a located URI at BR1 will no longer be found
in a SYS1 search scope; rather, a located URI at SYS1 will be found with
either a SYS1 or a BR1 search scope.
Put some info and rough suggested fix into the release notes.
Signed-off-by: Dan Scott <dscott at laurentian.ca>
Signed-off-by: Bill Erickson <berick at esilibrary.com>
diff --git a/RELEASE_NOTES b/RELEASE_NOTES
new file mode 100644
index 0000000..2010c99
--- /dev/null
+++ b/RELEASE_NOTES
@@ -0,0 +1,36 @@
+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,
+ '<subfield code="9">BR1</subfield>',
+ '<subfield code="9">SYS1</subfield>'
+ ),
+ '<subfield code="9">BR3</subfield>',
+ '<subfield code="9">SYS2</subfield>'
+ ) WHERE marc LIKE '<subfield code="9">BR1</subfield>'
+ OR marc LIKE '<subfield code="9">BR3</subfield>'
+;
+------------------------------------------------------------------------------
-----------------------------------------------------------------------
Summary of changes:
docs/RELEASE_NOTES_2_2.txt | 85 ++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 85 insertions(+), 0 deletions(-)
create mode 100644 docs/RELEASE_NOTES_2_2.txt
hooks/post-receive
--
Evergreen ILS
More information about the open-ils-commits
mailing list