- Evergreen-commits - example.com

[GIT] Evergreen ILS branch main updated. 998e6c492adf1c754392f7249dde1236bd5522e0
by Git User 18 Apr '25

18 Apr '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 998e6c492adf1c754392f7249dde1236bd5522e0 (commit) from e28cdfd3574b64dd9de0f76bd655a550028824d4 (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 998e6c492adf1c754392f7249dde1236bd5522e0 Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com> Date: Fri Apr 18 08:56:22 2025 -0400 Docs: file folder cleanup Release-note: Delete docs/modules/local_admin/assets/images/emergency_closing_handler directory Signed-off-by: Susan Morrison <smorrison(a)georgialibraries.org> Signed-off-by: Andrea Buntz Neiman <abneiman(a)equinoxinitiative.org> diff --git a/docs/modules/local_admin/assets/images/emergency_closing_handler/delete closing.png b/docs/modules/local_admin/assets/images/emergency_closing_handler/delete closing.png deleted file mode 100644 index c75983665d..0000000000 Binary files a/docs/modules/local_admin/assets/images/emergency_closing_handler/delete closing.png and /dev/null differ diff --git a/docs/modules/local_admin/assets/images/emergency_closing_handler/example closing.png b/docs/modules/local_admin/assets/images/emergency_closing_handler/example closing.png deleted file mode 100644 index c6f1f9385a..0000000000 Binary files a/docs/modules/local_admin/assets/images/emergency_closing_handler/example closing.png and /dev/null differ diff --git a/docs/modules/local_admin/assets/images/emergency_closing_handler/possibly emergency closure_section.png b/docs/modules/local_admin/assets/images/emergency_closing_handler/possibly emergency closure_section.png deleted file mode 100644 index fb14e00961..0000000000 Binary files a/docs/modules/local_admin/assets/images/emergency_closing_handler/possibly emergency closure_section.png and /dev/null differ diff --git a/docs/modules/local_admin/assets/images/emergency_closing_handler/possibly emergency closure_toast.png b/docs/modules/local_admin/assets/images/emergency_closing_handler/possibly emergency closure_toast.png deleted file mode 100644 index 4d598da279..0000000000 Binary files a/docs/modules/local_admin/assets/images/emergency_closing_handler/possibly emergency closure_toast.png and /dev/null differ diff --git a/docs/modules/local_admin/assets/images/emergency_closing_handler/upcoming closure listing.png b/docs/modules/local_admin/assets/images/emergency_closing_handler/upcoming closure listing.png deleted file mode 100644 index cc7852ce85..0000000000 Binary files a/docs/modules/local_admin/assets/images/emergency_closing_handler/upcoming closure listing.png and /dev/null differ ----------------------------------------------------------------------- Summary of changes: .../emergency_closing_handler/delete closing.png | Bin 25476 -> 0 bytes .../emergency_closing_handler/example closing.png | Bin 102446 -> 0 bytes .../possibly emergency closure_section.png | Bin 99042 -> 0 bytes .../possibly emergency closure_toast.png | Bin 11760 -> 0 bytes .../upcoming closure listing.png | Bin 33499 -> 0 bytes 5 files changed, 0 insertions(+), 0 deletions(-) delete mode 100644 docs/modules/local_admin/assets/images/emergency_closing_handler/delete closing.png delete mode 100644 docs/modules/local_admin/assets/images/emergency_closing_handler/example closing.png delete mode 100644 docs/modules/local_admin/assets/images/emergency_closing_handler/possibly emergency closure_section.png delete mode 100644 docs/modules/local_admin/assets/images/emergency_closing_handler/possibly emergency closure_toast.png delete mode 100644 docs/modules/local_admin/assets/images/emergency_closing_handler/upcoming closure listing.png hooks/post-receive -- Evergreen ILS

1 0

[GIT] Evergreen ILS branch rel_3_15 updated. 52c59d65a57e25106e82d3fad0408b319e5bdf45
by Git User 18 Apr '25

18 Apr '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 52c59d65a57e25106e82d3fad0408b319e5bdf45 (commit) from 4917c26baa1ddddd7f0473ea2cacebf48ab16691 (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 52c59d65a57e25106e82d3fad0408b319e5bdf45 Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com> Date: Fri Apr 18 08:53:26 2025 -0400 Docs: LP2063846 screenshots Release-note: Fixes screenshot location for Emergency Closing Handler Signed-off-by: Susan Morrison <smorrison(a)georgialibraries.org> Signed-off-by: Andrea Buntz Neiman <abneiman(a)equinoxinitiative.org> diff --git a/docs/modules/admin/assets/images/emergency_closing/delete closing.png b/docs/modules/admin/assets/images/emergency_closing/delete closing.png new file mode 100644 index 0000000000..c75983665d Binary files /dev/null and b/docs/modules/admin/assets/images/emergency_closing/delete closing.png differ diff --git a/docs/modules/admin/assets/images/emergency_closing/example closing.png b/docs/modules/admin/assets/images/emergency_closing/example closing.png new file mode 100644 index 0000000000..c6f1f9385a Binary files /dev/null and b/docs/modules/admin/assets/images/emergency_closing/example closing.png differ diff --git a/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_section.png b/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_section.png new file mode 100644 index 0000000000..fb14e00961 Binary files /dev/null and b/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_section.png differ diff --git a/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_toast.png b/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_toast.png new file mode 100644 index 0000000000..4d598da279 Binary files /dev/null and b/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_toast.png differ diff --git a/docs/modules/admin/assets/images/emergency_closing/upcoming closure listing.png b/docs/modules/admin/assets/images/emergency_closing/upcoming closure listing.png new file mode 100644 index 0000000000..cc7852ce85 Binary files /dev/null and b/docs/modules/admin/assets/images/emergency_closing/upcoming closure listing.png differ ----------------------------------------------------------------------- Summary of changes: .../assets/images/emergency_closing/delete closing.png | Bin 0 -> 25476 bytes .../images/emergency_closing/example closing.png | Bin 0 -> 102446 bytes .../possibly emergency closure_section.png | Bin 0 -> 99042 bytes .../possibly emergency closure_toast.png | Bin 0 -> 11760 bytes .../emergency_closing/upcoming closure listing.png | Bin 0 -> 33499 bytes 5 files changed, 0 insertions(+), 0 deletions(-) create mode 100644 docs/modules/admin/assets/images/emergency_closing/delete closing.png create mode 100644 docs/modules/admin/assets/images/emergency_closing/example closing.png create mode 100644 docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_section.png create mode 100644 docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_toast.png create mode 100644 docs/modules/admin/assets/images/emergency_closing/upcoming closure listing.png hooks/post-receive -- Evergreen ILS

