[open-ils-commits] [GIT] Evergreen ILS branch master updated. c965386c9f9b31f31809872320ebece595bbab9b
Evergreen Git
git at git.evergreen-ils.org
Wed Sep 27 12:07:27 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 c965386c9f9b31f31809872320ebece595bbab9b (commit)
via 0585cec54308a58d6c2120f012f90bb749a77950 (commit)
via 368ecff22d8c50322beee5ac63c5d5f1bcad9541 (commit)
via 0ced845e7d21568315be6566b0e4c6edbba11111 (commit)
via 8e29c86050928fe3264ca2e4a6f7fb04e71c7bb7 (commit)
from 8b37fc66df5791eb14ca72b962ce04e9b513b447 (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 c965386c9f9b31f31809872320ebece595bbab9b
Author: Jane Sandberg <sandbej at linnbenton.edu>
Date: Wed Sep 27 07:42:48 2017 -0700
Docs: adding release note entry for docs re-org
Signed-off-by: Jane Sandberg <sandbej at linnbenton.edu>
Signed-off-by: Galen Charlton <gmc at equinoxinitiative.org>
diff --git a/docs/RELEASE_NOTES_3_0.adoc b/docs/RELEASE_NOTES_3_0.adoc
index 803aa8d..3002772 100644
--- a/docs/RELEASE_NOTES_3_0.adoc
+++ b/docs/RELEASE_NOTES_3_0.adoc
@@ -983,7 +983,26 @@ For example, to silence the alert that sounds after a successful patron search:
* ln -s ../../nosound.wav by_search.wav
-
+Documentation
+~~~~~~~~~~~~~
+
+The official Evergreen manual has been split into eight new manuals, each
+designed for a specific audience. This new approach is designed to make
+the documentation more readable and usable.
+
+The specific audiences for the new manuals are:
+
+* Acquisitions staff
+* Circulation staff
+* Cataloging staff
+* Public services staff who use the public catalog
+* Serials staff
+* System administrators who use the command line
+* System administrators who use the Web client
+* System administrators and programmers who wish to integrate Evergreen
+with other technologies
+
+All manuals are available at http://docs.evergreen-ils.org
Public catalog
commit 0585cec54308a58d6c2120f012f90bb749a77950
Author: Jane Sandberg <sandbej at linnbenton.edu>
Date: Wed Sep 27 07:29:19 2017 -0700
Docs: replacing OPAC with Public catalog
Signed-off-by: Jane Sandberg <sandbej at linnbenton.edu>
Signed-off-by: Galen Charlton <gmc at equinoxinitiative.org>
diff --git a/docs/RELEASE_NOTES_3_0.adoc b/docs/RELEASE_NOTES_3_0.adoc
index 267e1aa..803aa8d 100644
--- a/docs/RELEASE_NOTES_3_0.adoc
+++ b/docs/RELEASE_NOTES_3_0.adoc
@@ -986,8 +986,8 @@ For example, to silence the alert that sounds after a successful patron search:
-OPAC
-~~~~
+Public catalog
+~~~~~~~~~~~~~~
commit 368ecff22d8c50322beee5ac63c5d5f1bcad9541
Author: Jane Sandberg <sandbej at linnbenton.edu>
Date: Wed Sep 27 07:04:29 2017 -0700
Docs: streamlining release notes for user buckets; adding trimmed content to the manuals
Signed-off-by: Jane Sandberg <sandbej at linnbenton.edu>
Signed-off-by: Galen Charlton <gmc at equinoxinitiative.org>
diff --git a/docs/RELEASE_NOTES_3_0.adoc b/docs/RELEASE_NOTES_3_0.adoc
index b57be2c..267e1aa 100644
--- a/docs/RELEASE_NOTES_3_0.adoc
+++ b/docs/RELEASE_NOTES_3_0.adoc
@@ -692,12 +692,12 @@ interface by user barcode. It is also possible to add users to a User
Bucket by uploading a text file that contains a list of user barcodes.
From this interface it is possible to perform a set of specific batch update
-operations against users.
+operations on user records.
Editing users
+++++++++++++
-The fields can now be changed in batch via an action on the User Bucket
+These fields can now be changed in batch via an action on the User Bucket
grid if the staff user has the UPDATE_USER permission:
* Active flag
@@ -708,21 +708,7 @@ grid if the staff user has the UPDATE_USER permission:
* Barred flag (BAR_PATRON permission consulted)
* Internet Access Level
-Each change set requires a name. Buckets may have multiple change sets. All
-users in the Bucket at the time of processing are updated when the change
-set is processed, and change sets are processed immediately upon successful
-creation. The interface delivers progress information regarding the
-processing stage and percent of completion.
-
-While processing the users, the original value for each field edited is
-recorded for potential future rollback. Users can examine the success and
-failure of applied change sets.
-
-The user will be able to rollback the entire change set, but not parts thereof.
-The rollback will affect only those users that were successfully updated by the
-original change set and may be different from the current set of users in the
-Bucket. Users can manually discard change sets, removing them from the
-interface but preventing future rollback.
+Changes made in this interface can be rolled back.
As a batch process, rather than a direct edit, this mechanism explicitly skips
processing of Action/Trigger event definitions for user update.
@@ -733,15 +719,7 @@ Deleting users
The batch edit mechanism also allows for the batch deletion of user. The staff
user must have both the UPDATE_USER and DELETE_USER permissions.
-Each delete set requires a name. Buckets may have multiple delete sets. All
-users in the Bucket at the time of processing are marked as deleted when
-the delete set is processed. The interface delivers progress information
-regarding the processing stage and percent of completion.
-
-While processing the users, the original value for the "deleted" field will be
-recorded for potential future rollback. Users are able to examine the
-success and failure of applied delete sets in the same interface used for the
-above described change sets.
+Changes made in this interface can be rolled back.
As a batch process, rather than a direct edit, this mechanism explicitly skips
processing of Action/Trigger event definitions for user deletion.
@@ -754,9 +732,7 @@ Editing Statistical Category Entries
All users in the bucket can have their Statistical Category Entries
modified. Unlike user data field updates, modification of Statistical
-Category Entries is permanent and cannot be rolled back. No named change
-sets are required. The interface will deliver progress information regarding
-the processing stage and percent of completion.
+Category Entries is permanent and cannot be rolled back.
As a batch process, rather than a direct edit, this mechanism explicitly skips
processing of Action/Trigger event definitions for user update.
diff --git a/docs/admin/qstore_service.adoc b/docs/admin/qstore_service.adoc
new file mode 100644
index 0000000..cd4622e
--- /dev/null
+++ b/docs/admin/qstore_service.adoc
@@ -0,0 +1,6 @@
+QStore service
+--------------
+
+The QStore service is used by the user buckets feature
+in the Web client.
+
diff --git a/docs/circulation/user_buckets.adoc b/docs/circulation/user_buckets.adoc
new file mode 100644
index 0000000..d0d61b9
--- /dev/null
+++ b/docs/circulation/user_buckets.adoc
@@ -0,0 +1,90 @@
+User buckets
+============
+
+Introduction
+------------
+indexterm:[patron buckets]
+indexterm:[patrons, batch operations]
+
+You can select and group a set of users into a User Bucket.
+You can add users to a User Bucket from the Patron Search
+interface or directly from the User Bucket interface by user barcode.
+It is also possible to add users to a User
+Bucket by uploading a text file that contains a list of user barcodes.
+
+From this interface it is possible to perform a set of specific batch update
+operations on the group of users you have identified.
+
+Editing users
+-------------
+indexterm:[batch edit, patrons]
+
+You can change the following fields in batch:
+
+ * Active flag
+ * Primary Permission Group (group application permissions consulted)
+ * Juvenile flag
+ * Home Library (if you have the UPDATE_USER permission for both the original and destination libraries)
+ * Privilege Expiration Date
+ * Barred flag (if you have the BAR_PATRON permission)
+ * Internet Access Level
+
+NOTE: You will need the UPDATE_USER permission.
+
+Each change set requires a name. Buckets may have multiple change sets. All
+users in the Bucket at the time of processing are updated when the change
+set is processed, and change sets are processed immediately upon successful
+creation. The interface delivers progress information regarding the
+processing stage and percent of completion.
+
+While processing the users, the original value for each field edited is
+recorded for potential future rollback. Users can examine the success and
+failure of applied change sets.
+
+The user will be able to rollback the entire change set, but not parts thereof.
+The rollback will affect only those users that were successfully updated by the
+original change set and may be different from the current set of users in the
+Bucket. Users can manually discard change sets, removing them from the
+interface but preventing future rollback.
+
+As a batch process, rather than a direct edit, this mechanism explicitly skips
+processing of Action/Trigger event definitions for user update, so users will
+not receive any notifications that they might otherwise receive when their accounts
+are edited.
+
+Deleting users
+--------------
+indexterm:[batch delete, patrons]
+
+You may also delete users as a batch.
+
+NOTE: You will need the UPDATE_USER and DELETE_USER permissions.
+
+Each delete set requires a name. Buckets may have multiple delete sets. All
+users in the Bucket at the time of processing are marked as deleted when
+the delete set is processed. The interface delivers progress information
+regarding the processing stage and percent of completion.
+
+While processing the users, the original value for the "deleted" field will be
+recorded for potential future rollback. Users are able to examine the
+success and failure of applied delete sets in the same interface used for the
+above described change sets.
+
+As a batch process, rather than a direct edit, this mechanism explicitly skips
+processing of Action/Trigger event definitions for user deletion.
+
+This mechanism does not completely purge the user from the database. User data
+will still be available to system administrators with database access.
+
+Editing Statistical Category Entries
+------------------------------------
+
+All users in the bucket can have their Statistical Category Entries
+modified. Unlike user data field updates, modification of Statistical
+Category Entries is permanent and cannot be rolled back. No named change
+sets are required. The interface will deliver progress information regarding
+the processing stage and percent of completion.
+
+As a batch process, rather than a direct edit, this mechanism explicitly skips
+processing of Action/Trigger event definitions for user update.
+
diff --git a/docs/root_circulation.adoc b/docs/root_circulation.adoc
index d43eefd..32fc0c4 100644
--- a/docs/root_circulation.adoc
+++ b/docs/root_circulation.adoc
@@ -54,6 +54,12 @@ include::circulation/booking.adoc[]
include::circulation/triggered_events.adoc[]
+:leveloffset: 0
+
+include::circulation/user_buckets.adoc[]
+
+:leveloffset: -1
+
include::opac/using_the_public_access_catalog.adoc[]
:leveloffset: 0
diff --git a/docs/root_command_line_admin.adoc b/docs/root_command_line_admin.adoc
index d9dcbf1..b7a39a9 100644
--- a/docs/root_command_line_admin.adoc
+++ b/docs/root_command_line_admin.adoc
@@ -52,16 +52,25 @@ Individual Evergreen Components
include::development/intro_opensrf.adoc[]
-include::development/pgtap.adoc[]
-
:leveloffset: 0
include::development/support_scripts.adoc[]
include::admin/actiontriggers_process.adoc[]
+Daemons and services
+--------------------
+
+:leveloffset: 1
+
include::reports/reporter_daemon.adoc[]
+include::admin/qstore_service.adoc[]
+
+
+include::development/pgtap.adoc[]
+
+:leveloffset: 0
System Configuration
====================
diff --git a/docs/root_staff_client_admin.adoc b/docs/root_staff_client_admin.adoc
index 3cd288e..6099eb2 100644
--- a/docs/root_staff_client_admin.adoc
+++ b/docs/root_staff_client_admin.adoc
@@ -150,6 +150,12 @@ Negative balances
This section needs to be written
+:leveloffset: 1
+
+include::circulation/user_buckets.adoc[]
+
+:leveloffset: 0
+
Circulation timesavers and workflows
------------------------------------
commit 0ced845e7d21568315be6566b0e4c6edbba11111
Author: Kathy Lussier <klussier at masslnc.org>
Date: Wed Sep 27 11:18:11 2017 -0400
Docs: Adding more acknowledgements for web client contributions
Adding contributors who participated through LP and by doing early testing
for Equinox.
Signed-off-by: Kathy Lussier <klussier at masslnc.org>
Signed-off-by: Galen Charlton <gmc at equinoxinitiative.org>
diff --git a/docs/RELEASE_NOTES_3_0.adoc b/docs/RELEASE_NOTES_3_0.adoc
index edae4e1..b57be2c 100644
--- a/docs/RELEASE_NOTES_3_0.adoc
+++ b/docs/RELEASE_NOTES_3_0.adoc
@@ -1307,15 +1307,15 @@ Acknowledgments
Web Client Acknowledgements
~~~~~~~~~~~~~~~~~~~~~~~~~~~
-The project to move Evergreen to a new browser-based web client launched four
-years ago at the September 2017 Evergreen developer hack-a-way when the
+The project to develop a new browser-based web client launched four
+years ago at the September 2013 Evergreen developer hack-a-way when the
developer community voted to move away from the XUL client and explore other
platforms. The first web client preview became available in Evergreen 2.7 when
-circulation was moved the the new platform.
+circulation was available in the new platform.
The browser-based client is available due to the work of many coders, testers,
-documentors, translators, project managers, spec writers, funders and other
-contributors over the past four years.
+bug reporters, documentors, translators, project managers, spec writers, funders
+and other contributors over the past four years.
The Evergreen project would like to acknowledge the following organizations
that funded development of the Web Staff Client:
@@ -1336,12 +1336,13 @@ that funded development of the Web Staff Client:
* SC Lends
The Evergreen project would also like to thank the following individuals who
-contributed code, translations, documentations patches, tests, technical
-specifications and proect management to the Web Staff Client:
+contributed code, translations, documentations patches, tests, bug reports,
+technical specifications and project management to the Web Staff Client:
* Jason Boyer
* Adam Bowling
* Christine Burns
+* Steve Callender
* Eva Cerniňáková
* Galen Charlton
* Dawn Dale
@@ -1353,6 +1354,7 @@ specifications and proect management to the Web Staff Client:
* Sally Fortin
* Jeff Godin
* Rogan Hamby
+* Elaine Hardy
* Blake Henderson
* Billy Horn
* Skye Howard
@@ -1361,7 +1363,9 @@ specifications and proect management to the Web Staff Client:
* Tina Ji
* Mary Jinglewski
* Angela Kilsdonk
+* Joan Kranich
* Victoria Lewis
+* Mary Llewelyn
* Jeanette Lundgren
* Kathy Lussier
* Terran McCanna
@@ -1374,19 +1378,24 @@ specifications and proect management to the Web Staff Client:
* Jillianne Presley
* Jennifer Pringle
* Michelle Purcell
+* Erica Rohlfs
* Mike Rylander
* Jane Sandberg
+* Janet Schrader
* Dan Scott
* Chris Sharp
* Ben Shum
* Clare Sobotka
+* Tim Spindler
* Remington Steed
* Jason Stephenson
* Josh Stompro
* Yamil Suarez
+* Amy Terlaga
* Scott Thomas
* Anahi Valdez
* Cesar Velez
+* Jessica Venturo
* Dan Wells
* Beth Willis
* Tigran Zargaryan
commit 8e29c86050928fe3264ca2e4a6f7fb04e71c7bb7
Author: Kathy Lussier <klussier at masslnc.org>
Date: Tue Sep 26 17:38:23 2017 -0400
Docs: Web client release notes and acknowledgements
Adding a special section on the web client to the release notes, as well as
acknnowledgements for everyone who has contributed to the project.
Signed-off-by: Kathy Lussier <klussier at masslnc.org>
Signed-off-by: Galen Charlton <gmc at equinoxinitiative.org>
diff --git a/docs/RELEASE_NOTES_3_0.adoc b/docs/RELEASE_NOTES_3_0.adoc
index 2b59def..edae4e1 100644
--- a/docs/RELEASE_NOTES_3_0.adoc
+++ b/docs/RELEASE_NOTES_3_0.adoc
@@ -130,6 +130,30 @@ the XUL staff client is slated to be entirely removed.
New Features
------------
+New Staff Client
+~~~~~~~~~~~~~~~~
+
+Evergreen 3.0 features a new, modern staff client that runs in the web browser
+and can be used on desktop and mobile devices. All functional areas of the
+system, including circulation, cataloging, acquisitions, serials, reports,
+booking, administration, and offline circulation, are available in the new staff
+client. Chrome and Firefox are officially supported for use with the web client.
+
+Library staff will no longer need to download separate software to perform most
+actions in Evergreen. A Chrome plugin called Hatch will be available as a
+separate installation for workstations that require seamless, dialog-free
+printing to multiple printers.
+
+In addition to adding more portability and stability, the new staff client also
+presents a cleaner and more modern interface for users. By virtue of running in
+a browser, actions that users are accustomed to performing on other web sites
+should now be available in the Evergreen client.
+
+The old, XUL client will continue to be available to allow for a gradual
+transition to the browser-based client, but no new features will be added. The
+old client will totally be removed from Evergreen in the Fall 2018 3.2.0
+release.
+
Administration
@@ -1279,6 +1303,97 @@ in the future.
Acknowledgments
---------------
+
+Web Client Acknowledgements
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The project to move Evergreen to a new browser-based web client launched four
+years ago at the September 2017 Evergreen developer hack-a-way when the
+developer community voted to move away from the XUL client and explore other
+platforms. The first web client preview became available in Evergreen 2.7 when
+circulation was moved the the new platform.
+
+The browser-based client is available due to the work of many coders, testers,
+documentors, translators, project managers, spec writers, funders and other
+contributors over the past four years.
+
+The Evergreen project would like to acknowledge the following organizations
+that funded development of the Web Staff Client:
+
+* Bibliomation
+* British Columbia Libraries Cooperative
+* C/W MARS
+* Georgia Public Library Service
+* Grand Rapids Public Library
+* The Howe Library
+* Kenton County Public Library
+* King County Library System
+* MassLNC
+* NC Cardinal
+* OhioNet
+* Pennsylvania Integrated Library System
+* Pioneer Library System
+* SC Lends
+
+The Evergreen project would also like to thank the following individuals who
+contributed code, translations, documentations patches, tests, technical
+specifications and proect management to the Web Staff Client:
+
+* Jason Boyer
+* Adam Bowling
+* Christine Burns
+* Eva Cerniňáková
+* Galen Charlton
+* Dawn Dale
+* Jeff Davis
+* Grace Dunbar
+* Bill Erickson
+* Jason Etheridge
+* Lynn Floyd
+* Sally Fortin
+* Jeff Godin
+* Rogan Hamby
+* Blake Henderson
+* Billy Horn
+* Skye Howard
+* Kyle Huckins
+* Linda Jansová
+* Tina Ji
+* Mary Jinglewski
+* Angela Kilsdonk
+* Victoria Lewis
+* Jeanette Lundgren
+* Kathy Lussier
+* Terran McCanna
+* Christine Morgan
+* Michele Morgan
+* Stephen Moss
+* Andrea Neiman
+* Nawras Othman
+* Freddy Enrique Pelayo Huapalla
+* Jillianne Presley
+* Jennifer Pringle
+* Michelle Purcell
+* Mike Rylander
+* Jane Sandberg
+* Dan Scott
+* Chris Sharp
+* Ben Shum
+* Clare Sobotka
+* Remington Steed
+* Jason Stephenson
+* Josh Stompro
+* Yamil Suarez
+* Scott Thomas
+* Anahi Valdez
+* Cesar Velez
+* Dan Wells
+* Beth Willis
+* Tigran Zargaryan
+
+Evergreen 3.0 Acknowledgements
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
The Evergreen project would like to acknowledge the following
organizations that commissioned developments in this release of
Evergreen:
-----------------------------------------------------------------------
Summary of changes:
docs/RELEASE_NOTES_3_0.adoc | 181 +++++++++++++++++++++++++++++------
docs/admin/qstore_service.adoc | 6 +
docs/circulation/user_buckets.adoc | 90 ++++++++++++++++++
docs/root_circulation.adoc | 6 +
docs/root_command_line_admin.adoc | 13 ++-
docs/root_staff_client_admin.adoc | 6 +
6 files changed, 269 insertions(+), 33 deletions(-)
create mode 100644 docs/admin/qstore_service.adoc
create mode 100644 docs/circulation/user_buckets.adoc
hooks/post-receive
--
Evergreen ILS
More information about the open-ils-commits
mailing list