[open-ils-commits] [GIT] Evergreen ILS branch master updated. 86c1ed702566af9d0011b8368b60af25bdc4997c
Evergreen Git
git at git.evergreen-ils.org
Sun Oct 1 13:15:18 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, master has been updated
via 86c1ed702566af9d0011b8368b60af25bdc4997c (commit)
via 52facdb418d82fee571931103cdfcb5661e12726 (commit)
from 24c896d8226e67af2d97f12a9ca636c16f111b64 (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 86c1ed702566af9d0011b8368b60af25bdc4997c
Author: Jane Sandberg <sandbej at linnbenton.edu>
Date: Sun Oct 1 10:14:56 2017 -0700
Docs: cleaning up client sysadmin manual
Signed-off-by: Jane Sandberg <sandbej at linnbenton.edu>
diff --git a/docs/admin/closed_dates.adoc b/docs/admin/closed_dates.adoc
new file mode 100644
index 0000000..678e528
--- /dev/null
+++ b/docs/admin/closed_dates.adoc
@@ -0,0 +1,42 @@
+Set closed dates using the Closed Dates Editor
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+indexterm:[Closed Dates]
+
+These dates are in addition to your regular weekly closed days (see the section called “Library Hours of Operation”). Both regular closed days and those entered in the Closed Dates Editor affect due dates and fines:
+
+* *Due dates.* Due dates that would fall on closed days are automatically pushed forward to the next open day. Likewise, if an item is checked out at 8pm, for example, and would normally be due on a day when the library closes before 8pm, Evergreen pushes the due date forward to the next open day.
+* *Overdue fines.* Overdue fines may not be charged on days when the library is closed. This fine behavior depends on how the _Charge fines on overdue circulations when closed_ setting is configured in the Library Settings Editor.
+
+Closed dates do not affect the processing delays for Action/Triggers. For example, if your library has a trigger event that marks items as lost after 30 days, that 30 day period will include both open and closed dates.
+
+Adding a closure
+^^^^^^^^^^^^^^^^
+
+. Select _Administration > Local Administration_.
+. Select _Closed Dates Editor_.
+. Select type of closure: typically Single Day or Multiple Day.
+. Click the Calendar gadget to select the All Day date or starting and ending
+ dates.
+. Enter a Reason for closure (optional).
+. Click *Apply* to all of my libraries if your organizational unit has children
+ units that will also be closed.
+. Click *Save*.
+
+image::media/closed_dates.png[]
+
+Now that your organizational structure is established, you can begin
+configuring permissions for the staff users of your Evergreen system.
+
+Detailed closure
+^^^^^^^^^^^^^^^^
+
+If your closed dates include a portion of a business day, you should create a detailed closing.
+
+. Select _Administration -> Local Administration_.
+. Select _Closed Dates Editor_.
+. Select _Add Detailed Closing_.
+. Enter applicable dates, times, and a descriptive reason for the closing.
+. Click Save.
+. Check the Apply to all of my libraries box if your library is a multi-branch system and the closing applies to all of your branches.
+
diff --git a/docs/admin/hours.adoc b/docs/admin/hours.adoc
new file mode 100644
index 0000000..2fd73d3
--- /dev/null
+++ b/docs/admin/hours.adoc
@@ -0,0 +1,10 @@
+Setting regular library hours
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You may do this in _Administation_ > _Server Administration_ > _Organizational
+Units_.
+
+The *Hours of Operation* tab is where you enter regular, weekly hours. Holiday
+and other closures are set in the *Closed Dates Editor*. Hours of operation and
+closed dates impact due dates and fine accrual.
+
diff --git a/docs/admin_initial_setup/describing_your_organization.adoc b/docs/admin_initial_setup/describing_your_organization.adoc
index e5355c4..33d035e 100644
--- a/docs/admin_initial_setup/describing_your_organization.adoc
+++ b/docs/admin_initial_setup/describing_your_organization.adoc
@@ -98,45 +98,3 @@ Run this script as the *opensrf* Linux account.
autogen.sh
------------------------------------------------------------------------------
-Set closed dates using the Closed Dates Editor
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-indexterm:[Closed Dates]
-
-These dates are in addition to your regular weekly closed days (see the section called “Library Hours of Operation”). Both regular closed days and those entered in the Closed Dates Editor affect due dates and fines:
-
-* *Due dates.* Due dates that would fall on closed days are automatically pushed forward to the next open day. Likewise, if an item is checked out at 8pm, for example, and would normally be due on a day when the library closes before 8pm, Evergreen pushes the due date forward to the next open day.
-* *Overdue fines.* Overdue fines may not be charged on days when the library is closed. This fine behavior depends on how the _Charge fines on overdue circulations when closed_ setting is configured in the Library Settings Editor.
-
-Closed dates do not affect the processing delays for Action/Triggers. For example, if your library has a trigger event that marks items as lost after 30 days, that 30 day period will include both open and closed dates.
-
-Adding a closure
-^^^^^^^^^^^^^^^^
-
-. Select _Administration > Local Administration_.
-. Select _Closed Dates Editor_.
-. Select type of closure: typically Single Day or Multiple Day.
-. Click the Calendar gadget to select the All Day date or starting and ending
- dates.
-. Enter a Reason for closure (optional).
-. Click *Apply* to all of my libraries if your organizational unit has children
- units that will also be closed.
-. Click *Save*.
-
-image::media/closed_dates.png[]
-
-Now that your organizational structure is established, you can begin
-configuring permissions for the staff users of your Evergreen system.
-
-Detailed closure
-^^^^^^^^^^^^^^^^
-
-If your closed dates include a portion of a business day, you should create a detailed closing.
-
-. Select _Administration -> Local Administration_.
-. Select _Closed Dates Editor_.
-. Select _Add Detailed Closing_.
-. Enter applicable dates, times, and a descriptive reason for the closing.
-. Click Save.
-. Check the Apply to all of my libraries box if your library is a multi-branch system and the closing applies to all of your branches.
-
diff --git a/docs/root_staff_client_admin.adoc b/docs/root_staff_client_admin.adoc
index d6bbea7..5d8a236 100644
--- a/docs/root_staff_client_admin.adoc
+++ b/docs/root_staff_client_admin.adoc
@@ -157,15 +157,9 @@ Library closures
This section describes both everyday closures and specific details suitable for school and academic libraries that operate on a term or semester system.
-Library hours
-~~~~~~~~~~~~~
+include::admin/hours.adoc[]
-In OU settings
-
-Closed dates
-~~~~~~~~~~~~
-
-Need to move out of the describing your OU docs
+include::admin/closed_dates.adoc[]
:leveloffset: 1
commit 52facdb418d82fee571931103cdfcb5661e12726
Author: Jane Sandberg <sandbej at linnbenton.edu>
Date: Sun Oct 1 09:43:10 2017 -0700
Docs: Adding search config info to client admin manual
Signed-off-by: Jane Sandberg <sandbej at linnbenton.edu>
diff --git a/docs/admin/search_settings_web_client.adoc b/docs/admin/search_settings_web_client.adoc
new file mode 100644
index 0000000..9ceaa9d
--- /dev/null
+++ b/docs/admin/search_settings_web_client.adoc
@@ -0,0 +1,63 @@
+Adjusting Relevance Ranking and Indexing
+----------------------------------------
+
+Metabib Class FTS Config Maps
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+NOTE: These settings will apply to all libraries in your
+consortium. There is no way to apply these settings to
+only one library or branch.
+
+* _Field Class_ - Reference to a field defined in
+ Administration > Server Administration > MARC
+ Search/Facet Classes.
+* _Text Search Config_ - Which Text Search config to use
+* _Active_ - Check this checkbox to use this configuration
+ for searching and indexing.
+* _Index Weight_ - The FTS index weight to use for this
+ FTS config. Should be A, B, C, or D, defaults to C.
+ You can see the exact numeric values for A, B, C, and
+ D in Administration > Server Administration > MARC
+ Search/Facet Classes.
+* _Index Language_ - An optional 3-letter code
+ representing the language the record should be set to
+ in order for this FTS config to be used for indexing.
+ should be set to in order for this FTS config to be used for indexing
+* _Search Language_ - An optional 3-letter code representing
+ what preferred language search should be selected by the
+ end-user in order for this FTS config to be applied to
+ their search.
+* _Always Use_ - Check this checkbox to override the
+ configuration for a more specific field. For example,
+ if you check this box when entering a setting for the
+ _author_ metabib class, it will override any settings
+ you have made for the _author|personal_ field in
+ the Administration > Server Administration > Metabib
+ Field FTS Config Maps screen.
+
+Metabib Field FTS Config Maps
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+NOTE: These settings will apply to all libraries in your
+consortium. There is no way to apply these settings to
+only one library or branch.
+
+* _Metabib Field_ - Reference to a field defined in
+ Administration > Server Administration > MARC
+ Search/Facet Fields.
+* _Text Search Config_ - Which Text Search config to use
+* _Active_ - Check this checkbox to use this configuration
+ for searching and indexing.
+* _Index Weight_ - The FTS index weight to use for this
+ FTS config. Should be A, B, C, or D, defaults to C.
+ You can see the exact numeric values for A, B, C, and
+ D in Administration > Server Administration > MARC
+ Search/Facet Classes.
+* _Index Language_ - An optional 3-letter code
+ representing the language the record should be set to
+ in order for this FTS config to be used for indexing.
+ should be set to in order for this FTS config to be used for indexing
+* _Search Language_ - An optional 3-letter code representing
+ what preferred language search should be selected by the
+ end-user in order for this FTS config to be applied to
+ their search.
diff --git a/docs/root_staff_client_admin.adoc b/docs/root_staff_client_admin.adoc
index 2a1aa30..d6bbea7 100644
--- a/docs/root_staff_client_admin.adoc
+++ b/docs/root_staff_client_admin.adoc
@@ -184,6 +184,15 @@ include::circulation/self_check_configuration.adoc[]
:leveloffset: 0
+// SEARCH ADMIN
+Search Settings
+===============
+
+include::admin/search_settings_web_client.adoc[]
+
+include::admin/popularity_badges_web_client.adoc[]
+
+
// Patron UX
Patron User Experience Administration
=====================================
-----------------------------------------------------------------------
Summary of changes:
docs/admin/closed_dates.adoc | 42 +++++++++++++
docs/admin/hours.adoc | 10 +++
docs/admin/search_settings_web_client.adoc | 63 ++++++++++++++++++++
.../describing_your_organization.adoc | 42 -------------
docs/root_staff_client_admin.adoc | 19 ++++---
5 files changed, 126 insertions(+), 50 deletions(-)
create mode 100644 docs/admin/closed_dates.adoc
create mode 100644 docs/admin/hours.adoc
create mode 100644 docs/admin/search_settings_web_client.adoc
hooks/post-receive
--
Evergreen ILS
More information about the open-ils-commits
mailing list