1 0

[GIT] Evergreen ILS branch rel_3_15 updated. 4917c26baa1ddddd7f0473ea2cacebf48ab16691
by Git User 18 Apr '25

18 Apr '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 4917c26baa1ddddd7f0473ea2cacebf48ab16691 (commit) from dc96ae62278a0db84e7c3eae52a28c2afc0d3700 (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 4917c26baa1ddddd7f0473ea2cacebf48ab16691 Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com> Date: Tue Nov 12 15:02:54 2024 -0500 Resolves LP#2063846 Docs: Update emergency_closing_handler.adoc - Consolidated with https://docs.evergreen-ils.org/docs/latest/admin/closed_dates.html to create one page on closed dates - updated screenshots - added line about ability to see upcoming closures in library info page Signed-off-by: Gina Monti <gmonti(a)biblio.org> diff --git a/docs/modules/admin/pages/emergency_closing_handler.adoc b/docs/modules/admin/pages/emergency_closing_handler.adoc index 831e0cc680..0bf77ccc8e 100644 --- a/docs/modules/admin/pages/emergency_closing_handler.adoc +++ b/docs/modules/admin/pages/emergency_closing_handler.adoc @@ -1,101 +1,138 @@ -= Emergency Closing Handler = += Closed Dates Editor = :toc: -== Introduction == +indexterm:[Closed Dates] -The *Closed Dates Editor* now includes an Emergency Closing feature that allows libraries to shift due dates and expiry dates to the next open day. Overdue fines will be automatically voided for the day(s) the library is marked closed. Once an Emergency Closing is processed, it is permanent and cannot be rolled back. +The *Closed Dates Editor* can be accessed via *Administration -> Local Administration -> Closed Dates Editor*. -== Administration == +Within the Closed Dates Editor screen, scheduled closed dates are listed and can be scoped by a specific organizational unit and date. The date filter in the upper right-hand corner will show upcoming library closures on or after the selected date in the filter. -=== Permissions === +Entries in the Closed Dates Editor are in addition to the regular weekly closed days for each organizational unit. Both regular closed days and those entered in the Closed Dates Editor affect due dates and fines: -To create an Emergency Closing, the EMERGENCY_CLOSING permission needs to be granted to the user for all locations to be affected by an emergency closing. - -== Create an emergency closing == +* *Due dates.* Due dates that would fall on closed days are automatically pushed forward to the next open day. Likewise, if an item is checked out at 8pm, for example, and would normally be due on a day when the library closes before 8pm, Evergreen pushes the due date forward to the next open day. +* *Overdue fines.* Overdue fines may not be charged on days when the library is closed. This fine behavior depends on how the _Charge fines on overdue circulations when closed_ setting is configured in the Library Settings Editor. -The Emergency Closing feature is located within the *Closed Dates Editor* screen, which can be accessed via *Administration -> Local Administration -> Closed Dates Editor*. +Closed dates do not affect the processing delays for Action/Triggers. For example, if your library has a trigger event that marks items as lost after 30 days, that 30-day period will include both open and closed dates. -Within the closed dates editor screen, scheduled closed dates are listed and can be scoped by specific org unit and date. The date filter in the upper right-hand corner will show upcoming library closings on or after the selected date in the filter. +Any closed dates entered in the interface will also appear on the xref:opac:linked_libraries.adoc[organizational unit’s library information page] under *Upcoming Closures* -[NOTE] -======================== -*NOTE* Before creating an Emergency Closure, delete any previously entered closures that overlap the Emergency Closure you wish to enter. Overlapping closed dates can cause issues in processing the Emergency Closure. -======================== +image::emergency_closing/upcoming closure listing.png[Upcoming closures] -Select *Add closing* to begin the emergency closing process. +== Adding a closure == +. Select _Administration -> Local Administration_. +. Select _Closed Dates Editor_. +. Select _Add Closing_. ++ image::emergency_closing/ECHClosedDatesEditorAddClosing.png[Add Closing] ++ +. A pop-up will appear with fields to fill out. ++ +image::emergency_closing/example closing.png[Create Closing for One Full Day] ++ +* *Library* - Using the dropdown window, select the organizational unit which will be closing. +* *Apply to all of my libraries* - When selected, this checkbox will apply the closing date to the selected organizational unit and any associated child organizational units. ++ +[NOTE] +==== +By default, creating a closed date in a parent organizational unit does _not_ also +close the child unit. For example, adding a system-level closure will not also +close all of that system's branches, unless you check the *Apply to all of my libraries* box. +==== ++ + +* *Closing type* - Available options in the dropdown window are _One Full Day_, _Multiple Days_, and _Detailed_ (for partial day closures). The _Multiple Days_ and _Detailed_ options will display different date options (e.g., start and end dates) in the next field if selected. ++ +image::emergency_closing/ECHLibraryClosingMultipleDays.png[Create Closing for Multiple Days] ++ -A pop-up will appear with fields to fill out. ++ +image::emergency_closing/ECHLibraryClosingDetailed.png[Create Detailed Closing] ++ +* *Date* - Click the calendar gadget to select which day or days the library will be closed. ++ +[NOTE] +==== +The Closed Dates editor is now date-aware. If a selected closed date is either in the past, or nearer in time than the end of the longest configured circulation period, staff will see a notification that says _Possible Emergency Closing_ in both the dialog box and in the bottom right-hand corner. See the Emergency Closing Handler section for information on how to manage emergency closures. +==== ++ +* *Reason* - Optionally enter the reason for the closure. Note that this will appear on the library’s contact page. +. Click *OK*. -image::emergency_closing/ECHLibraryClosingConstruction.png[Create Closing for One Full Day] +== Editing a closure == -*Library* - Using the dropdown window, select the org unit which will be closing. +To edit a closure, go to *Actions -> Edit closing*. -*Apply to all of my libraries* - When selected, this checkbox will apply the emergency closing date to the selected org unit and any associated child org unit(s). +image::emergency_closing/ECHEditClosing.png[Edit Closing] -*Closing Type* - The following Closing Type options are available in a drop down window: -* One full day -* Multiple days -* Detailed closing +A pop-up display will appear with the same format as creating a Closed Dates event. Once you make the changes, click *OK*. The Closed Dates Editor display will update. -The _Multiple days_ and _Detailed closing_ options will display different date options (e.g. start and end dates) in the next field if selected. +image::emergency_closing/ECHEditClosingModal.png[Edit Closing Pop-Up] -[NOTE] -======================== -*NOTE* There is an existing bug that pushes the due dates to the first day after the Emergency Closure even if that day is normally closed. So, if you need to enter an Emergency Closure for a Friday, but you are normally closed on Saturday and Sunday, be sure to enter the Emergency Closure for Friday through Sunday. -======================== +== Emergency closing handler == -image::emergency_closing/ECHLibraryClosingMultipleDays.png[Create Closing for Multiple Days] +The *Closed Dates Editor* includes an Emergency Closing feature that allows libraries to shift due dates and expiry dates to the next open day. Overdue fines will be automatically voided for the day(s) the library is marked closed. Once an Emergency Closing is processed, it is permanent and cannot be rolled back. -image::emergency_closing/ECHLibraryClosingDetailed.png[Create Detailed Closing] +When a date is chosen that is nearer in time than the end of the longest configured circulation period or in the past, then a _Possible Emergency Closing_ message will appear as a pop-up in the bottom right-hand corner of the screen. -*Date* - Select which day or days the library will be closed. +image::emergency_closing/possibly emergency closure_toast.png[Possible Emergency Closure Toast] -[NOTE] -======================== -*NOTE* The Closed Dates editor is now date-aware. If a selected closed date is either in the past, or nearer in time than the end of the longest configured circulation period, staff will see a notification that says "Possible Emergency Closing" in both the dialog box and in the bottom right-hand corner. -======================== +A _Possible Emergency Closure_ section will also appear in the Library Closing form. -*Reason* - Label the reason for library closing accordingly, e.g. 3/15 Snow Day +image::emergency_closing/possibly emergency closure_section.png[Possible Emergency Closure Section] -=== Emergency Closing Handler === +=== Adding an emergency closure === -When a date is chosen that is nearer in time than the end of the longest configured circulation period or in the past, then a *Possible Emergency Closing* message will appear in the pop-up and in the bottom right-hand corner of the screen. Below the Possible Emergency Closing message, two checkboxes appear: *Emergency* and *Process Immediately*. Both checkboxes must be manually selected in +[NOTE] +==== +Before creating an Emergency Closure, delete any previously entered closures that overlap the Emergency Closure you wish to enter. Overlapping closed dates can cause issues in processing the closure. +==== + +To add an emergency closure, follow the process for entering a regular closed date until you reach the *Possible Emergency Closure* section. [NOTE] -========================= -*NOTE* The *Emergency* checkbox must still be manually selected in order to actually set the closing as an Emergency Closing. -========================= +==== +There is an existing bug that pushes the due dates to the first day after the Emergency Closure even if that day is normally closed. So, if you need to enter an Emergency Closure for a Friday, but you are normally closed on Saturday and Sunday, be sure to enter the Emergency Closure for Friday through Sunday. +==== + +Below the Possible Emergency Closing message, two checkboxes appear: *Emergency* and *Process Immediately*. Both checkboxes must be manually selected in order to set the closure as an Emergency Closing. -By selecting the *Emergency* checkbox, the system will void any overdue fines incurred for that emergency closed day or days and push back any of the following dates to the next open day as determined by the library’s settings: +By selecting the *Emergency* checkbox, the system will void any overdue fines incurred for that emergency closed day(s) and push back any of the following dates to the next open day as determined by the library’s settings: * item due dates * shelf expire times * booking start times -image::emergency_closing/ECHClosingSnowDay.png[Create Emergency Closing] - -When selecting the *Process immediately* checkbox, Evergreen will enact the Emergency Closing changes immediately once the Emergency Closed Date information is saved. If Process immediately is not selected at the time of creation, staff will need to delete the original Emergency Closing and create a new one to make sure the Process immediately option is checked. If you go back to edit an entry to select the Process immediately checkbox, the Emergency processing will not occur. +When selecting the *Process immediately* checkbox, Evergreen will enact the Emergency Closing changes immediately once the Emergency Closed Date information is saved. Upon clicking *OK*, a progress bar will appear on-screen. After completion, the Closed Dates Editor screen will update, and under the Emergency Closing Processing Summary column, the number of affected/processed Circulations, Holds, and Reservations will be listed. image::emergency_closing/ECHLibraryClosingDone.png[Emergency Closing Processing Complete] [NOTE] -========================= -*NOTE* Processing can take some time, especially if you are creating an Emergency Closure at the system level and applying it to all branches. It's best to let it run and check back later to make sure that all circulations and holds processed. A successful processing is indicated by the green bar in the Emergency Closing Processing Summary column (shown in the screenshot above). If the bar is blue after processing, this indicates the processing did not complete correctly. -========================= +==== +Processing can take some time, especially if you are creating an Emergency Closure at the system level and applying it to all branches. It's best to let it run and check back later to make sure that all circulations and holds processed. A successful processing is indicated by the green bar in the Emergency Closing Processing Summary column (shown in the screenshot above). If the bar is blue after processing, this indicates the processing did not complete correctly. +==== -=== Editing Emergency Closings === +=== Editing an emergency closure === -If *Process immediately* is not selected during an Emergency Closing event creation, editing the existing Emergency Closing entry does not allow for proper processing. Staff will need to delete the original entry and create a new entry, making sure to select both the *Emergency Closing* and *Process immediately* options. +If *Process immediately* is not selected during an Emergency Closing event creation, staff can edit the closure entry, select the _Process immediately_ checkbox, and click *OK* to process the closure; however, the grid display does not update to show that the circulations and holds have been processed. -This caveat applies to editing the dates of an Emergency Closure as well. If the Emergency Closure dates need to be changed or extended, editing the existing entry does not process the circulations and holds properly. Either the original entry should be deleted and a new one created that encompasses the full date range, or a second Emergency Closure should be created to for the extended date range. +If the emergency closure dates need to be changed or extended, editing the existing entry _does not_ process the circulations and holds properly. Either the original entry should be deleted and a new one created that encompasses the full date range, or a second emergency closure should be created for the extended date range. -To edit the Reason field of an existing Emergency Closing event, go to *Actions -> Edit closing*. +== Deleting a closure == -image::emergency_closing/ECHEditClosing.png[Edit Closing] +To delete a regular or emergency closure, select the closure in the grid and go to *Actions -> Delete closing*. -A pop-up display will appear with the same format as creating a Closed Dates event. Once you make the changes, click *OK*. The Closed Dates Editor display will update. +image::emergency_closing/delete closing.png[Delete Closing] -image::emergency_closing/ECHEditClosingModal.png[Edit Closing Pop-Up] +== Permissions == + +To manage entries in the Closed Dates Editor, staff need the following permissions: + +* actor.org_unit.closed_date.create +* actor.org_unit.closed_date.update +* actor.org_unit.closed_date.delete + +To manage emergency closures, staff need the following additional permission: + +* EMERGENCY_CLOSING ----------------------------------------------------------------------- Summary of changes: .../admin/pages/emergency_closing_handler.adoc | 147 +++++++++++++-------- 1 file changed, 92 insertions(+), 55 deletions(-) hooks/post-receive -- Evergreen ILS

