[open-ils-commits] [GIT] Evergreen ILS branch rel_2_12 updated. 51d2f4d9b20345f8310b8a0c09d54f9e829e385d
Evergreen Git
git at git.evergreen-ils.org
Sun Mar 26 22:42:41 EDT 2017
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, rel_2_12 has been updated
via 51d2f4d9b20345f8310b8a0c09d54f9e829e385d (commit)
via 9eb86ae0140f71b41263fde8eb6bc020b50aa670 (commit)
via 6879ae9f0556471e089922a0aad60cfcd7b16782 (commit)
from 9c009a7318145290bed84cce1158e50164fe7017 (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 51d2f4d9b20345f8310b8a0c09d54f9e829e385d
Author: Dan Scott <dscott at laurentian.ca>
Date: Sun Mar 26 22:40:24 2017 -0400
Docs: Publish the 2.12 release notes
We've released 2.12, let's integrate the corresponding release
notes into the doc build.
Signed-off-by: Dan Scott <dscott at laurentian.ca>
diff --git a/docs/installation/server_upgrade.txt b/docs/installation/server_upgrade.txt
index 2fb063c..3676b97 100644
--- a/docs/installation/server_upgrade.txt
+++ b/docs/installation/server_upgrade.txt
@@ -350,6 +350,6 @@ from the Evergreen community.
Review Release Notes
~~~~~~~~~~~~~~~~~~~~
-Review the <<_evergreen_2_10_release_notes,2.10 release notes>> for other tasks
+Review the <<_evergreen_2_12_0_release_notes,2.12 release notes>> for other tasks
that need to be done after upgrading. If you have upgraded over several
major versions, you will need to review the release notes for each version also.
diff --git a/docs/root.txt b/docs/root.txt
index 8ae307c..f516acd 100644
--- a/docs/root.txt
+++ b/docs/root.txt
@@ -58,7 +58,7 @@ type – public, academic, special, school, and even tribal and home libraries
in over a dozen countries worldwide.
-include::RELEASE_NOTES_2_11.adoc[]
+include::RELEASE_NOTES_2_12.adoc[]
Software Installation
commit 9eb86ae0140f71b41263fde8eb6bc020b50aa670
Author: Robert Soulliere <rsoulliere at yahoo.com>
Date: Wed Sep 28 10:35:53 2016 -0400
Docs: Use the 2.11 release notes
Update root.txt to point to the 2.11 release notes.
Signed-off-by: Robert Soulliere <robert.soulliere at mohawkcollege.ca>
diff --git a/docs/root.txt b/docs/root.txt
index 518970f..8ae307c 100644
--- a/docs/root.txt
+++ b/docs/root.txt
@@ -58,7 +58,7 @@ type – public, academic, special, school, and even tribal and home libraries
in over a dozen countries worldwide.
-include::RELEASE_NOTES_2_10.adoc[]
+include::RELEASE_NOTES_2_11.adoc[]
Software Installation
commit 6879ae9f0556471e089922a0aad60cfcd7b16782
Author: Dan Scott <dscott at laurentian.ca>
Date: Sun Mar 26 22:24:57 2017 -0400
Resolve a few doc build errors with images
* We need to match the case of images exactly on case-sensitive file systems
* Two dots in a file name confuses the simple-minded PDF build
* Comment out images that we don't actually have yet
Signed-off-by: Dan Scott <dscott at laurentian.ca>
diff --git a/docs/cataloging/z39.50_search_enhancements.txt b/docs/cataloging/z39.50_search_enhancements.txt
index a36632c..e6c4566 100644
--- a/docs/cataloging/z39.50_search_enhancements.txt
+++ b/docs/cataloging/z39.50_search_enhancements.txt
@@ -56,7 +56,7 @@ From this interface, you can rank the quality of incoming search results accordi
. Rank the quality of the records from Z39.50 sources by adding quality metrics for the match set. Click *MARC Tag and Subfield*, and enter the 901z tag and subfield, specify the Z39.50 source, and enter a quality metric. Source quality increases as the numeric quality increases.
-image::media/Locate_Z39.50_Matches4.jpg[Locate_Z39.50_Matches4]
+image::media/Locate_Z39_50_Matches4.jpg[Locate_Z39.50_Matches4]
@@ -88,15 +88,15 @@ Two new settings control the Z39.50 search enhancements.
. Click *Perform Search*.
-image::media/Locate_Z39.50_Matches1.jpg[Locate_Z39.50_Matches1]
+image::media/Locate_Z39_50_Matches1.jpg[Locate_Z39.50_Matches1]
. Status information will appear, including the number of records in the bucket that were searched, the matches that were found, and the progress of the search. When the search is complete, click *Open Queue*.
-image::media/Locate_Z39.50_Matches2.jpg[Locate_Z39.50_Matches2]
+image::media/Locate_Z39_50_Matches2.jpg[Locate_Z39.50_Matches2]
. The Vandelay Queue will display. Matching records are identified in the *Matches* column. From this interface, import records according to your normal procedure. It is suggested that to merge the incoming records with the catalog records, you should choose an option to import the records. Next, select either merge option from the drop down menu, click *Merge on Best Match*, and then click *Import*.
-image::media/Locate_Z39.50_Matches3.jpg[Locate_Z39.50_Matches3]
+image::media/Locate_Z39_50_Matches3.jpg[Locate_Z39.50_Matches3]
. The records from the Z39.50 search will merge with the catalog records. NOTE: A new column has been added to this interface to identify the Z39.50 source. When records are imported to the Vandelay queue via a record bucket, Evergreen tags the Z39.50 source and enters the data into the $901z.
diff --git a/docs/circulation/circulating_items_web_client.txt b/docs/circulation/circulating_items_web_client.txt
index 6db0950..4e0ca60 100644
--- a/docs/circulation/circulating_items_web_client.txt
+++ b/docs/circulation/circulating_items_web_client.txt
@@ -141,7 +141,7 @@ image::media/renew_action_web_client.png[]
3) If you want to specify the due date, click *Renew with Specific Due Date*. You will be prompted to select a due date. Once done, click *Apply*.
-image::media/renew_specific_date_web_client.png[]
+//image::media/renew_specific_date_web_client.png[]
Renewing by Item Barcode
@@ -303,7 +303,7 @@ Marking items damaged or missing and other functions
2) Select the item. Click on *Actions for Selected Items* -> *Mark Item Damaged* or *Mark Item Missing*.
-image::media/mark_missing_damaged_web_client.png[]
+// image::media/mark_missing_damaged_web_client.png[]
[NOTE]
Depending on the library's policy, when marking an item damaged, bills (cost and/or processing fee) may be inserted into the last borrower's account.
@@ -320,11 +320,11 @@ The *Edit Item Attributes* function on the *Actions for Selected Items* dropdown
3) The item record is displayed in the *Copy Editor*.
-image::media/copy_edit_alert_web_client.png[]
+//image::media/copy_edit_alert_web_client.png[]
4) Click *Alert Message* in the *Miscellaneous* column. The background color of the box changes. Type in the message then click *Apply*.
-image::media/copy_alert_message_web_client.png[]
+//image::media/copy_alert_message_web_client.png[]
5) Click *Modify Copies*, then confirm the action.
@@ -344,14 +344,14 @@ Once an item has been overdue for a configurable amount of time, Evergreen will
Optionally the patron can be billed for the item price, a long overdue processing fee, and any overdue fines can be voided from the account. Patrons can also be sent a notification that the item was marked long overdue.
-image::media/long_overdue1.JPG[Patron Account-Long Overdue]
+image::media/long_overdue1.jpg[Patron Account-Long Overdue]
*Checking in a Long Overdue item*
If an item that has been marked long overdue is checked in, an alert will appear on the screen informing the staff member that the item was long overdue. Once checked in, the item will go into the status of “In process”. Optionally, the item price and long overdue processing fee can be voided and overdue fines can be reinstated on the patron’s account. If the item is checked in at a library other than its home library, a library setting controls whether the item can immediately fill a hold or circulate, or if it needs to be sent to its home library for processing.
-image::media/long_overdue2.JPG[Long Overdue Checkin]
+image::media/long_overdue2.jpg[Long Overdue Checkin]
*Notification/Action Triggers*
diff --git a/docs/media/Locate_Z39.50_Matches1.jpg b/docs/media/Locate_Z39_50_Matches1.jpg
similarity index 100%
rename from docs/media/Locate_Z39.50_Matches1.jpg
rename to docs/media/Locate_Z39_50_Matches1.jpg
diff --git a/docs/media/Locate_Z39.50_Matches2.jpg b/docs/media/Locate_Z39_50_Matches2.jpg
similarity index 100%
rename from docs/media/Locate_Z39.50_Matches2.jpg
rename to docs/media/Locate_Z39_50_Matches2.jpg
diff --git a/docs/media/Locate_Z39.50_Matches3.jpg b/docs/media/Locate_Z39_50_Matches3.jpg
similarity index 100%
rename from docs/media/Locate_Z39.50_Matches3.jpg
rename to docs/media/Locate_Z39_50_Matches3.jpg
diff --git a/docs/media/Locate_Z39.50_Matches4.jpg b/docs/media/Locate_Z39_50_Matches4.jpg
similarity index 100%
rename from docs/media/Locate_Z39.50_Matches4.jpg
rename to docs/media/Locate_Z39_50_Matches4.jpg
-----------------------------------------------------------------------
Summary of changes:
docs/cataloging/z39.50_search_enhancements.txt | 8 ++++----
docs/circulation/circulating_items_web_client.txt | 12 ++++++------
docs/installation/server_upgrade.txt | 2 +-
....50_Matches1.jpg => Locate_Z39_50_Matches1.jpg} | Bin 76698 -> 76698 bytes
....50_Matches2.jpg => Locate_Z39_50_Matches2.jpg} | Bin 92574 -> 92574 bytes
....50_Matches3.jpg => Locate_Z39_50_Matches3.jpg} | Bin 42879 -> 42879 bytes
....50_Matches4.jpg => Locate_Z39_50_Matches4.jpg} | Bin 122099 -> 122099 bytes
docs/root.txt | 2 +-
8 files changed, 12 insertions(+), 12 deletions(-)
rename docs/media/{Locate_Z39.50_Matches1.jpg => Locate_Z39_50_Matches1.jpg} (100%)
rename docs/media/{Locate_Z39.50_Matches2.jpg => Locate_Z39_50_Matches2.jpg} (100%)
rename docs/media/{Locate_Z39.50_Matches3.jpg => Locate_Z39_50_Matches3.jpg} (100%)
rename docs/media/{Locate_Z39.50_Matches4.jpg => Locate_Z39_50_Matches4.jpg} (100%)
hooks/post-receive
--
Evergreen ILS
More information about the open-ils-commits
mailing list