[GIT] Evergreen ILS branch main updated. 80abca0014915b8a9477341a13dbfe430cf04a7b
by Git User 10 Jul '25
by Git User 10 Jul '25
10 Jul '25
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, main has been updated
via 80abca0014915b8a9477341a13dbfe430cf04a7b (commit)
from 8839b4645d92496dd08ed09530c911d353589741 (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 80abca0014915b8a9477341a13dbfe430cf04a7b
Author: Stephanie Leary <stephanie.leary(a)equinoxoli.org>
Date: Wed Jul 2 19:18:03 2025 +0000
LP2115824 metarecord hold format, language labels
Adds form labels to the language and format selects in the metarecord
section of the Place Hold form.
Also changes the heading to read 'Select your desired formats and
languages' based on screen reader user feedback.
Release-note: Adds missing form labels, revises heading for metarecord
holds formats and languages options
Signed-off-by: Stephanie Leary <stephanie.leary(a)equinoxoli.org>
Signed-off-by: Garry Collum <gcollum(a)gmail.com>
Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com>
diff --git a/Open-ILS/src/templates-bootstrap/opac/parts/metarecord_hold_filters.tt2 b/Open-ILS/src/templates-bootstrap/opac/parts/metarecord_hold_filters.tt2
index c1e2df691d..0cb716ff32 100755
--- a/Open-ILS/src/templates-bootstrap/opac/parts/metarecord_hold_filters.tt2
+++ b/Open-ILS/src/templates-bootstrap/opac/parts/metarecord_hold_filters.tt2
@@ -19,14 +19,15 @@ limiting the set of desired records for a given metarecord.
END;
%]
<hr>
-<h4>[% l('Select your desired format(s).') %]</h4>
+<h4>[% l('Select your desired formats and languages') %]</h4>
<div class="row">
<div class="col-6">
<div class="metarecord_filter_header">
</div>
+ <label class="form-label" for="metarecord_formats_[% target_id %]">[% l('Formats') %]</label>
<select multiple='multiple' class="form-control"
- name="metarecord_formats_[% target_id %]">
+ name="metarecord_formats_[% target_id %]" id="metarecord_formats_[% target_id %]">
[% FOR ccvm IN
hold_data.metarecord_filters.formats.sort('search_label');
NEXT IF ccvm.opac_visible == 'f' %]
@@ -43,9 +44,9 @@ limiting the set of desired records for a given metarecord.
my_lang = ctx.get_i18n_l(ctx.eg_locale).marc_code;
%]
<div class="col-6">
-
+ <label class="form-label" for="metarecord_langs_[% target_id %]">[% l('Languages') %]</label>
<select multiple='multiple' class="form-control"
- name="metarecord_langs_[% target_id %]">
+ name="metarecord_langs_[% target_id %]" id="metarecord_langs_[% target_id %]">
[% FOR lang_ccvm IN hold_data.metarecord_filters.langs.sort('value');
NEXT IF lang_ccvm.opac_visible == 'f';
selected = 0;
-----------------------------------------------------------------------
Summary of changes:
.../templates-bootstrap/opac/parts/metarecord_hold_filters.tt2 | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
hooks/post-receive
--
Evergreen ILS
1
0
[GIT] Evergreen ILS branch rel_3_14 updated. c20a70c873f4f7ccbf71b58abb9f970781fe3f04
by Git User 10 Jul '25
by Git User 10 Jul '25
10 Jul '25
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_3_14 has been updated
via c20a70c873f4f7ccbf71b58abb9f970781fe3f04 (commit)
from 452048e984ab360531be9639358b37848addb9be (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 c20a70c873f4f7ccbf71b58abb9f970781fe3f04
Author: Stephanie Leary <stephanie.leary(a)equinoxoli.org>
Date: Wed Jul 2 19:18:03 2025 +0000
LP2115824 metarecord hold format, language labels
Adds form labels to the language and format selects in the metarecord
section of the Place Hold form.
Also changes the heading to read 'Select your desired formats and
languages' based on screen reader user feedback.
Release-note: Adds missing form labels, revises heading for metarecord
holds formats and languages options
Signed-off-by: Stephanie Leary <stephanie.leary(a)equinoxoli.org>
Signed-off-by: Garry Collum <gcollum(a)gmail.com>
Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com>
diff --git a/Open-ILS/src/templates-bootstrap/opac/parts/metarecord_hold_filters.tt2 b/Open-ILS/src/templates-bootstrap/opac/parts/metarecord_hold_filters.tt2
index c1e2df691d..0cb716ff32 100755
--- a/Open-ILS/src/templates-bootstrap/opac/parts/metarecord_hold_filters.tt2
+++ b/Open-ILS/src/templates-bootstrap/opac/parts/metarecord_hold_filters.tt2
@@ -19,14 +19,15 @@ limiting the set of desired records for a given metarecord.
END;
%]
<hr>
-<h4>[% l('Select your desired format(s).') %]</h4>
+<h4>[% l('Select your desired formats and languages') %]</h4>
<div class="row">
<div class="col-6">
<div class="metarecord_filter_header">
</div>
+ <label class="form-label" for="metarecord_formats_[% target_id %]">[% l('Formats') %]</label>
<select multiple='multiple' class="form-control"
- name="metarecord_formats_[% target_id %]">
+ name="metarecord_formats_[% target_id %]" id="metarecord_formats_[% target_id %]">
[% FOR ccvm IN
hold_data.metarecord_filters.formats.sort('search_label');
NEXT IF ccvm.opac_visible == 'f' %]
@@ -43,9 +44,9 @@ limiting the set of desired records for a given metarecord.
my_lang = ctx.get_i18n_l(ctx.eg_locale).marc_code;
%]
<div class="col-6">
-
+ <label class="form-label" for="metarecord_langs_[% target_id %]">[% l('Languages') %]</label>
<select multiple='multiple' class="form-control"
- name="metarecord_langs_[% target_id %]">
+ name="metarecord_langs_[% target_id %]" id="metarecord_langs_[% target_id %]">
[% FOR lang_ccvm IN hold_data.metarecord_filters.langs.sort('value');
NEXT IF lang_ccvm.opac_visible == 'f';
selected = 0;
-----------------------------------------------------------------------
Summary of changes:
.../templates-bootstrap/opac/parts/metarecord_hold_filters.tt2 | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
hooks/post-receive
--
Evergreen ILS
1
0
[GIT] Evergreen ILS branch rel_3_14 updated. 452048e984ab360531be9639358b37848addb9be
by Git User 10 Jul '25
by Git User 10 Jul '25
10 Jul '25
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_3_14 has been updated
via 452048e984ab360531be9639358b37848addb9be (commit)
via c615bf4ae369da464a70a0ccd053d29c7bcd4242 (commit)
via ae7580767555f145d9430b0a953a12e4a1628daf (commit)
via 147f2017ec69aa916b475286d739d68145119187 (commit)
from 612117e942aa0b01db6fe11c9d3e18f064f13e06 (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 452048e984ab360531be9639358b37848addb9be
Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com>
Date: Thu Jul 3 16:16:05 2025 -0400
Docs: Updates to "org unit" terminology lsa-address_alert.adoc
Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com>
diff --git a/docs/modules/admin/pages/lsa-address_alert.adoc b/docs/modules/admin/pages/lsa-address_alert.adoc
index d2f264d58e..9f26d48e00 100644
--- a/docs/modules/admin/pages/lsa-address_alert.adoc
+++ b/docs/modules/admin/pages/lsa-address_alert.adoc
@@ -6,43 +6,41 @@ indexterm:[address alerts]
The Address Alert module gives administrators the ability to notify staff with a custom message when
addresses with certain patterns are entered in patron records.
-This feature only serves to provide pertinent information to your library system's circulation staff during the registration process. An alert will not prevent the new patron account from being registered and the information will not be permanently associated with the patron account.
+This feature only serves to provide pertinent information to your library system's circulation staff during the registration process. An alert will not prevent the new patron account from being registered, and the information will not be permanently associated with the patron account.
-To access the Address Alert module, select *Administration* -> *Local Administration* -> *Address Alerts*.
+To access the Address Alert module, select *Administration* -> *Local Administration* -> *Address Alerts*.
[NOTE]
==========
-You must have Local Administrator permissions or ADMIN_ADDRESS_ALERT permission to access the Address Alert module.
+You must have Local Administrator permissions or the ADMIN_ADDRESS_ALERT permission to access the Address Alert module.
==========
== General Usage Examples ==
-- Alert staff when an address for a large apartment is entered to prompt them to ask for unit number.
+- Alert staff when an address for a large apartment is entered to prompt them to ask for a unit number.
- Alert staff when the address of a hotel or other temporary housing is entered.
- Alert staff when an address for a different country is entered.
-- Alert staff when a specific city or zip code is entered if that city or zip code needs to be handled in a special way. If you have a neighboring city that you don't have a reciprocal relationship with, you could notify staff that a fee card is required for this customer.
+- Alert staff when a specific city or zip code is entered if that city or zip code needs to be handled in a special way. If you have a neighboring city that you don't have a reciprocal relationship with, you could notify staff that a fee card is required for this customer.
== Access Control and Scoping ==
-Each address alert is tied to an Org Unit and will only be matched against staff client instances of that Org Unit and its children.
+Each address alert is tied to an organizational unit and will only be matched against staff client instances of that organizational unit and its children.
-When viewing the address alerts you will only see the alerts associated with the specific org unit selected in the *"Context Org Unit"* selection box. You won't see alerts associated with parent org units, so the list of alerts isn't a list of all alerts that may effect your org unit, only of the ones that you can edit.
+When viewing the address alerts, you will only see the alerts associated with the specific organizational unit selected in the context selection box. You won't see alerts associated with parent organizational units, so the list of alerts isn't a list of all alerts that may affect your organizational unit, only of the ones that you can edit.
-The specific permission that controls access to configuring this feature is ADMIN_ADDRESS_ALERT. Local Administrator level users will already have this permission. It is possible for the Local Administrator to grant this permission to other staff.
-
-== Adding a new Address Alert ==
+== Adding a New Address Alert ==
How to add an address to the alert list:
. Log into the Evergreen Staff Client using a Local Administrator account or another account that has been granted the proper permission.
-. Click on Administration -> Local Administration -> Address Alerts.
-. Click "New Address Alert."
+. Click on *Administration* -> *Local Administration* -> *Address Alerts*.
+. Click *New Address Alert*.
. A form will open with the following fields to fill out:
+
.New Address Alert Fields
|===
|*Field* |*Description*
-| Owner |Which Org Unit owns this alert. Set this to your system or branch.
+| Owner |Which organizational unit owns this alert. Set this to your system or branch.
| Alert Message |Message that will be displayed to staff when this alert is triggered.
| Street (1) |Street 1 field regular expression.
| Street (2) |Street 2 field regular expression.
@@ -54,29 +52,29 @@ How to add an address to the alert list:
| Billing Address |Check-box that specifies that the alert will only match a billing address if checked.
| Mailing Address |Check-box that specifies that the alert will only match a mailing address if checked.
| Match All Fields |Check-box that controls if all the fields need to match to trigger the alert(checked), or only at least one field needs to match(unchecked).
-| Active |Check-box that controls if the alert is active or not. Inactive alerts are not processed.
-| Address Alert ID |Displays the internal database id for alert after the alert has been saved. This auto-populates.
+| Active |Check-box that controls if the alert is active or not. Inactive alerts are not processed.
+| Address Alert ID |Displays the internal database id for alert after the alert has been saved. This auto-populates.
|===
+
-. Click save once you have finished.
+. Click *Save* once you have finished.
== Editing an Address Alert ==
-To make changes to an existing alert, double click on the alert in the list. The editing form will appear, make your changes and click save or cancel when you are done.
+To make changes to an existing alert, double click on the alert in the list. The editing form will appear. Make your changes and click *Save* (or *Cancel* to exit the form and cancel the action) when you are done.
-If you don't see your alerts, make sure the *"Context Org Unit"* selection box has the correct Org Unit selected.
+If you don't see your alerts, make sure the organizational unit in the context box has the correct organizational unit selected.
image::lsa_address_alert/edit_address_alert.jpg[Editing an Address Alert]
== Deleting an Address Alert ==
-To delete an alert or many alerts, click the selection check-box for all alerts you would like to delete. Then click the "Delete Selected" button at the top of the screen.
+To delete an alert or many alerts, click the selection checkbox for all alerts you would like to delete. Then click the *Delete Selected* button at the top of the screen.
image::lsa_address_alert/delete_address_alert.jpg[Delete Address Alert]
== Staff View of Address Alerts ==
-When an Address Alert is triggered by a matching address the staff will see the address block highlighted with a red dashed line, along with an *"Address Alert"* block which contains the alert message.
+When an Address Alert is triggered by a matching address, staff will see the address block highlighted with a red dashed line, along with an *Address Alert* block which contains the alert message.
Here is an example of what staff would see.
@@ -88,7 +86,7 @@ All of the patterns entered to match the various address fields are evaluated as
[NOTE]
==========
-Address Alerts use POSIX Regular Expressions included in the PostgreSQL database engine. See the PostgreSQL documentation for full details.
+Address Alerts use POSIX Regular Expressions included in the PostgreSQL database engine. See the PostgreSQL documentation for full details.
==========
If you want to do a case-sensitive match you need to prepend the pattern with "(?c)"
@@ -100,17 +98,17 @@ The simplest regular expression that acts as a wildcard is ".*", that matches an
.Apartment address
Match an apartment address to prompt for unit number.
-. Choose *Owner* Org Unit.
+. Choose *Owner* organizational unit
. Active = Checked
. Match All Fields = Checked
-. Alert Message = "This is a large apartment building, Please ask customer for unit number."
+. Alert Message = "This is a large apartment building. Please ask customer for unit number."
. Street (1) = "1212 Evergreen Lane.*"
. City = "mytown"
.All addresses on street
-Match all addresses on a certain street. Matches ave and avenue because of ending wildcard.
+Match all addresses on a certain street. Matches ave and avenue because of ending wildcard.
-. Choose *Owner* Org Unit.
+. Choose *Owner* organizational unit
. Active = Checked
. Match All Fields = Checked
. Alert Message = "This street is in a different county, please setup reciprocal card."
@@ -118,9 +116,9 @@ Match all addresses on a certain street. Matches ave and avenue because of endi
. City = "mytown"
.Match list of cities
-Match several different cities with one alert. Could be used if certain cities don't have reciprocal agreements. Note the use of parentheses and the | character to separate the different options.
+Match several different cities with one alert. Could be used if certain cities don't have reciprocal agreements. Note the use of parentheses and the | character to separate the different options.
-. Choose *Owner* Org Unit.
+. Choose *Owner* organizational unit
. Active = Checked
. Match All Fields = Checked
. Alert Message = "Customer must purchase a Fee card."
commit c615bf4ae369da464a70a0ccd053d29c7bcd4242
Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com>
Date: Thu Jul 3 15:54:53 2025 -0400
Docs: Updated "org unit" terminology in circulation_limit_groups.adoc
Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com>
diff --git a/docs/modules/admin/pages/circulation_limit_groups.adoc b/docs/modules/admin/pages/circulation_limit_groups.adoc
index 8e6d359204..c5eb56c4ec 100644
--- a/docs/modules/admin/pages/circulation_limit_groups.adoc
+++ b/docs/modules/admin/pages/circulation_limit_groups.adoc
@@ -14,15 +14,15 @@ To limit checkouts by shelving location:
. Click *Administration -> Local Administration -> Circulation Limit Sets*.
. Click *New Circulation Limit Set* to create a new circulation limit set.
. Enter a brief *Description* of the circulation limit set.
-. Check the box adjacent to *Global Flag* if you want all of the org units in
+. Check the box adjacent to *Global Flag* if you want all of the organizational units in
your consortium to be restricted by this limit set when it is applied to a
circulation policy. Otherwise, Evergreen will only apply the limit to the direct
ancestors and descendants of the owning library.
. *ID* will autopopulate after saving.
. Enter the number of *Items Out* that a user can take from this shelving location.
-. Enter the *Min Depth*, or the minimum depth in the org tree that Evergreen
+. Enter the *Min Depth*, or the minimum depth in the organizational unit tree that Evergreen
will consider as valid circulation libraries for counting items out. The min
-depth is based on org unit type depths. For example, if you want the items in
+depth is based on organizational unit type depths. For example, if you want the items in
all of the circulating libraries in your consortium to be eligible for
restriction by this limit set when it is applied to a circulation policy, then
enter a zero (0) in this field.
commit ae7580767555f145d9430b0a953a12e4a1628daf
Author: Jennifer Pringle <jennifer.pringle(a)bc.libraries.coop>
Date: Thu Jul 3 12:50:58 2025 -0700
Docs: Update "org unit" acquisitions_admin.adoc
Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com>
diff --git a/docs/modules/admin/pages/acquisitions_admin.adoc b/docs/modules/admin/pages/acquisitions_admin.adoc
index c8cba0c79a..3f37f93b92 100644
--- a/docs/modules/admin/pages/acquisitions_admin.adoc
+++ b/docs/modules/admin/pages/acquisitions_admin.adoc
@@ -99,7 +99,7 @@ image::acq_funds/claiming1.PNG[Claiming]
[[acq_claim_policy]]
=== Create a claim policy ===
-To create a claim policy, go to _Administration -> Acquisitions Administration>Claiming_. The first tab in this interface is labeled _Claim Policies_. Claim Policies enables you to name the claim policy and specify the organization that owns it.
+To create a claim policy, go to _Administration -> Acquisitions Administration -> Claiming_. The first tab in this interface is labeled _Claim Policies_. Claim Policies enables you to name the claim policy and specify the organization that owns it.
. To create a claim policy, click _New Claim Policy_.
@@ -107,7 +107,7 @@ To create a claim policy, go to _Administration -> Acquisitions Administration>C
. Enter a claim policy Description. No limits exist on the number of characters that can be entered in this field. Example: Materials overdue by 30 days.
-. Select an Org Unit from the drop-down menu. The org unit indicates the organizational units whose staff can use this claim policy. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
+. Select an Owner from the drop-down menu. The Owner indicates the organizational units whose staff can use this claim policy. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
[NOTE] The rule of parental inheritance applies to this list.
@@ -124,7 +124,7 @@ The claim type link enables you to specify the reason for a type of claim.
. Enter a Code and a Description. No limits exist on the number of characters that can be entered in these fields. Example: Past due, Damaged, Wrong Item, etc.
-. Select an Org Unit from the drop-down menu. The org unit indicates the organizational units whose staff can use this claim type. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
+. Select an Owner from the drop-down menu. The Owner indicates the organizational units whose staff can use this claim type. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
[NOTE] The rule of parental inheritance applies to this list.
@@ -145,7 +145,7 @@ The claim event type describes the physical action that should occur when an ite
[NOTE] Currently, all claims are initiated by a user. The ILS cannot automatically claim an issue.
-. Select an Org Unit from the drop-down menu. The org unit indicates the organizational units whose staff can use this event type. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
+. Select an Owner from the drop-down menu. The Owner indicates the organizational units whose staff can use this event type. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
[NOTE] The rule of parental inheritance applies to this list.
@@ -239,7 +239,7 @@ needed.
. Enter a Formula Name. No limits exist on the number of characters that can be entered in this field.
-. Choose a Formula Owner from the drop-down menu. The Formula Owner indicates the organizational units whose staff can use this formula. TThe drop-down menu is controlled by permissions and you will see a list of org units that your user account has permission to create distribution formulas for.
+. Choose a Formula Owner from the drop-down menu. The Formula Owner indicates the organizational units whose staff can use this formula. The drop-down menu is controlled by permissions and you will see a list of organizational units that your user account has permission to create distribution formulas for.
.
[NOTE] The rule of parental inheritance applies to this list.
@@ -528,7 +528,7 @@ If your library does not wish to track fund accounting, you can create one large
In the funds interface, you can create funds; allocate credits from funding sources to funds; transfer money between funds; and apply fund tags to funds.
-Funds are created for a specific year, either fiscal or calendar, and are owned by an org unit or library. At the top of the funds interface, you can set a contextual org unit or library to view the associated funds. Within the grid display of funds you can filter by year to view the funds for a specific year only.
+Funds are created for a specific year, either fiscal or calendar, and are owned by an organizational unit or library. At the top of the funds interface, you can set a contextual organizational unit or library to view the associated funds. Within the grid display of funds you can filter by year to view the funds for a specific year only.
The Funds tab will give you a general overview of the configuration and status of your funds.
@@ -541,7 +541,7 @@ To create a new Fund:
. Enter a Name for the fund. No limits exist on the number of characters that can be entered in this field.
. Create a Code for the fund. No limits exist on the number of characters that can be entered in this field.
. Enter a Year for the fund. This can be a fiscal year or a calendar year. The format of the year is YYYY. The year entry is restricted to a range of 10 years before through 10 years after the current year.
-. Select an Org Unit from the drop-down menu. The org unit indicates the organizational units whose staff can use this fund. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
+. Select an Owner from the drop-down menu. The owner indicates the organizational units whose staff can use this fund. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
. Check the Active box to make this an active fund. You cannot make purchases from this fund if it is not active.
. Select a Currency Type from the drop-down menu. This menu consists of entries Currencies and Exchange Rates interface. When a fund is applied to a line item or copy, the price of the item will be encumbered in the currency associated with the fund.
. Check the Propagate box if you want to propagate funds during fiscal year close out procedures.
@@ -612,16 +612,16 @@ To perform the year end closeout of funds:
. Go to _Administration -> Acquisitions Administration -> Fund Administration_.
. Review your current funds.
-.. Confirm that the correct Org Unit is selected.
+.. Confirm that the correct organizational unit is selected.
.. Double check the Year Filter. It defaults to the current year, so you may need to switch back to a previous year to view funds that have not been rolled over yet. If the list is blank, check this.
.. Double check that the correct funds have Propagate and Rollover set.
. Click _Fiscal Propagation and Rollover_.
. Verify the Context Org Unit for the close out operation.
. Select the Year that you want to close out.
-. Include funds from descendant Org Units: check this box if you want to include funds owned by descendant org units of the Context Org Unit.
+. Include funds from descendant Org Units: check this box if you want to include funds owned by descendant organizational units of the Context Org Unit.
. Fund Propagation: This will happen automatically when _Process_ is clicked, if the Fund’s Propagate setting is enabled.
. Perform Fiscal Year Close-Out: check this box to move encumbrances and unspent funds to the analogous fund for the next fiscal year. It will also deactivate funds for the selected fiscal year. Evergreen will only move encumbrances and unspent funds if the Rollover setting is enabled for a fund.
-.. Limit Fiscal Year Close-Out to Encumbrances: check this box if only encumbered funds should be moved to the analogous fund for the next fiscal year. Unspent funds will not be carried forward to the next fiscal year. This setting will only display if the ‘Allow funds to be rolled over without bringing the money along’ Library Setting has been enabled. This setting is available in the Library Setting Editor accessible via Administration -> Local Administration -> Library Settings Editor.
+.. Limit Fiscal Year Close-Out to Encumbrances: check this box if only encumbered funds should be moved to the analogous fund for the next fiscal year. Unspent funds will not be carried forward to the next fiscal year. This setting will only display if the ‘Allow funds to be rolled over without bringing the money along’ library setting has been enabled. This setting is available in the Library Setting Editor accessible via Administration -> Local Administration -> Library Settings Editor.
. Dry Run: check this box if you want to test changes to the funds before they are enacted. Evergreen will generate a summary of the changes that would occur during the selected operations. No data will be changed.
. Click _Process_.
. Evergreen will begin the propagation process. Evergreen will make a clone of each fund, but it will increment the year by 1.
@@ -786,7 +786,7 @@ To create a new Provider Account, follow one of the paths listed above to retrie
.. _Default Claim Policy_: assign a default claim policy to be applied to purchase orders created with this provider. Claim policies are set up in Acquisitions Administration. (optional)
.. _Default # Copies_: assign a default number of copies to be automatically created for each line item in purchase orders created with this provider. (optional)
.. _EDI Default_: assign the EDI Account to be used on purchase orders created with this provider. EDI Accounts can be set up from within the Provider record or from Acquisitions Administration->EDI Accounts. (optional)
-.. _Owner_: assign the org unit that will use this provider account. This field will default to the org unit of the workstation you are logged in at. (required)
+.. _Owner_: assign the organizational unit that will use this provider account. This field will default to the organizational unit of the workstation you are logged in at. (required)
.. _URL_: add a URL associated with the provider (optional). URLs must include the prefix, such as http:// or https:// in order to link correctly.
.. _SAN_: assign the provider’s SAN. (required if using EDI ordering)
.. _Prepayment Required_: indicate if prepayment is required for orders with this provider. (optional)
@@ -877,4 +877,4 @@ As part of transitioning the General Search interface to Angular, several change
.. Prepayment Required
. Column headers for the search results can be clicked on to sort the results by the column. The columns will sort alphabetically or by date as appropriate for the data type.
. Using the column actions to filter or sort search results will execute a new search using the original search parameters. If any un-executed changes are made to the search parameters between the initial search submission and any changes to the filters, the new search parameters will be executed upon filtering.
-. Dropdown menus for the search fields will retrieve a maximum of 100 rows at a time.
\ No newline at end of file
+. Dropdown menus for the search fields will retrieve a maximum of 100 rows at a time.
commit 147f2017ec69aa916b475286d739d68145119187
Author: Jennifer Pringle <jennifer.pringle(a)bc.libraries.coop>
Date: Thu Jul 3 12:37:40 2025 -0700
Docs: Update "org unit" in copy_locations.adoc
Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com>
diff --git a/docs/modules/admin/pages/copy_locations.adoc b/docs/modules/admin/pages/copy_locations.adoc
index 92caa3288b..19260fe821 100644
--- a/docs/modules/admin/pages/copy_locations.adoc
+++ b/docs/modules/admin/pages/copy_locations.adoc
@@ -22,7 +22,7 @@ To add a shelving location
image::shelving_location/shelving_location_new.png[New shelving location]
+
. Select your parameters for your shelving locations.
-.. Choose the owning Org Unit of the shelving location.
+.. Choose the Owning Org Unit of the shelving location.
.. Type the name of the shelving location in the name field.
.. _Is OPAC Visible?_, choose whether you would like items in this shelving location to appear in the catalog.
.. _Can Circulate?_ can items in this location circulate?
@@ -74,7 +74,7 @@ Evergreen preserves shelving locations in the database, so no statistical inform
== Modifying shelving location order ==
-By default Evergreen displays shelving locations in alphabetical order. This order can be modified per Org Unit.
+By default Evergreen displays shelving locations in alphabetical order. This order can be modified per organizational unit.
To modify the order of shelving locations, Go to *Administration -> Local Administration -> Shelving Location Order*
@@ -82,9 +82,9 @@ image::shelving_location/shelving_location_order.png[Shelving Location Order]
To change the order:
-. Choose the Org Unit you are wanting to reorder.
+. Choose the organizational unit you are wanting to reorder.
. Drag and drop the locations until you are satisfied with their order.
-. Click _Apply changes_.
+. Click _Save changes_.
== Shelving location groups ==
@@ -94,7 +94,7 @@ To change the order:
Mayberry Public Library provides a scope allowing users to search for all children's materials in their library. The library's children's scope incorporates several shelving locations used at the library, including picture Books, Children's Fiction, Children's Non-Fiction, Easy Readers, and Children's DVDs. The library also builds a similar scope for YA materials that incorporates several shelving locations.
****
-This feature allows staff to create and name sets of shelving locations to use as a search filter in the catalog. OPAC-visible groups will display within the library selector in the [.underline]#Public Catalog#. When a user selects a group and performs a search, the set of results will be limited to records that have items in one of the shelving locations within the group. Groups can live at any level of the library hierarchy and may include shelving locations from any parent org unit or child org unit.
+This feature allows staff to create and name sets of shelving locations to use as a search filter in the catalog. OPAC-visible groups will display within the library selector in the [.underline]#Public Catalog#. When a user selects a group and performs a search, the set of results will be limited to records that have items in one of the shelving locations within the group. Groups can live at any level of the library hierarchy and may include shelving locations from any parent organizational unit or child organizational unit.
NOTE: To work with shelving location groups, you will need the ADMIN_COPY_LOCATION_GROUP permission.
@@ -103,22 +103,22 @@ image::shelving_location/shelving_location_groups_editor.png[Shelving Location G
=== Create a shelving location group ===
. Click *Administration -> Local Administration -> Shelving Location Groups*.
-. At the top of the screen is a menu that displays the org unit tree. Select the unit within the org tree to which you want to add a shelving location group. The shelving locations associated with the org unit appear in the shelving locations column.
+. The library selector at the screen defaults to the highlest level organizational unit. Select the organizational unit to which you want to add a shelving location group; the associated shelving locations will appear in the shelving locations column.
. Click _New Location Group_.
+
image::shelving_location/new_shelving_location_group.png[New Shelving Location Group]
+
-. Choose how you want the shelving location group to display to patrons in the catalog's org unit tree in the OPAC. By default, when you add a new shelving location group, the group displays in the org unit tree beneath any branches or sub-libraries of its parental org unit. If you select _Yes_ for _Display Above Orgs_, then the group will appear above the branches or sub-libraries of its parental org unit.
+. Choose how you want the shelving location group to display to patrons in the catalog's organizational unit tree in the OPAC. By default, when you add a new shelving location group, the group displays in the organizational unit tree beneath any branches or sub-libraries of its parental organizational unit. If you select _Yes_ for _Display Above Orgs_, then the group will appear above the branches or sub-libraries of its parental organizational unit.
. To make the shelving location group visible to users searching the public catalog, select _Yes_ for _Is OPAC Visible?_
. _Position_ will order the display of the shelving location group. This takes integers with 0 being first.
. Enter a _Name_ for the shelving location group.
. Click Save. The name of the shelving location group appears in the location groups.
-. Select the shelving locations that you want to add to the group, and click Add. The shelving locations will populate the middle column, Group Entries.
-. The shelving location group is now visible in the org unit tree in the catalog. Search the catalog to retrieve results from any of the shelving locations that you added to the shelving location group.
+. Select the shelving locations that you want to add to the group, and click _Add to group_. The shelving locations will populate the middle column, Shelving Locations in Group.
+. The shelving location group is now visible in the organizational unit tree in the catalog. Search the catalog to retrieve results from any of the shelving locations that you added to the shelving location group.
=== Order shelving location groups ===
-If you create more than one shelving location group, then you can order the groups in the org unit tree.
+If you create more than one shelving location group, then you can order the groups in the organizational unit tree.
image::shelving_location/sl_groups_example.png[Shelving Location Group Display Example]
-----------------------------------------------------------------------
Summary of changes:
docs/modules/admin/pages/acquisitions_admin.adoc | 24 +++++-----
.../admin/pages/circulation_limit_groups.adoc | 6 +--
docs/modules/admin/pages/copy_locations.adoc | 20 ++++-----
docs/modules/admin/pages/lsa-address_alert.adoc | 52 +++++++++++-----------
4 files changed, 50 insertions(+), 52 deletions(-)
hooks/post-receive
--
Evergreen ILS
1
0
[GIT] Evergreen ILS branch main updated. 8839b4645d92496dd08ed09530c911d353589741
by Git User 10 Jul '25
by Git User 10 Jul '25
10 Jul '25
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, main has been updated
via 8839b4645d92496dd08ed09530c911d353589741 (commit)
via b77b1de16e16d20e90d558370a280faa93a801f0 (commit)
via a67f5653e7719f57ab974c8396d383094514d02b (commit)
via 65cc8d234562b0ed8c1a8baf87f6a5536f460d82 (commit)
via ceae31712d416e845a23c13dc9c8069e4543bba6 (commit)
via 5329b0e83f4efaf469f310234179253b565a55ea (commit)
from 371b82bb76b08d5dad7f1c517c899e37a71f0b66 (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 8839b4645d92496dd08ed09530c911d353589741
Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com>
Date: Thu Jul 3 16:34:34 2025 -0400
Docs: Updates to "org unit" terminology in data_unapi.adoc
Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com>
diff --git a/docs/modules/development/pages/data_unapi.adoc b/docs/modules/development/pages/data_unapi.adoc
index 5d6fcb18b4..10a32f7c6e 100644
--- a/docs/modules/development/pages/data_unapi.adoc
+++ b/docs/modules/development/pages/data_unapi.adoc
@@ -22,7 +22,7 @@ following form:
** +acns+ (call number suffixes)
** +acp+ (items)
** +acpn+ (item notes)
- ** +aou+ (org units)
+ ** +aou+ (organizational units)
** +ascecm+ (item stat cat entries)
** +auri+ (located URIs)
** +bmp+ (monographic parts)
@@ -49,13 +49,13 @@ following form:
by commas)
* followed, optionally, by limit and offset in square brackets
* followed, optionally, by a comma-separated list of "includes"
- enclosed in curly brackets. The list of includes is
+ enclosed in curly brackets. The list of includes is
the same as the list of classes with the following addition:
** +bre.extern+ (information from the non-MARC parts of a bib
record)
- * followed, optionally, by +/+ and org unit; "-" signifies
- the top of the org unit tree
- * followed, optionally, by +/+ and org unit depth
+ * followed, optionally, by +/+ and organizational unit; "-" signifies
+ the top of the organizational unit tree
+ * followed, optionally, by +/+ and organizational unit depth
* followed, optionally, by +/+ and a path. If the path
is +barcode+ and the class is +acp+, the record ID is taken
to be an item barcode rather than an item ID; for example, in
commit b77b1de16e16d20e90d558370a280faa93a801f0
Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com>
Date: Thu Jul 3 16:30:50 2025 -0400
Docs: Update to "org unit" terminology in nav.adoc
Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com>
diff --git a/docs/modules/admin_initial_setup/nav.adoc b/docs/modules/admin_initial_setup/nav.adoc
index 7c535ee882..f7ed92f632 100644
--- a/docs/modules/admin_initial_setup/nav.adoc
+++ b/docs/modules/admin_initial_setup/nav.adoc
@@ -13,7 +13,7 @@
*** xref:opac:new_skin_customizations.adoc[Creating a New Skin: the Bare Minimum]
*** xref:admin_initial_setup:carousels.adoc[OPAC Carousels]
*** xref:admin_initial_setup:managing_holds_ui_in_tpac.adoc[Managing how holds options display in the catalog]
-*** xref:admin_initial_setup:custom_ou_trees.adoc[Custom Org Unit Trees]
+*** xref:admin_initial_setup:custom_ou_trees.adoc[Custom Organizational Unit Trees]
** xref:admin_initial_setup:KidsOPAC.adoc[Kid's OPAC Configuration]
** xref:admin_initial_setup:bootstrap_opac.adoc[Bootstrap OPAC]
** xref:admin:search_interface.adoc[Designing the patron search experience]
commit a67f5653e7719f57ab974c8396d383094514d02b
Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com>
Date: Thu Jul 3 16:16:05 2025 -0400
Docs: Updates to "org unit" terminology lsa-address_alert.adoc
Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com>
diff --git a/docs/modules/admin/pages/lsa-address_alert.adoc b/docs/modules/admin/pages/lsa-address_alert.adoc
index d2f264d58e..9f26d48e00 100644
--- a/docs/modules/admin/pages/lsa-address_alert.adoc
+++ b/docs/modules/admin/pages/lsa-address_alert.adoc
@@ -6,43 +6,41 @@ indexterm:[address alerts]
The Address Alert module gives administrators the ability to notify staff with a custom message when
addresses with certain patterns are entered in patron records.
-This feature only serves to provide pertinent information to your library system's circulation staff during the registration process. An alert will not prevent the new patron account from being registered and the information will not be permanently associated with the patron account.
+This feature only serves to provide pertinent information to your library system's circulation staff during the registration process. An alert will not prevent the new patron account from being registered, and the information will not be permanently associated with the patron account.
-To access the Address Alert module, select *Administration* -> *Local Administration* -> *Address Alerts*.
+To access the Address Alert module, select *Administration* -> *Local Administration* -> *Address Alerts*.
[NOTE]
==========
-You must have Local Administrator permissions or ADMIN_ADDRESS_ALERT permission to access the Address Alert module.
+You must have Local Administrator permissions or the ADMIN_ADDRESS_ALERT permission to access the Address Alert module.
==========
== General Usage Examples ==
-- Alert staff when an address for a large apartment is entered to prompt them to ask for unit number.
+- Alert staff when an address for a large apartment is entered to prompt them to ask for a unit number.
- Alert staff when the address of a hotel or other temporary housing is entered.
- Alert staff when an address for a different country is entered.
-- Alert staff when a specific city or zip code is entered if that city or zip code needs to be handled in a special way. If you have a neighboring city that you don't have a reciprocal relationship with, you could notify staff that a fee card is required for this customer.
+- Alert staff when a specific city or zip code is entered if that city or zip code needs to be handled in a special way. If you have a neighboring city that you don't have a reciprocal relationship with, you could notify staff that a fee card is required for this customer.
== Access Control and Scoping ==
-Each address alert is tied to an Org Unit and will only be matched against staff client instances of that Org Unit and its children.
+Each address alert is tied to an organizational unit and will only be matched against staff client instances of that organizational unit and its children.
-When viewing the address alerts you will only see the alerts associated with the specific org unit selected in the *"Context Org Unit"* selection box. You won't see alerts associated with parent org units, so the list of alerts isn't a list of all alerts that may effect your org unit, only of the ones that you can edit.
+When viewing the address alerts, you will only see the alerts associated with the specific organizational unit selected in the context selection box. You won't see alerts associated with parent organizational units, so the list of alerts isn't a list of all alerts that may affect your organizational unit, only of the ones that you can edit.
-The specific permission that controls access to configuring this feature is ADMIN_ADDRESS_ALERT. Local Administrator level users will already have this permission. It is possible for the Local Administrator to grant this permission to other staff.
-
-== Adding a new Address Alert ==
+== Adding a New Address Alert ==
How to add an address to the alert list:
. Log into the Evergreen Staff Client using a Local Administrator account or another account that has been granted the proper permission.
-. Click on Administration -> Local Administration -> Address Alerts.
-. Click "New Address Alert."
+. Click on *Administration* -> *Local Administration* -> *Address Alerts*.
+. Click *New Address Alert*.
. A form will open with the following fields to fill out:
+
.New Address Alert Fields
|===
|*Field* |*Description*
-| Owner |Which Org Unit owns this alert. Set this to your system or branch.
+| Owner |Which organizational unit owns this alert. Set this to your system or branch.
| Alert Message |Message that will be displayed to staff when this alert is triggered.
| Street (1) |Street 1 field regular expression.
| Street (2) |Street 2 field regular expression.
@@ -54,29 +52,29 @@ How to add an address to the alert list:
| Billing Address |Check-box that specifies that the alert will only match a billing address if checked.
| Mailing Address |Check-box that specifies that the alert will only match a mailing address if checked.
| Match All Fields |Check-box that controls if all the fields need to match to trigger the alert(checked), or only at least one field needs to match(unchecked).
-| Active |Check-box that controls if the alert is active or not. Inactive alerts are not processed.
-| Address Alert ID |Displays the internal database id for alert after the alert has been saved. This auto-populates.
+| Active |Check-box that controls if the alert is active or not. Inactive alerts are not processed.
+| Address Alert ID |Displays the internal database id for alert after the alert has been saved. This auto-populates.
|===
+
-. Click save once you have finished.
+. Click *Save* once you have finished.
== Editing an Address Alert ==
-To make changes to an existing alert, double click on the alert in the list. The editing form will appear, make your changes and click save or cancel when you are done.
+To make changes to an existing alert, double click on the alert in the list. The editing form will appear. Make your changes and click *Save* (or *Cancel* to exit the form and cancel the action) when you are done.
-If you don't see your alerts, make sure the *"Context Org Unit"* selection box has the correct Org Unit selected.
+If you don't see your alerts, make sure the organizational unit in the context box has the correct organizational unit selected.
image::lsa_address_alert/edit_address_alert.jpg[Editing an Address Alert]
== Deleting an Address Alert ==
-To delete an alert or many alerts, click the selection check-box for all alerts you would like to delete. Then click the "Delete Selected" button at the top of the screen.
+To delete an alert or many alerts, click the selection checkbox for all alerts you would like to delete. Then click the *Delete Selected* button at the top of the screen.
image::lsa_address_alert/delete_address_alert.jpg[Delete Address Alert]
== Staff View of Address Alerts ==
-When an Address Alert is triggered by a matching address the staff will see the address block highlighted with a red dashed line, along with an *"Address Alert"* block which contains the alert message.
+When an Address Alert is triggered by a matching address, staff will see the address block highlighted with a red dashed line, along with an *Address Alert* block which contains the alert message.
Here is an example of what staff would see.
@@ -88,7 +86,7 @@ All of the patterns entered to match the various address fields are evaluated as
[NOTE]
==========
-Address Alerts use POSIX Regular Expressions included in the PostgreSQL database engine. See the PostgreSQL documentation for full details.
+Address Alerts use POSIX Regular Expressions included in the PostgreSQL database engine. See the PostgreSQL documentation for full details.
==========
If you want to do a case-sensitive match you need to prepend the pattern with "(?c)"
@@ -100,17 +98,17 @@ The simplest regular expression that acts as a wildcard is ".*", that matches an
.Apartment address
Match an apartment address to prompt for unit number.
-. Choose *Owner* Org Unit.
+. Choose *Owner* organizational unit
. Active = Checked
. Match All Fields = Checked
-. Alert Message = "This is a large apartment building, Please ask customer for unit number."
+. Alert Message = "This is a large apartment building. Please ask customer for unit number."
. Street (1) = "1212 Evergreen Lane.*"
. City = "mytown"
.All addresses on street
-Match all addresses on a certain street. Matches ave and avenue because of ending wildcard.
+Match all addresses on a certain street. Matches ave and avenue because of ending wildcard.
-. Choose *Owner* Org Unit.
+. Choose *Owner* organizational unit
. Active = Checked
. Match All Fields = Checked
. Alert Message = "This street is in a different county, please setup reciprocal card."
@@ -118,9 +116,9 @@ Match all addresses on a certain street. Matches ave and avenue because of endi
. City = "mytown"
.Match list of cities
-Match several different cities with one alert. Could be used if certain cities don't have reciprocal agreements. Note the use of parentheses and the | character to separate the different options.
+Match several different cities with one alert. Could be used if certain cities don't have reciprocal agreements. Note the use of parentheses and the | character to separate the different options.
-. Choose *Owner* Org Unit.
+. Choose *Owner* organizational unit
. Active = Checked
. Match All Fields = Checked
. Alert Message = "Customer must purchase a Fee card."
commit 65cc8d234562b0ed8c1a8baf87f6a5536f460d82
Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com>
Date: Thu Jul 3 15:54:53 2025 -0400
Docs: Updated "org unit" terminology in circulation_limit_groups.adoc
Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com>
diff --git a/docs/modules/admin/pages/circulation_limit_groups.adoc b/docs/modules/admin/pages/circulation_limit_groups.adoc
index 8e6d359204..c5eb56c4ec 100644
--- a/docs/modules/admin/pages/circulation_limit_groups.adoc
+++ b/docs/modules/admin/pages/circulation_limit_groups.adoc
@@ -14,15 +14,15 @@ To limit checkouts by shelving location:
. Click *Administration -> Local Administration -> Circulation Limit Sets*.
. Click *New Circulation Limit Set* to create a new circulation limit set.
. Enter a brief *Description* of the circulation limit set.
-. Check the box adjacent to *Global Flag* if you want all of the org units in
+. Check the box adjacent to *Global Flag* if you want all of the organizational units in
your consortium to be restricted by this limit set when it is applied to a
circulation policy. Otherwise, Evergreen will only apply the limit to the direct
ancestors and descendants of the owning library.
. *ID* will autopopulate after saving.
. Enter the number of *Items Out* that a user can take from this shelving location.
-. Enter the *Min Depth*, or the minimum depth in the org tree that Evergreen
+. Enter the *Min Depth*, or the minimum depth in the organizational unit tree that Evergreen
will consider as valid circulation libraries for counting items out. The min
-depth is based on org unit type depths. For example, if you want the items in
+depth is based on organizational unit type depths. For example, if you want the items in
all of the circulating libraries in your consortium to be eligible for
restriction by this limit set when it is applied to a circulation policy, then
enter a zero (0) in this field.
commit ceae31712d416e845a23c13dc9c8069e4543bba6
Author: Jennifer Pringle <jennifer.pringle(a)bc.libraries.coop>
Date: Thu Jul 3 12:50:58 2025 -0700
Docs: Update "org unit" acquisitions_admin.adoc
Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com>
diff --git a/docs/modules/admin/pages/acquisitions_admin.adoc b/docs/modules/admin/pages/acquisitions_admin.adoc
index c8cba0c79a..3f37f93b92 100644
--- a/docs/modules/admin/pages/acquisitions_admin.adoc
+++ b/docs/modules/admin/pages/acquisitions_admin.adoc
@@ -99,7 +99,7 @@ image::acq_funds/claiming1.PNG[Claiming]
[[acq_claim_policy]]
=== Create a claim policy ===
-To create a claim policy, go to _Administration -> Acquisitions Administration>Claiming_. The first tab in this interface is labeled _Claim Policies_. Claim Policies enables you to name the claim policy and specify the organization that owns it.
+To create a claim policy, go to _Administration -> Acquisitions Administration -> Claiming_. The first tab in this interface is labeled _Claim Policies_. Claim Policies enables you to name the claim policy and specify the organization that owns it.
. To create a claim policy, click _New Claim Policy_.
@@ -107,7 +107,7 @@ To create a claim policy, go to _Administration -> Acquisitions Administration>C
. Enter a claim policy Description. No limits exist on the number of characters that can be entered in this field. Example: Materials overdue by 30 days.
-. Select an Org Unit from the drop-down menu. The org unit indicates the organizational units whose staff can use this claim policy. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
+. Select an Owner from the drop-down menu. The Owner indicates the organizational units whose staff can use this claim policy. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
[NOTE] The rule of parental inheritance applies to this list.
@@ -124,7 +124,7 @@ The claim type link enables you to specify the reason for a type of claim.
. Enter a Code and a Description. No limits exist on the number of characters that can be entered in these fields. Example: Past due, Damaged, Wrong Item, etc.
-. Select an Org Unit from the drop-down menu. The org unit indicates the organizational units whose staff can use this claim type. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
+. Select an Owner from the drop-down menu. The Owner indicates the organizational units whose staff can use this claim type. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
[NOTE] The rule of parental inheritance applies to this list.
@@ -145,7 +145,7 @@ The claim event type describes the physical action that should occur when an ite
[NOTE] Currently, all claims are initiated by a user. The ILS cannot automatically claim an issue.
-. Select an Org Unit from the drop-down menu. The org unit indicates the organizational units whose staff can use this event type. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
+. Select an Owner from the drop-down menu. The Owner indicates the organizational units whose staff can use this event type. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
[NOTE] The rule of parental inheritance applies to this list.
@@ -239,7 +239,7 @@ needed.
. Enter a Formula Name. No limits exist on the number of characters that can be entered in this field.
-. Choose a Formula Owner from the drop-down menu. The Formula Owner indicates the organizational units whose staff can use this formula. TThe drop-down menu is controlled by permissions and you will see a list of org units that your user account has permission to create distribution formulas for.
+. Choose a Formula Owner from the drop-down menu. The Formula Owner indicates the organizational units whose staff can use this formula. The drop-down menu is controlled by permissions and you will see a list of organizational units that your user account has permission to create distribution formulas for.
.
[NOTE] The rule of parental inheritance applies to this list.
@@ -528,7 +528,7 @@ If your library does not wish to track fund accounting, you can create one large
In the funds interface, you can create funds; allocate credits from funding sources to funds; transfer money between funds; and apply fund tags to funds.
-Funds are created for a specific year, either fiscal or calendar, and are owned by an org unit or library. At the top of the funds interface, you can set a contextual org unit or library to view the associated funds. Within the grid display of funds you can filter by year to view the funds for a specific year only.
+Funds are created for a specific year, either fiscal or calendar, and are owned by an organizational unit or library. At the top of the funds interface, you can set a contextual organizational unit or library to view the associated funds. Within the grid display of funds you can filter by year to view the funds for a specific year only.
The Funds tab will give you a general overview of the configuration and status of your funds.
@@ -541,7 +541,7 @@ To create a new Fund:
. Enter a Name for the fund. No limits exist on the number of characters that can be entered in this field.
. Create a Code for the fund. No limits exist on the number of characters that can be entered in this field.
. Enter a Year for the fund. This can be a fiscal year or a calendar year. The format of the year is YYYY. The year entry is restricted to a range of 10 years before through 10 years after the current year.
-. Select an Org Unit from the drop-down menu. The org unit indicates the organizational units whose staff can use this fund. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
+. Select an Owner from the drop-down menu. The owner indicates the organizational units whose staff can use this fund. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
. Check the Active box to make this an active fund. You cannot make purchases from this fund if it is not active.
. Select a Currency Type from the drop-down menu. This menu consists of entries Currencies and Exchange Rates interface. When a fund is applied to a line item or copy, the price of the item will be encumbered in the currency associated with the fund.
. Check the Propagate box if you want to propagate funds during fiscal year close out procedures.
@@ -612,16 +612,16 @@ To perform the year end closeout of funds:
. Go to _Administration -> Acquisitions Administration -> Fund Administration_.
. Review your current funds.
-.. Confirm that the correct Org Unit is selected.
+.. Confirm that the correct organizational unit is selected.
.. Double check the Year Filter. It defaults to the current year, so you may need to switch back to a previous year to view funds that have not been rolled over yet. If the list is blank, check this.
.. Double check that the correct funds have Propagate and Rollover set.
. Click _Fiscal Propagation and Rollover_.
. Verify the Context Org Unit for the close out operation.
. Select the Year that you want to close out.
-. Include funds from descendant Org Units: check this box if you want to include funds owned by descendant org units of the Context Org Unit.
+. Include funds from descendant Org Units: check this box if you want to include funds owned by descendant organizational units of the Context Org Unit.
. Fund Propagation: This will happen automatically when _Process_ is clicked, if the Fund’s Propagate setting is enabled.
. Perform Fiscal Year Close-Out: check this box to move encumbrances and unspent funds to the analogous fund for the next fiscal year. It will also deactivate funds for the selected fiscal year. Evergreen will only move encumbrances and unspent funds if the Rollover setting is enabled for a fund.
-.. Limit Fiscal Year Close-Out to Encumbrances: check this box if only encumbered funds should be moved to the analogous fund for the next fiscal year. Unspent funds will not be carried forward to the next fiscal year. This setting will only display if the ‘Allow funds to be rolled over without bringing the money along’ Library Setting has been enabled. This setting is available in the Library Setting Editor accessible via Administration -> Local Administration -> Library Settings Editor.
+.. Limit Fiscal Year Close-Out to Encumbrances: check this box if only encumbered funds should be moved to the analogous fund for the next fiscal year. Unspent funds will not be carried forward to the next fiscal year. This setting will only display if the ‘Allow funds to be rolled over without bringing the money along’ library setting has been enabled. This setting is available in the Library Setting Editor accessible via Administration -> Local Administration -> Library Settings Editor.
. Dry Run: check this box if you want to test changes to the funds before they are enacted. Evergreen will generate a summary of the changes that would occur during the selected operations. No data will be changed.
. Click _Process_.
. Evergreen will begin the propagation process. Evergreen will make a clone of each fund, but it will increment the year by 1.
@@ -786,7 +786,7 @@ To create a new Provider Account, follow one of the paths listed above to retrie
.. _Default Claim Policy_: assign a default claim policy to be applied to purchase orders created with this provider. Claim policies are set up in Acquisitions Administration. (optional)
.. _Default # Copies_: assign a default number of copies to be automatically created for each line item in purchase orders created with this provider. (optional)
.. _EDI Default_: assign the EDI Account to be used on purchase orders created with this provider. EDI Accounts can be set up from within the Provider record or from Acquisitions Administration->EDI Accounts. (optional)
-.. _Owner_: assign the org unit that will use this provider account. This field will default to the org unit of the workstation you are logged in at. (required)
+.. _Owner_: assign the organizational unit that will use this provider account. This field will default to the organizational unit of the workstation you are logged in at. (required)
.. _URL_: add a URL associated with the provider (optional). URLs must include the prefix, such as http:// or https:// in order to link correctly.
.. _SAN_: assign the provider’s SAN. (required if using EDI ordering)
.. _Prepayment Required_: indicate if prepayment is required for orders with this provider. (optional)
@@ -877,4 +877,4 @@ As part of transitioning the General Search interface to Angular, several change
.. Prepayment Required
. Column headers for the search results can be clicked on to sort the results by the column. The columns will sort alphabetically or by date as appropriate for the data type.
. Using the column actions to filter or sort search results will execute a new search using the original search parameters. If any un-executed changes are made to the search parameters between the initial search submission and any changes to the filters, the new search parameters will be executed upon filtering.
-. Dropdown menus for the search fields will retrieve a maximum of 100 rows at a time.
\ No newline at end of file
+. Dropdown menus for the search fields will retrieve a maximum of 100 rows at a time.
commit 5329b0e83f4efaf469f310234179253b565a55ea
Author: Jennifer Pringle <jennifer.pringle(a)bc.libraries.coop>
Date: Thu Jul 3 12:37:40 2025 -0700
Docs: Update "org unit" in copy_locations.adoc
Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com>
diff --git a/docs/modules/admin/pages/copy_locations.adoc b/docs/modules/admin/pages/copy_locations.adoc
index 92caa3288b..19260fe821 100644
--- a/docs/modules/admin/pages/copy_locations.adoc
+++ b/docs/modules/admin/pages/copy_locations.adoc
@@ -22,7 +22,7 @@ To add a shelving location
image::shelving_location/shelving_location_new.png[New shelving location]
+
. Select your parameters for your shelving locations.
-.. Choose the owning Org Unit of the shelving location.
+.. Choose the Owning Org Unit of the shelving location.
.. Type the name of the shelving location in the name field.
.. _Is OPAC Visible?_, choose whether you would like items in this shelving location to appear in the catalog.
.. _Can Circulate?_ can items in this location circulate?
@@ -74,7 +74,7 @@ Evergreen preserves shelving locations in the database, so no statistical inform
== Modifying shelving location order ==
-By default Evergreen displays shelving locations in alphabetical order. This order can be modified per Org Unit.
+By default Evergreen displays shelving locations in alphabetical order. This order can be modified per organizational unit.
To modify the order of shelving locations, Go to *Administration -> Local Administration -> Shelving Location Order*
@@ -82,9 +82,9 @@ image::shelving_location/shelving_location_order.png[Shelving Location Order]
To change the order:
-. Choose the Org Unit you are wanting to reorder.
+. Choose the organizational unit you are wanting to reorder.
. Drag and drop the locations until you are satisfied with their order.
-. Click _Apply changes_.
+. Click _Save changes_.
== Shelving location groups ==
@@ -94,7 +94,7 @@ To change the order:
Mayberry Public Library provides a scope allowing users to search for all children's materials in their library. The library's children's scope incorporates several shelving locations used at the library, including picture Books, Children's Fiction, Children's Non-Fiction, Easy Readers, and Children's DVDs. The library also builds a similar scope for YA materials that incorporates several shelving locations.
****
-This feature allows staff to create and name sets of shelving locations to use as a search filter in the catalog. OPAC-visible groups will display within the library selector in the [.underline]#Public Catalog#. When a user selects a group and performs a search, the set of results will be limited to records that have items in one of the shelving locations within the group. Groups can live at any level of the library hierarchy and may include shelving locations from any parent org unit or child org unit.
+This feature allows staff to create and name sets of shelving locations to use as a search filter in the catalog. OPAC-visible groups will display within the library selector in the [.underline]#Public Catalog#. When a user selects a group and performs a search, the set of results will be limited to records that have items in one of the shelving locations within the group. Groups can live at any level of the library hierarchy and may include shelving locations from any parent organizational unit or child organizational unit.
NOTE: To work with shelving location groups, you will need the ADMIN_COPY_LOCATION_GROUP permission.
@@ -103,22 +103,22 @@ image::shelving_location/shelving_location_groups_editor.png[Shelving Location G
=== Create a shelving location group ===
. Click *Administration -> Local Administration -> Shelving Location Groups*.
-. At the top of the screen is a menu that displays the org unit tree. Select the unit within the org tree to which you want to add a shelving location group. The shelving locations associated with the org unit appear in the shelving locations column.
+. The library selector at the screen defaults to the highlest level organizational unit. Select the organizational unit to which you want to add a shelving location group; the associated shelving locations will appear in the shelving locations column.
. Click _New Location Group_.
+
image::shelving_location/new_shelving_location_group.png[New Shelving Location Group]
+
-. Choose how you want the shelving location group to display to patrons in the catalog's org unit tree in the OPAC. By default, when you add a new shelving location group, the group displays in the org unit tree beneath any branches or sub-libraries of its parental org unit. If you select _Yes_ for _Display Above Orgs_, then the group will appear above the branches or sub-libraries of its parental org unit.
+. Choose how you want the shelving location group to display to patrons in the catalog's organizational unit tree in the OPAC. By default, when you add a new shelving location group, the group displays in the organizational unit tree beneath any branches or sub-libraries of its parental organizational unit. If you select _Yes_ for _Display Above Orgs_, then the group will appear above the branches or sub-libraries of its parental organizational unit.
. To make the shelving location group visible to users searching the public catalog, select _Yes_ for _Is OPAC Visible?_
. _Position_ will order the display of the shelving location group. This takes integers with 0 being first.
. Enter a _Name_ for the shelving location group.
. Click Save. The name of the shelving location group appears in the location groups.
-. Select the shelving locations that you want to add to the group, and click Add. The shelving locations will populate the middle column, Group Entries.
-. The shelving location group is now visible in the org unit tree in the catalog. Search the catalog to retrieve results from any of the shelving locations that you added to the shelving location group.
+. Select the shelving locations that you want to add to the group, and click _Add to group_. The shelving locations will populate the middle column, Shelving Locations in Group.
+. The shelving location group is now visible in the organizational unit tree in the catalog. Search the catalog to retrieve results from any of the shelving locations that you added to the shelving location group.
=== Order shelving location groups ===
-If you create more than one shelving location group, then you can order the groups in the org unit tree.
+If you create more than one shelving location group, then you can order the groups in the organizational unit tree.
image::shelving_location/sl_groups_example.png[Shelving Location Group Display Example]
-----------------------------------------------------------------------
Summary of changes:
docs/modules/admin/pages/acquisitions_admin.adoc | 24 +++++-----
.../admin/pages/circulation_limit_groups.adoc | 6 +--
docs/modules/admin/pages/copy_locations.adoc | 20 ++++-----
docs/modules/admin/pages/lsa-address_alert.adoc | 52 +++++++++++-----------
docs/modules/admin_initial_setup/nav.adoc | 2 +-
docs/modules/development/pages/data_unapi.adoc | 10 ++---
6 files changed, 56 insertions(+), 58 deletions(-)
hooks/post-receive
--
Evergreen ILS
1
0
[GIT] Evergreen ILS branch rel_3_15 updated. 75c064a80b6df3b16fdc283b9819375e6a6ec04b
by Git User 10 Jul '25
by Git User 10 Jul '25
10 Jul '25
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_3_15 has been updated
via 75c064a80b6df3b16fdc283b9819375e6a6ec04b (commit)
via 9ee8a37c753dc2fe64dd57b71b38e2148795a228 (commit)
via c9a905c3e8414c44d649cf039ab9fc833f5d61c3 (commit)
via 38095f822d38164ccc1f92af4c17bfc775d5d01c (commit)
from b2348b675a7a9b685ab794881c3f388ee0838ab3 (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 75c064a80b6df3b16fdc283b9819375e6a6ec04b
Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com>
Date: Thu Jul 3 16:16:05 2025 -0400
Docs: Updates to "org unit" terminology lsa-address_alert.adoc
Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com>
diff --git a/docs/modules/admin/pages/lsa-address_alert.adoc b/docs/modules/admin/pages/lsa-address_alert.adoc
index d2f264d58e..9f26d48e00 100644
--- a/docs/modules/admin/pages/lsa-address_alert.adoc
+++ b/docs/modules/admin/pages/lsa-address_alert.adoc
@@ -6,43 +6,41 @@ indexterm:[address alerts]
The Address Alert module gives administrators the ability to notify staff with a custom message when
addresses with certain patterns are entered in patron records.
-This feature only serves to provide pertinent information to your library system's circulation staff during the registration process. An alert will not prevent the new patron account from being registered and the information will not be permanently associated with the patron account.
+This feature only serves to provide pertinent information to your library system's circulation staff during the registration process. An alert will not prevent the new patron account from being registered, and the information will not be permanently associated with the patron account.
-To access the Address Alert module, select *Administration* -> *Local Administration* -> *Address Alerts*.
+To access the Address Alert module, select *Administration* -> *Local Administration* -> *Address Alerts*.
[NOTE]
==========
-You must have Local Administrator permissions or ADMIN_ADDRESS_ALERT permission to access the Address Alert module.
+You must have Local Administrator permissions or the ADMIN_ADDRESS_ALERT permission to access the Address Alert module.
==========
== General Usage Examples ==
-- Alert staff when an address for a large apartment is entered to prompt them to ask for unit number.
+- Alert staff when an address for a large apartment is entered to prompt them to ask for a unit number.
- Alert staff when the address of a hotel or other temporary housing is entered.
- Alert staff when an address for a different country is entered.
-- Alert staff when a specific city or zip code is entered if that city or zip code needs to be handled in a special way. If you have a neighboring city that you don't have a reciprocal relationship with, you could notify staff that a fee card is required for this customer.
+- Alert staff when a specific city or zip code is entered if that city or zip code needs to be handled in a special way. If you have a neighboring city that you don't have a reciprocal relationship with, you could notify staff that a fee card is required for this customer.
== Access Control and Scoping ==
-Each address alert is tied to an Org Unit and will only be matched against staff client instances of that Org Unit and its children.
+Each address alert is tied to an organizational unit and will only be matched against staff client instances of that organizational unit and its children.
-When viewing the address alerts you will only see the alerts associated with the specific org unit selected in the *"Context Org Unit"* selection box. You won't see alerts associated with parent org units, so the list of alerts isn't a list of all alerts that may effect your org unit, only of the ones that you can edit.
+When viewing the address alerts, you will only see the alerts associated with the specific organizational unit selected in the context selection box. You won't see alerts associated with parent organizational units, so the list of alerts isn't a list of all alerts that may affect your organizational unit, only of the ones that you can edit.
-The specific permission that controls access to configuring this feature is ADMIN_ADDRESS_ALERT. Local Administrator level users will already have this permission. It is possible for the Local Administrator to grant this permission to other staff.
-
-== Adding a new Address Alert ==
+== Adding a New Address Alert ==
How to add an address to the alert list:
. Log into the Evergreen Staff Client using a Local Administrator account or another account that has been granted the proper permission.
-. Click on Administration -> Local Administration -> Address Alerts.
-. Click "New Address Alert."
+. Click on *Administration* -> *Local Administration* -> *Address Alerts*.
+. Click *New Address Alert*.
. A form will open with the following fields to fill out:
+
.New Address Alert Fields
|===
|*Field* |*Description*
-| Owner |Which Org Unit owns this alert. Set this to your system or branch.
+| Owner |Which organizational unit owns this alert. Set this to your system or branch.
| Alert Message |Message that will be displayed to staff when this alert is triggered.
| Street (1) |Street 1 field regular expression.
| Street (2) |Street 2 field regular expression.
@@ -54,29 +52,29 @@ How to add an address to the alert list:
| Billing Address |Check-box that specifies that the alert will only match a billing address if checked.
| Mailing Address |Check-box that specifies that the alert will only match a mailing address if checked.
| Match All Fields |Check-box that controls if all the fields need to match to trigger the alert(checked), or only at least one field needs to match(unchecked).
-| Active |Check-box that controls if the alert is active or not. Inactive alerts are not processed.
-| Address Alert ID |Displays the internal database id for alert after the alert has been saved. This auto-populates.
+| Active |Check-box that controls if the alert is active or not. Inactive alerts are not processed.
+| Address Alert ID |Displays the internal database id for alert after the alert has been saved. This auto-populates.
|===
+
-. Click save once you have finished.
+. Click *Save* once you have finished.
== Editing an Address Alert ==
-To make changes to an existing alert, double click on the alert in the list. The editing form will appear, make your changes and click save or cancel when you are done.
+To make changes to an existing alert, double click on the alert in the list. The editing form will appear. Make your changes and click *Save* (or *Cancel* to exit the form and cancel the action) when you are done.
-If you don't see your alerts, make sure the *"Context Org Unit"* selection box has the correct Org Unit selected.
+If you don't see your alerts, make sure the organizational unit in the context box has the correct organizational unit selected.
image::lsa_address_alert/edit_address_alert.jpg[Editing an Address Alert]
== Deleting an Address Alert ==
-To delete an alert or many alerts, click the selection check-box for all alerts you would like to delete. Then click the "Delete Selected" button at the top of the screen.
+To delete an alert or many alerts, click the selection checkbox for all alerts you would like to delete. Then click the *Delete Selected* button at the top of the screen.
image::lsa_address_alert/delete_address_alert.jpg[Delete Address Alert]
== Staff View of Address Alerts ==
-When an Address Alert is triggered by a matching address the staff will see the address block highlighted with a red dashed line, along with an *"Address Alert"* block which contains the alert message.
+When an Address Alert is triggered by a matching address, staff will see the address block highlighted with a red dashed line, along with an *Address Alert* block which contains the alert message.
Here is an example of what staff would see.
@@ -88,7 +86,7 @@ All of the patterns entered to match the various address fields are evaluated as
[NOTE]
==========
-Address Alerts use POSIX Regular Expressions included in the PostgreSQL database engine. See the PostgreSQL documentation for full details.
+Address Alerts use POSIX Regular Expressions included in the PostgreSQL database engine. See the PostgreSQL documentation for full details.
==========
If you want to do a case-sensitive match you need to prepend the pattern with "(?c)"
@@ -100,17 +98,17 @@ The simplest regular expression that acts as a wildcard is ".*", that matches an
.Apartment address
Match an apartment address to prompt for unit number.
-. Choose *Owner* Org Unit.
+. Choose *Owner* organizational unit
. Active = Checked
. Match All Fields = Checked
-. Alert Message = "This is a large apartment building, Please ask customer for unit number."
+. Alert Message = "This is a large apartment building. Please ask customer for unit number."
. Street (1) = "1212 Evergreen Lane.*"
. City = "mytown"
.All addresses on street
-Match all addresses on a certain street. Matches ave and avenue because of ending wildcard.
+Match all addresses on a certain street. Matches ave and avenue because of ending wildcard.
-. Choose *Owner* Org Unit.
+. Choose *Owner* organizational unit
. Active = Checked
. Match All Fields = Checked
. Alert Message = "This street is in a different county, please setup reciprocal card."
@@ -118,9 +116,9 @@ Match all addresses on a certain street. Matches ave and avenue because of endi
. City = "mytown"
.Match list of cities
-Match several different cities with one alert. Could be used if certain cities don't have reciprocal agreements. Note the use of parentheses and the | character to separate the different options.
+Match several different cities with one alert. Could be used if certain cities don't have reciprocal agreements. Note the use of parentheses and the | character to separate the different options.
-. Choose *Owner* Org Unit.
+. Choose *Owner* organizational unit
. Active = Checked
. Match All Fields = Checked
. Alert Message = "Customer must purchase a Fee card."
commit 9ee8a37c753dc2fe64dd57b71b38e2148795a228
Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com>
Date: Thu Jul 3 15:54:53 2025 -0400
Docs: Updated "org unit" terminology in circulation_limit_groups.adoc
Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com>
diff --git a/docs/modules/admin/pages/circulation_limit_groups.adoc b/docs/modules/admin/pages/circulation_limit_groups.adoc
index 8e6d359204..c5eb56c4ec 100644
--- a/docs/modules/admin/pages/circulation_limit_groups.adoc
+++ b/docs/modules/admin/pages/circulation_limit_groups.adoc
@@ -14,15 +14,15 @@ To limit checkouts by shelving location:
. Click *Administration -> Local Administration -> Circulation Limit Sets*.
. Click *New Circulation Limit Set* to create a new circulation limit set.
. Enter a brief *Description* of the circulation limit set.
-. Check the box adjacent to *Global Flag* if you want all of the org units in
+. Check the box adjacent to *Global Flag* if you want all of the organizational units in
your consortium to be restricted by this limit set when it is applied to a
circulation policy. Otherwise, Evergreen will only apply the limit to the direct
ancestors and descendants of the owning library.
. *ID* will autopopulate after saving.
. Enter the number of *Items Out* that a user can take from this shelving location.
-. Enter the *Min Depth*, or the minimum depth in the org tree that Evergreen
+. Enter the *Min Depth*, or the minimum depth in the organizational unit tree that Evergreen
will consider as valid circulation libraries for counting items out. The min
-depth is based on org unit type depths. For example, if you want the items in
+depth is based on organizational unit type depths. For example, if you want the items in
all of the circulating libraries in your consortium to be eligible for
restriction by this limit set when it is applied to a circulation policy, then
enter a zero (0) in this field.
commit c9a905c3e8414c44d649cf039ab9fc833f5d61c3
Author: Jennifer Pringle <jennifer.pringle(a)bc.libraries.coop>
Date: Thu Jul 3 12:50:58 2025 -0700
Docs: Update "org unit" acquisitions_admin.adoc
Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com>
diff --git a/docs/modules/admin/pages/acquisitions_admin.adoc b/docs/modules/admin/pages/acquisitions_admin.adoc
index c8cba0c79a..3f37f93b92 100644
--- a/docs/modules/admin/pages/acquisitions_admin.adoc
+++ b/docs/modules/admin/pages/acquisitions_admin.adoc
@@ -99,7 +99,7 @@ image::acq_funds/claiming1.PNG[Claiming]
[[acq_claim_policy]]
=== Create a claim policy ===
-To create a claim policy, go to _Administration -> Acquisitions Administration>Claiming_. The first tab in this interface is labeled _Claim Policies_. Claim Policies enables you to name the claim policy and specify the organization that owns it.
+To create a claim policy, go to _Administration -> Acquisitions Administration -> Claiming_. The first tab in this interface is labeled _Claim Policies_. Claim Policies enables you to name the claim policy and specify the organization that owns it.
. To create a claim policy, click _New Claim Policy_.
@@ -107,7 +107,7 @@ To create a claim policy, go to _Administration -> Acquisitions Administration>C
. Enter a claim policy Description. No limits exist on the number of characters that can be entered in this field. Example: Materials overdue by 30 days.
-. Select an Org Unit from the drop-down menu. The org unit indicates the organizational units whose staff can use this claim policy. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
+. Select an Owner from the drop-down menu. The Owner indicates the organizational units whose staff can use this claim policy. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
[NOTE] The rule of parental inheritance applies to this list.
@@ -124,7 +124,7 @@ The claim type link enables you to specify the reason for a type of claim.
. Enter a Code and a Description. No limits exist on the number of characters that can be entered in these fields. Example: Past due, Damaged, Wrong Item, etc.
-. Select an Org Unit from the drop-down menu. The org unit indicates the organizational units whose staff can use this claim type. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
+. Select an Owner from the drop-down menu. The Owner indicates the organizational units whose staff can use this claim type. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
[NOTE] The rule of parental inheritance applies to this list.
@@ -145,7 +145,7 @@ The claim event type describes the physical action that should occur when an ite
[NOTE] Currently, all claims are initiated by a user. The ILS cannot automatically claim an issue.
-. Select an Org Unit from the drop-down menu. The org unit indicates the organizational units whose staff can use this event type. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
+. Select an Owner from the drop-down menu. The Owner indicates the organizational units whose staff can use this event type. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
[NOTE] The rule of parental inheritance applies to this list.
@@ -239,7 +239,7 @@ needed.
. Enter a Formula Name. No limits exist on the number of characters that can be entered in this field.
-. Choose a Formula Owner from the drop-down menu. The Formula Owner indicates the organizational units whose staff can use this formula. TThe drop-down menu is controlled by permissions and you will see a list of org units that your user account has permission to create distribution formulas for.
+. Choose a Formula Owner from the drop-down menu. The Formula Owner indicates the organizational units whose staff can use this formula. The drop-down menu is controlled by permissions and you will see a list of organizational units that your user account has permission to create distribution formulas for.
.
[NOTE] The rule of parental inheritance applies to this list.
@@ -528,7 +528,7 @@ If your library does not wish to track fund accounting, you can create one large
In the funds interface, you can create funds; allocate credits from funding sources to funds; transfer money between funds; and apply fund tags to funds.
-Funds are created for a specific year, either fiscal or calendar, and are owned by an org unit or library. At the top of the funds interface, you can set a contextual org unit or library to view the associated funds. Within the grid display of funds you can filter by year to view the funds for a specific year only.
+Funds are created for a specific year, either fiscal or calendar, and are owned by an organizational unit or library. At the top of the funds interface, you can set a contextual organizational unit or library to view the associated funds. Within the grid display of funds you can filter by year to view the funds for a specific year only.
The Funds tab will give you a general overview of the configuration and status of your funds.
@@ -541,7 +541,7 @@ To create a new Fund:
. Enter a Name for the fund. No limits exist on the number of characters that can be entered in this field.
. Create a Code for the fund. No limits exist on the number of characters that can be entered in this field.
. Enter a Year for the fund. This can be a fiscal year or a calendar year. The format of the year is YYYY. The year entry is restricted to a range of 10 years before through 10 years after the current year.
-. Select an Org Unit from the drop-down menu. The org unit indicates the organizational units whose staff can use this fund. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
+. Select an Owner from the drop-down menu. The owner indicates the organizational units whose staff can use this fund. This menu is populated with the Short (Policy) Name codes that you created for your libraries in the organizational units tree (See Administration -> Server Administration -> Organizational Units).
. Check the Active box to make this an active fund. You cannot make purchases from this fund if it is not active.
. Select a Currency Type from the drop-down menu. This menu consists of entries Currencies and Exchange Rates interface. When a fund is applied to a line item or copy, the price of the item will be encumbered in the currency associated with the fund.
. Check the Propagate box if you want to propagate funds during fiscal year close out procedures.
@@ -612,16 +612,16 @@ To perform the year end closeout of funds:
. Go to _Administration -> Acquisitions Administration -> Fund Administration_.
. Review your current funds.
-.. Confirm that the correct Org Unit is selected.
+.. Confirm that the correct organizational unit is selected.
.. Double check the Year Filter. It defaults to the current year, so you may need to switch back to a previous year to view funds that have not been rolled over yet. If the list is blank, check this.
.. Double check that the correct funds have Propagate and Rollover set.
. Click _Fiscal Propagation and Rollover_.
. Verify the Context Org Unit for the close out operation.
. Select the Year that you want to close out.
-. Include funds from descendant Org Units: check this box if you want to include funds owned by descendant org units of the Context Org Unit.
+. Include funds from descendant Org Units: check this box if you want to include funds owned by descendant organizational units of the Context Org Unit.
. Fund Propagation: This will happen automatically when _Process_ is clicked, if the Fund’s Propagate setting is enabled.
. Perform Fiscal Year Close-Out: check this box to move encumbrances and unspent funds to the analogous fund for the next fiscal year. It will also deactivate funds for the selected fiscal year. Evergreen will only move encumbrances and unspent funds if the Rollover setting is enabled for a fund.
-.. Limit Fiscal Year Close-Out to Encumbrances: check this box if only encumbered funds should be moved to the analogous fund for the next fiscal year. Unspent funds will not be carried forward to the next fiscal year. This setting will only display if the ‘Allow funds to be rolled over without bringing the money along’ Library Setting has been enabled. This setting is available in the Library Setting Editor accessible via Administration -> Local Administration -> Library Settings Editor.
+.. Limit Fiscal Year Close-Out to Encumbrances: check this box if only encumbered funds should be moved to the analogous fund for the next fiscal year. Unspent funds will not be carried forward to the next fiscal year. This setting will only display if the ‘Allow funds to be rolled over without bringing the money along’ library setting has been enabled. This setting is available in the Library Setting Editor accessible via Administration -> Local Administration -> Library Settings Editor.
. Dry Run: check this box if you want to test changes to the funds before they are enacted. Evergreen will generate a summary of the changes that would occur during the selected operations. No data will be changed.
. Click _Process_.
. Evergreen will begin the propagation process. Evergreen will make a clone of each fund, but it will increment the year by 1.
@@ -786,7 +786,7 @@ To create a new Provider Account, follow one of the paths listed above to retrie
.. _Default Claim Policy_: assign a default claim policy to be applied to purchase orders created with this provider. Claim policies are set up in Acquisitions Administration. (optional)
.. _Default # Copies_: assign a default number of copies to be automatically created for each line item in purchase orders created with this provider. (optional)
.. _EDI Default_: assign the EDI Account to be used on purchase orders created with this provider. EDI Accounts can be set up from within the Provider record or from Acquisitions Administration->EDI Accounts. (optional)
-.. _Owner_: assign the org unit that will use this provider account. This field will default to the org unit of the workstation you are logged in at. (required)
+.. _Owner_: assign the organizational unit that will use this provider account. This field will default to the organizational unit of the workstation you are logged in at. (required)
.. _URL_: add a URL associated with the provider (optional). URLs must include the prefix, such as http:// or https:// in order to link correctly.
.. _SAN_: assign the provider’s SAN. (required if using EDI ordering)
.. _Prepayment Required_: indicate if prepayment is required for orders with this provider. (optional)
@@ -877,4 +877,4 @@ As part of transitioning the General Search interface to Angular, several change
.. Prepayment Required
. Column headers for the search results can be clicked on to sort the results by the column. The columns will sort alphabetically or by date as appropriate for the data type.
. Using the column actions to filter or sort search results will execute a new search using the original search parameters. If any un-executed changes are made to the search parameters between the initial search submission and any changes to the filters, the new search parameters will be executed upon filtering.
-. Dropdown menus for the search fields will retrieve a maximum of 100 rows at a time.
\ No newline at end of file
+. Dropdown menus for the search fields will retrieve a maximum of 100 rows at a time.
commit 38095f822d38164ccc1f92af4c17bfc775d5d01c
Author: Jennifer Pringle <jennifer.pringle(a)bc.libraries.coop>
Date: Thu Jul 3 12:37:40 2025 -0700
Docs: Update "org unit" in copy_locations.adoc
Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com>
diff --git a/docs/modules/admin/pages/copy_locations.adoc b/docs/modules/admin/pages/copy_locations.adoc
index 92caa3288b..19260fe821 100644
--- a/docs/modules/admin/pages/copy_locations.adoc
+++ b/docs/modules/admin/pages/copy_locations.adoc
@@ -22,7 +22,7 @@ To add a shelving location
image::shelving_location/shelving_location_new.png[New shelving location]
+
. Select your parameters for your shelving locations.
-.. Choose the owning Org Unit of the shelving location.
+.. Choose the Owning Org Unit of the shelving location.
.. Type the name of the shelving location in the name field.
.. _Is OPAC Visible?_, choose whether you would like items in this shelving location to appear in the catalog.
.. _Can Circulate?_ can items in this location circulate?
@@ -74,7 +74,7 @@ Evergreen preserves shelving locations in the database, so no statistical inform
== Modifying shelving location order ==
-By default Evergreen displays shelving locations in alphabetical order. This order can be modified per Org Unit.
+By default Evergreen displays shelving locations in alphabetical order. This order can be modified per organizational unit.
To modify the order of shelving locations, Go to *Administration -> Local Administration -> Shelving Location Order*
@@ -82,9 +82,9 @@ image::shelving_location/shelving_location_order.png[Shelving Location Order]
To change the order:
-. Choose the Org Unit you are wanting to reorder.
+. Choose the organizational unit you are wanting to reorder.
. Drag and drop the locations until you are satisfied with their order.
-. Click _Apply changes_.
+. Click _Save changes_.
== Shelving location groups ==
@@ -94,7 +94,7 @@ To change the order:
Mayberry Public Library provides a scope allowing users to search for all children's materials in their library. The library's children's scope incorporates several shelving locations used at the library, including picture Books, Children's Fiction, Children's Non-Fiction, Easy Readers, and Children's DVDs. The library also builds a similar scope for YA materials that incorporates several shelving locations.
****
-This feature allows staff to create and name sets of shelving locations to use as a search filter in the catalog. OPAC-visible groups will display within the library selector in the [.underline]#Public Catalog#. When a user selects a group and performs a search, the set of results will be limited to records that have items in one of the shelving locations within the group. Groups can live at any level of the library hierarchy and may include shelving locations from any parent org unit or child org unit.
+This feature allows staff to create and name sets of shelving locations to use as a search filter in the catalog. OPAC-visible groups will display within the library selector in the [.underline]#Public Catalog#. When a user selects a group and performs a search, the set of results will be limited to records that have items in one of the shelving locations within the group. Groups can live at any level of the library hierarchy and may include shelving locations from any parent organizational unit or child organizational unit.
NOTE: To work with shelving location groups, you will need the ADMIN_COPY_LOCATION_GROUP permission.
@@ -103,22 +103,22 @@ image::shelving_location/shelving_location_groups_editor.png[Shelving Location G
=== Create a shelving location group ===
. Click *Administration -> Local Administration -> Shelving Location Groups*.
-. At the top of the screen is a menu that displays the org unit tree. Select the unit within the org tree to which you want to add a shelving location group. The shelving locations associated with the org unit appear in the shelving locations column.
+. The library selector at the screen defaults to the highlest level organizational unit. Select the organizational unit to which you want to add a shelving location group; the associated shelving locations will appear in the shelving locations column.
. Click _New Location Group_.
+
image::shelving_location/new_shelving_location_group.png[New Shelving Location Group]
+
-. Choose how you want the shelving location group to display to patrons in the catalog's org unit tree in the OPAC. By default, when you add a new shelving location group, the group displays in the org unit tree beneath any branches or sub-libraries of its parental org unit. If you select _Yes_ for _Display Above Orgs_, then the group will appear above the branches or sub-libraries of its parental org unit.
+. Choose how you want the shelving location group to display to patrons in the catalog's organizational unit tree in the OPAC. By default, when you add a new shelving location group, the group displays in the organizational unit tree beneath any branches or sub-libraries of its parental organizational unit. If you select _Yes_ for _Display Above Orgs_, then the group will appear above the branches or sub-libraries of its parental organizational unit.
. To make the shelving location group visible to users searching the public catalog, select _Yes_ for _Is OPAC Visible?_
. _Position_ will order the display of the shelving location group. This takes integers with 0 being first.
. Enter a _Name_ for the shelving location group.
. Click Save. The name of the shelving location group appears in the location groups.
-. Select the shelving locations that you want to add to the group, and click Add. The shelving locations will populate the middle column, Group Entries.
-. The shelving location group is now visible in the org unit tree in the catalog. Search the catalog to retrieve results from any of the shelving locations that you added to the shelving location group.
+. Select the shelving locations that you want to add to the group, and click _Add to group_. The shelving locations will populate the middle column, Shelving Locations in Group.
+. The shelving location group is now visible in the organizational unit tree in the catalog. Search the catalog to retrieve results from any of the shelving locations that you added to the shelving location group.
=== Order shelving location groups ===
-If you create more than one shelving location group, then you can order the groups in the org unit tree.
+If you create more than one shelving location group, then you can order the groups in the organizational unit tree.
image::shelving_location/sl_groups_example.png[Shelving Location Group Display Example]
-----------------------------------------------------------------------
Summary of changes:
docs/modules/admin/pages/acquisitions_admin.adoc | 24 +++++-----
.../admin/pages/circulation_limit_groups.adoc | 6 +--
docs/modules/admin/pages/copy_locations.adoc | 20 ++++-----
docs/modules/admin/pages/lsa-address_alert.adoc | 52 +++++++++++-----------
4 files changed, 50 insertions(+), 52 deletions(-)
hooks/post-receive
--
Evergreen ILS
1
0
[GIT] Evergreen ILS branch main updated. 371b82bb76b08d5dad7f1c517c899e37a71f0b66
by Git User 09 Jul '25
by Git User 09 Jul '25
09 Jul '25
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, main has been updated
via 371b82bb76b08d5dad7f1c517c899e37a71f0b66 (commit)
from 1153f4784c1cd4bb4b3ca9dd6c5a9c46d23f10a2 (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 371b82bb76b08d5dad7f1c517c899e37a71f0b66
Author: Dan Briem <dbriem(a)harrisonpl.org>
Date: Fri Jun 6 05:18:14 2025 +0000
LP#2112613 AngularJS modal close button has insufficient contrast
- Sets modal color CSS variables to the body colors in light mode.
- --modal-header-bg is currently unused, but was updated to
provide appropriate contrast if used in the future.
Release-note:
Fixes AngularJS modal close button contrast in light mode.
Signed-off-by: Dan Briem <dbriem(a)harrisonpl.org>
Signed-off-by: John Amundson <jamundson(a)cwmars.org>
Signed-off-by: Stephanie Leary <stephanie.leary(a)equinoxoli.org>
diff --git a/Open-ILS/src/templates/staff/css/light.css.tt2 b/Open-ILS/src/templates/staff/css/light.css.tt2
index 7f099be099..0c17cd0d26 100644
--- a/Open-ILS/src/templates/staff/css/light.css.tt2
+++ b/Open-ILS/src/templates/staff/css/light.css.tt2
@@ -94,8 +94,8 @@
--btn-gray-color: var(--bs-body-color);
--btn-gray-border: var(--bs-gray-400);
- --modal-header-color: white;
- --modal-header-bg: var(--bs-cyan-800);
+ --modal-header-color: var(--bs-body-color);
+ --modal-header-bg: var(--bs-body-bg);
--modal-body-bg: var(--bs-body-bg);
--popover-menu-hover: var(--bs-gray-100);
--popover-header-bg: var(--bs-gray-100);
-----------------------------------------------------------------------
Summary of changes:
Open-ILS/src/templates/staff/css/light.css.tt2 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
hooks/post-receive
--
Evergreen ILS
1
0
[GIT] Evergreen ILS branch rel_3_15 updated. b2348b675a7a9b685ab794881c3f388ee0838ab3
by Git User 09 Jul '25
by Git User 09 Jul '25
09 Jul '25
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_3_15 has been updated
via b2348b675a7a9b685ab794881c3f388ee0838ab3 (commit)
from 5769a56641bc4998ec7646059d718b9c00bf0d56 (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 b2348b675a7a9b685ab794881c3f388ee0838ab3
Author: Dan Briem <dbriem(a)harrisonpl.org>
Date: Fri Jun 6 05:18:14 2025 +0000
LP#2112613 AngularJS modal close button has insufficient contrast
- Sets modal color CSS variables to the body colors in light mode.
- --modal-header-bg is currently unused, but was updated to
provide appropriate contrast if used in the future.
Release-note:
Fixes AngularJS modal close button contrast in light mode.
Signed-off-by: Dan Briem <dbriem(a)harrisonpl.org>
Signed-off-by: John Amundson <jamundson(a)cwmars.org>
Signed-off-by: Stephanie Leary <stephanie.leary(a)equinoxoli.org>
diff --git a/Open-ILS/src/templates/staff/css/light.css.tt2 b/Open-ILS/src/templates/staff/css/light.css.tt2
index 7f099be099..0c17cd0d26 100644
--- a/Open-ILS/src/templates/staff/css/light.css.tt2
+++ b/Open-ILS/src/templates/staff/css/light.css.tt2
@@ -94,8 +94,8 @@
--btn-gray-color: var(--bs-body-color);
--btn-gray-border: var(--bs-gray-400);
- --modal-header-color: white;
- --modal-header-bg: var(--bs-cyan-800);
+ --modal-header-color: var(--bs-body-color);
+ --modal-header-bg: var(--bs-body-bg);
--modal-body-bg: var(--bs-body-bg);
--popover-menu-hover: var(--bs-gray-100);
--popover-header-bg: var(--bs-gray-100);
-----------------------------------------------------------------------
Summary of changes:
Open-ILS/src/templates/staff/css/light.css.tt2 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
hooks/post-receive
--
Evergreen ILS
1
0
[GIT] Evergreen ILS branch rel_3_14 updated. 612117e942aa0b01db6fe11c9d3e18f064f13e06
by Git User 09 Jul '25
by Git User 09 Jul '25
09 Jul '25
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_3_14 has been updated
via 612117e942aa0b01db6fe11c9d3e18f064f13e06 (commit)
from 2816853cc466ca93b6d23cc03b82c3ab427d0a2d (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 612117e942aa0b01db6fe11c9d3e18f064f13e06
Author: Dan Briem <dbriem(a)harrisonpl.org>
Date: Fri Jun 6 05:18:14 2025 +0000
LP#2112613 AngularJS modal close button has insufficient contrast
- Sets modal color CSS variables to the body colors in light mode.
- --modal-header-bg is currently unused, but was updated to
provide appropriate contrast if used in the future.
Release-note:
Fixes AngularJS modal close button contrast in light mode.
Signed-off-by: Dan Briem <dbriem(a)harrisonpl.org>
Signed-off-by: John Amundson <jamundson(a)cwmars.org>
Signed-off-by: Stephanie Leary <stephanie.leary(a)equinoxoli.org>
diff --git a/Open-ILS/src/templates/staff/css/light.css.tt2 b/Open-ILS/src/templates/staff/css/light.css.tt2
index 7f099be099..0c17cd0d26 100644
--- a/Open-ILS/src/templates/staff/css/light.css.tt2
+++ b/Open-ILS/src/templates/staff/css/light.css.tt2
@@ -94,8 +94,8 @@
--btn-gray-color: var(--bs-body-color);
--btn-gray-border: var(--bs-gray-400);
- --modal-header-color: white;
- --modal-header-bg: var(--bs-cyan-800);
+ --modal-header-color: var(--bs-body-color);
+ --modal-header-bg: var(--bs-body-bg);
--modal-body-bg: var(--bs-body-bg);
--popover-menu-hover: var(--bs-gray-100);
--popover-header-bg: var(--bs-gray-100);
-----------------------------------------------------------------------
Summary of changes:
Open-ILS/src/templates/staff/css/light.css.tt2 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
hooks/post-receive
--
Evergreen ILS
1
0
[GIT] Evergreen ILS branch rel_3_14 updated. 2816853cc466ca93b6d23cc03b82c3ab427d0a2d
by Git User 08 Jul '25
by Git User 08 Jul '25
08 Jul '25
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_3_14 has been updated
via 2816853cc466ca93b6d23cc03b82c3ab427d0a2d (commit)
from c13076109a88277aefb1299c84940dd8c1698ec1 (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 2816853cc466ca93b6d23cc03b82c3ab427d0a2d
Author: Stephanie Leary <stephanie.leary(a)equinoxoli.org>
Date: Thu Jun 26 14:58:18 2025 +0000
LP2115535 Basket nav markup, ARIA label
Creates a separate navigation landmark for the OPAC basket. This is
useful primarily when there are items in the basket, in which case a
dropdown menu of basket actions becomes available.
Release-note: Adds a separate navigation landmark for OPAC basket
Signed-off-by: Stephanie Leary <stephanie.leary(a)equinoxoli.org>
Signed-off-by: Garry Collum <gcollum(a)gmail.com>
Signed-off-by: Jane Sandberg <js7389(a)princeton.edu>
Sponsored-by: BC Libraries Cooperative
diff --git a/Open-ILS/src/templates-bootstrap/opac/css/style.css.tt2 b/Open-ILS/src/templates-bootstrap/opac/css/style.css.tt2
index ef9a671593..2f6716f99b 100755
--- a/Open-ILS/src/templates-bootstrap/opac/css/style.css.tt2
+++ b/Open-ILS/src/templates-bootstrap/opac/css/style.css.tt2
@@ -1723,7 +1723,8 @@ tr.result_table_row > td.result_table_pic_header {
text-decoration: none;
}
#basket_actions {
- margin: .5rem;
+ margin: .5rem;
+ padding-inline: 1rem 1.5rem;
}
#basket_actions select {
border-color: [% css_colors.basket_actions_select_border %];
diff --git a/Open-ILS/src/templates-bootstrap/opac/parts/cart.tt2 b/Open-ILS/src/templates-bootstrap/opac/parts/cart.tt2
index 594f43df36..526272fe4f 100755
--- a/Open-ILS/src/templates-bootstrap/opac/parts/cart.tt2
+++ b/Open-ILS/src/templates-bootstrap/opac/parts/cart.tt2
@@ -1,4 +1,4 @@
-<div id="record_basket">
+<nav id="record_basket" aria-label="[% l('Basket') %]">
<div id="basket_actions">
<select id="select_basket_action" aria-label="[% l('Select basket action') %]">
<option value="">[% l('-- Basket Actions --') %]</option>
@@ -39,4 +39,4 @@
</div>
</a>
</div>
-</div>
+</nav>
diff --git a/Open-ILS/src/templates-bootstrap/opac/parts/cart_nav.tt2 b/Open-ILS/src/templates-bootstrap/opac/parts/cart_nav.tt2
index 1087f813cd..2aac3b573e 100755
--- a/Open-ILS/src/templates-bootstrap/opac/parts/cart_nav.tt2
+++ b/Open-ILS/src/templates-bootstrap/opac/parts/cart_nav.tt2
@@ -1,10 +1,10 @@
- <div id="basket_actions">
+ <nav id="basket_actions" aria-label="[% l('Basket') %]">
<div id="select_basket_action" class="dropdown">
<button type="button" class="btn p-1" id="cartDropdown" data-toggle="dropdown"
- aria-label="[% l('View basket'); %]" aria-describedby="record_basket_count">
+ aria-label="[% l('View basket'); %]" aria-labelledby="cartDropdown record_basket_count" aria-expanded="false">
<img id="cart_icon_image" src="[% ctx.media_prefix %]/images/cart-sm.png[% ctx.cache_key %]" alt="">
- <div id="record_basket_count_floater" role="status" aria-labelledby="cartDropdown">
+ <div id="record_basket_count_floater">
<span id="record_basket_count">[% ctx.mylist.size %]</span>
</div>
</button>
@@ -22,4 +22,4 @@
<a class="dropdown-item" role="menuitem" href="[% mkurl(ctx.opac_root _ '/mylist/clear', {}) %]"><i class="fas fa-trash" aria-hidden="true"></i> [% l('Clear Basket') %]</a>
</div>
</div>
- </div>
+ </nav>
-----------------------------------------------------------------------
Summary of changes:
Open-ILS/src/templates-bootstrap/opac/css/style.css.tt2 | 3 ++-
Open-ILS/src/templates-bootstrap/opac/parts/cart.tt2 | 4 ++--
Open-ILS/src/templates-bootstrap/opac/parts/cart_nav.tt2 | 8 ++++----
3 files changed, 8 insertions(+), 7 deletions(-)
hooks/post-receive
--
Evergreen ILS
1
0
[GIT] Evergreen ILS branch main updated. 1153f4784c1cd4bb4b3ca9dd6c5a9c46d23f10a2
by Git User 08 Jul '25
by Git User 08 Jul '25
08 Jul '25
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, main has been updated
via 1153f4784c1cd4bb4b3ca9dd6c5a9c46d23f10a2 (commit)
from e50e936afa4c9c68c7846dc800b44303187d3c2f (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 1153f4784c1cd4bb4b3ca9dd6c5a9c46d23f10a2
Author: Stephanie Leary <stephanie.leary(a)equinoxoli.org>
Date: Thu Jun 26 14:58:18 2025 +0000
LP2115535 Basket nav markup, ARIA label
Creates a separate navigation landmark for the OPAC basket. This is
useful primarily when there are items in the basket, in which case a
dropdown menu of basket actions becomes available.
Release-note: Adds a separate navigation landmark for OPAC basket
Signed-off-by: Stephanie Leary <stephanie.leary(a)equinoxoli.org>
Signed-off-by: Garry Collum <gcollum(a)gmail.com>
Signed-off-by: Jane Sandberg <js7389(a)princeton.edu>
Sponsored-by: BC Libraries Cooperative
diff --git a/Open-ILS/src/templates-bootstrap/opac/css/style.css.tt2 b/Open-ILS/src/templates-bootstrap/opac/css/style.css.tt2
index ef9a671593..2f6716f99b 100755
--- a/Open-ILS/src/templates-bootstrap/opac/css/style.css.tt2
+++ b/Open-ILS/src/templates-bootstrap/opac/css/style.css.tt2
@@ -1723,7 +1723,8 @@ tr.result_table_row > td.result_table_pic_header {
text-decoration: none;
}
#basket_actions {
- margin: .5rem;
+ margin: .5rem;
+ padding-inline: 1rem 1.5rem;
}
#basket_actions select {
border-color: [% css_colors.basket_actions_select_border %];
diff --git a/Open-ILS/src/templates-bootstrap/opac/parts/cart.tt2 b/Open-ILS/src/templates-bootstrap/opac/parts/cart.tt2
index 594f43df36..526272fe4f 100755
--- a/Open-ILS/src/templates-bootstrap/opac/parts/cart.tt2
+++ b/Open-ILS/src/templates-bootstrap/opac/parts/cart.tt2
@@ -1,4 +1,4 @@
-<div id="record_basket">
+<nav id="record_basket" aria-label="[% l('Basket') %]">
<div id="basket_actions">
<select id="select_basket_action" aria-label="[% l('Select basket action') %]">
<option value="">[% l('-- Basket Actions --') %]</option>
@@ -39,4 +39,4 @@
</div>
</a>
</div>
-</div>
+</nav>
diff --git a/Open-ILS/src/templates-bootstrap/opac/parts/cart_nav.tt2 b/Open-ILS/src/templates-bootstrap/opac/parts/cart_nav.tt2
index 1087f813cd..2aac3b573e 100755
--- a/Open-ILS/src/templates-bootstrap/opac/parts/cart_nav.tt2
+++ b/Open-ILS/src/templates-bootstrap/opac/parts/cart_nav.tt2
@@ -1,10 +1,10 @@
- <div id="basket_actions">
+ <nav id="basket_actions" aria-label="[% l('Basket') %]">
<div id="select_basket_action" class="dropdown">
<button type="button" class="btn p-1" id="cartDropdown" data-toggle="dropdown"
- aria-label="[% l('View basket'); %]" aria-describedby="record_basket_count">
+ aria-label="[% l('View basket'); %]" aria-labelledby="cartDropdown record_basket_count" aria-expanded="false">
<img id="cart_icon_image" src="[% ctx.media_prefix %]/images/cart-sm.png[% ctx.cache_key %]" alt="">
- <div id="record_basket_count_floater" role="status" aria-labelledby="cartDropdown">
+ <div id="record_basket_count_floater">
<span id="record_basket_count">[% ctx.mylist.size %]</span>
</div>
</button>
@@ -22,4 +22,4 @@
<a class="dropdown-item" role="menuitem" href="[% mkurl(ctx.opac_root _ '/mylist/clear', {}) %]"><i class="fas fa-trash" aria-hidden="true"></i> [% l('Clear Basket') %]</a>
</div>
</div>
- </div>
+ </nav>
-----------------------------------------------------------------------
Summary of changes:
Open-ILS/src/templates-bootstrap/opac/css/style.css.tt2 | 3 ++-
Open-ILS/src/templates-bootstrap/opac/parts/cart.tt2 | 4 ++--
Open-ILS/src/templates-bootstrap/opac/parts/cart_nav.tt2 | 8 ++++----
3 files changed, 8 insertions(+), 7 deletions(-)
hooks/post-receive
--
Evergreen ILS
1
0