1 0

[GIT] Evergreen ILS branch rel_3_14 updated. 13ca38f1c81f84ed2953b2bb77d740fc4b9d5223
by Git User 18 Apr '25

18 Apr '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 13ca38f1c81f84ed2953b2bb77d740fc4b9d5223 (commit) from d9d7bbb28ef7a2a25e5bb4b5a77c7bbbb2705f35 (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 13ca38f1c81f84ed2953b2bb77d740fc4b9d5223 Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com> Date: Fri Apr 18 08:53:26 2025 -0400 Docs: LP2063846 screenshots Release-note: Fixes screenshot location for Emergency Closing Handler Signed-off-by: Susan Morrison <smorrison(a)georgialibraries.org> Signed-off-by: Andrea Buntz Neiman <abneiman(a)equinoxinitiative.org> diff --git a/docs/modules/admin/assets/images/emergency_closing/delete closing.png b/docs/modules/admin/assets/images/emergency_closing/delete closing.png new file mode 100644 index 0000000000..c75983665d Binary files /dev/null and b/docs/modules/admin/assets/images/emergency_closing/delete closing.png differ diff --git a/docs/modules/admin/assets/images/emergency_closing/example closing.png b/docs/modules/admin/assets/images/emergency_closing/example closing.png new file mode 100644 index 0000000000..c6f1f9385a Binary files /dev/null and b/docs/modules/admin/assets/images/emergency_closing/example closing.png differ diff --git a/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_section.png b/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_section.png new file mode 100644 index 0000000000..fb14e00961 Binary files /dev/null and b/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_section.png differ diff --git a/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_toast.png b/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_toast.png new file mode 100644 index 0000000000..4d598da279 Binary files /dev/null and b/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_toast.png differ diff --git a/docs/modules/admin/assets/images/emergency_closing/upcoming closure listing.png b/docs/modules/admin/assets/images/emergency_closing/upcoming closure listing.png new file mode 100644 index 0000000000..cc7852ce85 Binary files /dev/null and b/docs/modules/admin/assets/images/emergency_closing/upcoming closure listing.png differ ----------------------------------------------------------------------- Summary of changes: .../assets/images/emergency_closing/delete closing.png | Bin 0 -> 25476 bytes .../images/emergency_closing/example closing.png | Bin 0 -> 102446 bytes .../possibly emergency closure_section.png | Bin 0 -> 99042 bytes .../possibly emergency closure_toast.png | Bin 0 -> 11760 bytes .../emergency_closing/upcoming closure listing.png | Bin 0 -> 33499 bytes 5 files changed, 0 insertions(+), 0 deletions(-) create mode 100644 docs/modules/admin/assets/images/emergency_closing/delete closing.png create mode 100644 docs/modules/admin/assets/images/emergency_closing/example closing.png create mode 100644 docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_section.png create mode 100644 docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_toast.png create mode 100644 docs/modules/admin/assets/images/emergency_closing/upcoming closure listing.png hooks/post-receive -- Evergreen ILS

