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 62a47b510472209ae884c1828f256a83036afe03 (commit) from eafb167a74e4faa0d544675a449de2f13f9f8048 (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 62a47b510472209ae884c1828f256a83036afe03 Author: spmorrison <101879901+spmorrison@users.noreply.github.com> Date: Thu Jul 3 14:20:15 2025 -0400 Docs: Update "org unit" terms in oaipmh.adoc Signed-off-by: Jane Sandberg <js7389@princeton.edu> diff --git a/docs/modules/admin_initial_setup/pages/oaipmh.adoc b/docs/modules/admin_initial_setup/pages/oaipmh.adoc index a85d96e06f..2b159d0233 100644 --- a/docs/modules/admin_initial_setup/pages/oaipmh.adoc +++ b/docs/modules/admin_initial_setup/pages/oaipmh.adoc @@ -24,11 +24,11 @@ Sets for authority records are based on the browse axis of the heading for the r All generated Sets for bib records currently test for effective search visibility on the three described components. -In order to retrieve item data from a specific branch of the org tree, a harvester must use a Set that contains `COPIES:`. The hierarchical shortnames of the org units follow the colon, so in a freshly installed system a Set with the setSpec of `COPIES:CONS:SYS2:BR3` will retrieve all bib records that have visible copies at BR3, and include only the item data for that org unit. +In order to retrieve item data from a specific branch of the org tree, a harvester must use a Set that contains `COPIES:`. The hierarchical shortnames of the organizational units follow the colon, so in a freshly installed system a Set with the setSpec of `COPIES:CONS:SYS2:BR3` will retrieve all bib records that have visible copies at BR3, and include only the item data for that organizational unit. -To retrieve records with Located URIs, which behave in the hierarchical reverse of copies by limiting display to those org units "inside" the branch of the tree where the licensing "lives", a harvester should supply a setSpec with an org unit shortname that would display the Located URI. For example: `LURIS:CONS:SYS2:BR3` +To retrieve records with Located URIs, which behave in the hierarchical reverse of copies by limiting display to those organizational units "inside" the branch of the tree where the licensing "lives", a harvester should supply a setSpec with an organizational unit shortname that would display the Located URI. For example: `LURIS:CONS:SYS2:BR3` -Note: the `LURI:` org unit is also used to restrict any item data that may be available for LURI-filtered records. +Note: the `LURI:` organizational unit is also used to restrict any item data that may be available for LURI-filtered records. To retrieve records that are in a transcendent bib source, a harvester can used a setSpec starting with `SOURCES:` followed by the source name. ----------------------------------------------------------------------- Summary of changes: docs/modules/admin_initial_setup/pages/oaipmh.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) hooks/post-receive -- Evergreen ILS