1 0

[GIT] Evergreen ILS branch main updated. e28cdfd3574b64dd9de0f76bd655a550028824d4
by Git User 18 Apr '25

18 Apr '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 e28cdfd3574b64dd9de0f76bd655a550028824d4 (commit) from 6e198a73c8264e0b3d44bedec219702f095ef599 (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 e28cdfd3574b64dd9de0f76bd655a550028824d4 Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com> Date: Fri Apr 18 08:53:26 2025 -0400 Docs: LP2063846 screenshots Release-note: Fixes screenshot location for Emergency Closing Handler Signed-off-by: Susan Morrison <smorrison(a)georgialibraries.org> Signed-off-by: Andrea Buntz Neiman <abneiman(a)equinoxinitiative.org> diff --git a/docs/modules/admin/assets/images/emergency_closing/delete closing.png b/docs/modules/admin/assets/images/emergency_closing/delete closing.png new file mode 100644 index 0000000000..c75983665d Binary files /dev/null and b/docs/modules/admin/assets/images/emergency_closing/delete closing.png differ diff --git a/docs/modules/admin/assets/images/emergency_closing/example closing.png b/docs/modules/admin/assets/images/emergency_closing/example closing.png new file mode 100644 index 0000000000..c6f1f9385a Binary files /dev/null and b/docs/modules/admin/assets/images/emergency_closing/example closing.png differ diff --git a/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_section.png b/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_section.png new file mode 100644 index 0000000000..fb14e00961 Binary files /dev/null and b/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_section.png differ diff --git a/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_toast.png b/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_toast.png new file mode 100644 index 0000000000..4d598da279 Binary files /dev/null and b/docs/modules/admin/assets/images/emergency_closing/possibly emergency closure_toast.png differ diff --git a/docs/modules/admin/assets/images/emergency_closing/upcoming closure listing.png b/docs/modules/admin/assets/images/emergency_closing/upcoming closure listing.png new file mode 100644 index 0000000000..cc7852ce85 Binary files /dev/null and b/docs/modules/admin/assets/images/emergency_closing/upcoming closure listing.png differ ----------------------------------------------------------------------- Summary of changes: .../assets/images/emergency_closing}/delete closing.png | Bin .../assets/images/emergency_closing}/example closing.png | Bin .../possibly emergency closure_section.png | Bin .../emergency_closing}/possibly emergency closure_toast.png | Bin .../images/emergency_closing}/upcoming closure listing.png | Bin 5 files changed, 0 insertions(+), 0 deletions(-) copy docs/modules/{local_admin/assets/images/emergency_closing_handler => admin/assets/images/emergency_closing}/delete closing.png (100%) copy docs/modules/{local_admin/assets/images/emergency_closing_handler => admin/assets/images/emergency_closing}/example closing.png (100%) copy docs/modules/{local_admin/assets/images/emergency_closing_handler => admin/assets/images/emergency_closing}/possibly emergency closure_section.png (100%) copy docs/modules/{local_admin/assets/images/emergency_closing_handler => admin/assets/images/emergency_closing}/possibly emergency closure_toast.png (100%) copy docs/modules/{local_admin/assets/images/emergency_closing_handler => admin/assets/images/emergency_closing}/upcoming closure listing.png (100%) hooks/post-receive -- Evergreen ILS

1 0

[GIT] Evergreen ILS branch rel_3_15 updated. dc96ae62278a0db84e7c3eae52a28c2afc0d3700
by Git User 18 Apr '25

18 Apr '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 dc96ae62278a0db84e7c3eae52a28c2afc0d3700 (commit) via 21c28fc2805f20d30797efb4d1d2428dceb8ac9a (commit) from ce881a4d0b9f5f2a559b47a192fa0c24645d4d48 (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 dc96ae62278a0db84e7c3eae52a28c2afc0d3700 Author: Jane Sandberg <sandbergja(a)gmail.com> Date: Fri Apr 18 06:12:22 2025 -0700 Docs (follow-up): image syntax Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com> diff --git a/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc b/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc index a33ce4c7d7..17c6e95b34 100644 --- a/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc +++ b/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc @@ -127,7 +127,7 @@ When the same information is input for each address type, any edits made to one . Click on the tab of the address you would like to make changes to. . Click the *Clone as New Address* button toward the bottom of the screen. + -image::describing_your_organization/clone as new address.png [Additional button text: This address is used for multiple address types.]] +image::describing_your_organization/clone as new address.png[Additional button text: This address is used for multiple address types.] + . Input the address updates. . Click *Save*. commit 21c28fc2805f20d30797efb4d1d2428dceb8ac9a Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com> Date: Tue Apr 15 11:31:26 2025 -0400 Docs: LP2078341 - Add Clone as New Address to describing_your_organization.adoc Related PR for new image: https://github.com/spmorrison/Evergreen/pull/17 Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com> diff --git a/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc b/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc index 852522ba85..a33ce4c7d7 100644 --- a/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc +++ b/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc @@ -122,9 +122,19 @@ The *Addresses* tab is broken out into four address types: *Physical Address*, * image::describing_your_organization/org_unit_addresses.png[Organizational unit addresses] +When the same information is input for each address type, any edits made to one type will carry over to the others. If the addresses differ, for example, if the physical address is not the same as the mailing address, use the *Clone as New Address* function. To do so: + +. Click on the tab of the address you would like to make changes to. +. Click the *Clone as New Address* button toward the bottom of the screen. ++ +image::describing_your_organization/clone as new address.png [Additional button text: This address is used for multiple address types.]] ++ +. Input the address updates. +. Click *Save*. + If you are offering geographic location service for your catalog, you can also set the longitude and latitude coordinates under any of the addresses screens. -If library settings have geographic location service enabled, then you could type in the address, click *Get Coordinates* for the fields to autofill. You can also set the coordinates manually. +If library settings have geographic location service enabled, then you could type in the address, click *Get Coordinates* for the fields to autofill. You can also set the coordinates manually. image::geo_coordinates.png[Coordinates Screenshot] ----------------------------------------------------------------------- Summary of changes: .../pages/describing_your_organization.adoc | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) hooks/post-receive -- Evergreen ILS

1 0

[GIT] Evergreen ILS branch rel_3_14 updated. d9d7bbb28ef7a2a25e5bb4b5a77c7bbbb2705f35
by Git User 18 Apr '25

18 Apr '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 d9d7bbb28ef7a2a25e5bb4b5a77c7bbbb2705f35 (commit) via ea8e6aee89c4419acd8b69a543e0bf9b7f35f1d7 (commit) from 6f74d28eb80561023fca72f28c081af6af118fdd (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 d9d7bbb28ef7a2a25e5bb4b5a77c7bbbb2705f35 Author: Jane Sandberg <sandbergja(a)gmail.com> Date: Fri Apr 18 06:12:22 2025 -0700 Docs (follow-up): image syntax Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com> diff --git a/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc b/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc index a33ce4c7d7..17c6e95b34 100644 --- a/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc +++ b/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc @@ -127,7 +127,7 @@ When the same information is input for each address type, any edits made to one . Click on the tab of the address you would like to make changes to. . Click the *Clone as New Address* button toward the bottom of the screen. + -image::describing_your_organization/clone as new address.png [Additional button text: This address is used for multiple address types.]] +image::describing_your_organization/clone as new address.png[Additional button text: This address is used for multiple address types.] + . Input the address updates. . Click *Save*. commit ea8e6aee89c4419acd8b69a543e0bf9b7f35f1d7 Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com> Date: Tue Apr 15 11:31:26 2025 -0400 Docs: LP2078341 - Add Clone as New Address to describing_your_organization.adoc Related PR for new image: https://github.com/spmorrison/Evergreen/pull/17 Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com> diff --git a/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc b/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc index 852522ba85..a33ce4c7d7 100644 --- a/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc +++ b/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc @@ -122,9 +122,19 @@ The *Addresses* tab is broken out into four address types: *Physical Address*, * image::describing_your_organization/org_unit_addresses.png[Organizational unit addresses] +When the same information is input for each address type, any edits made to one type will carry over to the others. If the addresses differ, for example, if the physical address is not the same as the mailing address, use the *Clone as New Address* function. To do so: + +. Click on the tab of the address you would like to make changes to. +. Click the *Clone as New Address* button toward the bottom of the screen. ++ +image::describing_your_organization/clone as new address.png [Additional button text: This address is used for multiple address types.]] ++ +. Input the address updates. +. Click *Save*. + If you are offering geographic location service for your catalog, you can also set the longitude and latitude coordinates under any of the addresses screens. -If library settings have geographic location service enabled, then you could type in the address, click *Get Coordinates* for the fields to autofill. You can also set the coordinates manually. +If library settings have geographic location service enabled, then you could type in the address, click *Get Coordinates* for the fields to autofill. You can also set the coordinates manually. image::geo_coordinates.png[Coordinates Screenshot] ----------------------------------------------------------------------- Summary of changes: .../pages/describing_your_organization.adoc | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) hooks/post-receive -- Evergreen ILS

1 0

[GIT] Evergreen ILS branch main updated. 6e198a73c8264e0b3d44bedec219702f095ef599
by Git User 18 Apr '25

18 Apr '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 6e198a73c8264e0b3d44bedec219702f095ef599 (commit) via ce9688ae86fee4b27c45b6ed3d3515634a9cca2e (commit) from fa547f885b21fcf253e78958941fdf13426dbcae (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 6e198a73c8264e0b3d44bedec219702f095ef599 Author: Jane Sandberg <sandbergja(a)gmail.com> Date: Fri Apr 18 06:12:22 2025 -0700 Docs (follow-up): image syntax Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com> diff --git a/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc b/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc index a33ce4c7d7..17c6e95b34 100644 --- a/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc +++ b/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc @@ -127,7 +127,7 @@ When the same information is input for each address type, any edits made to one . Click on the tab of the address you would like to make changes to. . Click the *Clone as New Address* button toward the bottom of the screen. + -image::describing_your_organization/clone as new address.png [Additional button text: This address is used for multiple address types.]] +image::describing_your_organization/clone as new address.png[Additional button text: This address is used for multiple address types.] + . Input the address updates. . Click *Save*. commit ce9688ae86fee4b27c45b6ed3d3515634a9cca2e Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com> Date: Tue Apr 15 11:31:26 2025 -0400 Docs: LP2078341 - Add Clone as New Address to describing_your_organization.adoc Related PR for new image: https://github.com/spmorrison/Evergreen/pull/17 Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com> diff --git a/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc b/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc index 852522ba85..a33ce4c7d7 100644 --- a/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc +++ b/docs/modules/admin_initial_setup/pages/describing_your_organization.adoc @@ -122,9 +122,19 @@ The *Addresses* tab is broken out into four address types: *Physical Address*, * image::describing_your_organization/org_unit_addresses.png[Organizational unit addresses] +When the same information is input for each address type, any edits made to one type will carry over to the others. If the addresses differ, for example, if the physical address is not the same as the mailing address, use the *Clone as New Address* function. To do so: + +. Click on the tab of the address you would like to make changes to. +. Click the *Clone as New Address* button toward the bottom of the screen. ++ +image::describing_your_organization/clone as new address.png [Additional button text: This address is used for multiple address types.]] ++ +. Input the address updates. +. Click *Save*. + If you are offering geographic location service for your catalog, you can also set the longitude and latitude coordinates under any of the addresses screens. -If library settings have geographic location service enabled, then you could type in the address, click *Get Coordinates* for the fields to autofill. You can also set the coordinates manually. +If library settings have geographic location service enabled, then you could type in the address, click *Get Coordinates* for the fields to autofill. You can also set the coordinates manually. image::geo_coordinates.png[Coordinates Screenshot] ----------------------------------------------------------------------- Summary of changes: .../pages/describing_your_organization.adoc | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) hooks/post-receive -- Evergreen ILS

1 0

[GIT] Evergreen ILS branch rel_3_15 updated. ce881a4d0b9f5f2a559b47a192fa0c24645d4d48
by Git User 18 Apr '25

18 Apr '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 ce881a4d0b9f5f2a559b47a192fa0c24645d4d48 (commit) via 655020656e77d7e4b2f79930e8e6c0e667503d5a (commit) from eabf63ae5e3496835f4660289cb9b858344d217a (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 ce881a4d0b9f5f2a559b47a192fa0c24645d4d48 Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com> Date: Tue Apr 15 11:20:22 2025 -0400 Docs: Screenshot for LP2078341 update Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com> diff --git a/docs/modules/admin_initial_setup/assets/images/describing_your_organization/clone as new address.png b/docs/modules/admin_initial_setup/assets/images/describing_your_organization/clone as new address.png new file mode 100644 index 0000000000..220cc5be7e Binary files /dev/null and b/docs/modules/admin_initial_setup/assets/images/describing_your_organization/clone as new address.png differ commit 655020656e77d7e4b2f79930e8e6c0e667503d5a Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com> Date: Fri Apr 4 16:23:23 2025 -0400 Docs: Update "org unit" terminology in borrowing_items.adoc Excluding when used in button/interface name Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com> diff --git a/docs/modules/admin_initial_setup/pages/borrowing_items.adoc b/docs/modules/admin_initial_setup/pages/borrowing_items.adoc index 5c6096a424..a249a86ae2 100644 --- a/docs/modules/admin_initial_setup/pages/borrowing_items.adoc +++ b/docs/modules/admin_initial_setup/pages/borrowing_items.adoc @@ -7,7 +7,7 @@ borrow what types of materials, for how long, and with what overdue fines. Individual elements of the circulation policies are configured using specific interfaces, and should be configured prior to setting up the circulation -policies. +policies. == Data elements that affect your circulation policies == @@ -22,7 +22,7 @@ circulation of an item. * *Circulation modifier* - Circulation modifiers are fields used to control circulation policies on specific groups of items. They can be added to items during the cataloging process. New circulation modifiers can be created in the -staff client by navigating to *Administration -> Server Administration -> Circulation +staff client by navigating to *Administration -> Server Administration -> Circulation Modifiers*. * *Circulate?* flag - The circulate? flag in the holdings editor can be set to False to disallow an item from circulating. @@ -55,7 +55,7 @@ image::borrowing_items/copy_locations_editor.png[screenshot of Shelving Location === User data === Finally, several characteristics of specific patrons can affect circulation -policies. You can modify these characteristics in a patron's record (*Search -> +policies. You can modify these characteristics in a patron's record (*Search -> Search for Patrons*, select a patron, choose *Edit* tab) or when registering a new patron (*Circulation -> Register Patron*). @@ -113,11 +113,11 @@ modifiers. * Configure the circulation limit sets by selecting *Administration -> Local Administration -> Circulation Limit Sets*. -* *Items Out* - The maximum number of items circulated to a patron at the same +* *Items Out* - The maximum number of items circulated to a patron at the same time. -* *Min Depth* - Enter the minimum depth in the org tree that +* *Min Depth* - Enter 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 +The minimum 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. @@ -158,9 +158,9 @@ particulars of a given circulation transaction, and 'result' columns, those that return the various parameters that are applied to the matching transaction. * Circulation policies by checkout library or owning library? - - If your policies should follow the rules of the library that checks out the + - If your policies should follow the rules of the library that checks out the item, select the checkout library as the *Org Unit (org_unit)*. - - If your policies should follow the rules of the library that owns the item, + - If your policies should follow the rules of the library that owns the item, select the consortium as the *Org Unit (org_unit)* and select the owning library as the *Item Circ Lib (copy_circ_lib)*. * Renewal policies can be created by setting *Renewals? (is_renewal)* to True. ----------------------------------------------------------------------- Summary of changes: .../clone as new address.png | Bin 0 -> 3768 bytes .../admin_initial_setup/pages/borrowing_items.adoc | 16 ++++++++-------- 2 files changed, 8 insertions(+), 8 deletions(-) create mode 100644 docs/modules/admin_initial_setup/assets/images/describing_your_organization/clone as new address.png hooks/post-receive -- Evergreen ILS

1 0

[GIT] Evergreen ILS branch rel_3_14 updated. 6f74d28eb80561023fca72f28c081af6af118fdd
by Git User 18 Apr '25

18 Apr '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 6f74d28eb80561023fca72f28c081af6af118fdd (commit) via fa8b9784880fbd1a38194a34c182137e329f0779 (commit) from 4d12d13a6000d59aa0c0a25516257fdc5364fc4b (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 6f74d28eb80561023fca72f28c081af6af118fdd Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com> Date: Tue Apr 15 11:20:22 2025 -0400 Docs: Screenshot for LP2078341 update Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com> diff --git a/docs/modules/admin_initial_setup/assets/images/describing_your_organization/clone as new address.png b/docs/modules/admin_initial_setup/assets/images/describing_your_organization/clone as new address.png new file mode 100644 index 0000000000..220cc5be7e Binary files /dev/null and b/docs/modules/admin_initial_setup/assets/images/describing_your_organization/clone as new address.png differ commit fa8b9784880fbd1a38194a34c182137e329f0779 Author: spmorrison <101879901+spmorrison(a)users.noreply.github.com> Date: Fri Apr 4 16:23:23 2025 -0400 Docs: Update "org unit" terminology in borrowing_items.adoc Excluding when used in button/interface name Signed-off-by: Jane Sandberg <sandbergja(a)gmail.com> diff --git a/docs/modules/admin_initial_setup/pages/borrowing_items.adoc b/docs/modules/admin_initial_setup/pages/borrowing_items.adoc index 5c6096a424..a249a86ae2 100644 --- a/docs/modules/admin_initial_setup/pages/borrowing_items.adoc +++ b/docs/modules/admin_initial_setup/pages/borrowing_items.adoc @@ -7,7 +7,7 @@ borrow what types of materials, for how long, and with what overdue fines. Individual elements of the circulation policies are configured using specific interfaces, and should be configured prior to setting up the circulation -policies. +policies. == Data elements that affect your circulation policies == @@ -22,7 +22,7 @@ circulation of an item. * *Circulation modifier* - Circulation modifiers are fields used to control circulation policies on specific groups of items. They can be added to items during the cataloging process. New circulation modifiers can be created in the -staff client by navigating to *Administration -> Server Administration -> Circulation +staff client by navigating to *Administration -> Server Administration -> Circulation Modifiers*. * *Circulate?* flag - The circulate? flag in the holdings editor can be set to False to disallow an item from circulating. @@ -55,7 +55,7 @@ image::borrowing_items/copy_locations_editor.png[screenshot of Shelving Location === User data === Finally, several characteristics of specific patrons can affect circulation -policies. You can modify these characteristics in a patron's record (*Search -> +policies. You can modify these characteristics in a patron's record (*Search -> Search for Patrons*, select a patron, choose *Edit* tab) or when registering a new patron (*Circulation -> Register Patron*). @@ -113,11 +113,11 @@ modifiers. * Configure the circulation limit sets by selecting *Administration -> Local Administration -> Circulation Limit Sets*. -* *Items Out* - The maximum number of items circulated to a patron at the same +* *Items Out* - The maximum number of items circulated to a patron at the same time. -* *Min Depth* - Enter the minimum depth in the org tree that +* *Min Depth* - Enter 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 +The minimum 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. @@ -158,9 +158,9 @@ particulars of a given circulation transaction, and 'result' columns, those that return the various parameters that are applied to the matching transaction. * Circulation policies by checkout library or owning library? - - If your policies should follow the rules of the library that checks out the + - If your policies should follow the rules of the library that checks out the item, select the checkout library as the *Org Unit (org_unit)*. - - If your policies should follow the rules of the library that owns the item, + - If your policies should follow the rules of the library that owns the item, select the consortium as the *Org Unit (org_unit)* and select the owning library as the *Item Circ Lib (copy_circ_lib)*. * Renewal policies can be created by setting *Renewals? (is_renewal)* to True. ----------------------------------------------------------------------- Summary of changes: .../clone as new address.png | Bin 0 -> 3768 bytes .../admin_initial_setup/pages/borrowing_items.adoc | 16 ++++++++-------- 2 files changed, 8 insertions(+), 8 deletions(-) create mode 100644 docs/modules/admin_initial_setup/assets/images/describing_your_organization/clone as new address.png hooks/post-receive -- Evergreen ILS

1 0