| 2012-03-13 18:36:07 |
Bill Erickson |
description |
References :
http://masslnc.cwmars.org/node/2516
http://www.esilibrary.com/esi/docs/?p=841
This bug addresses two, tightly linked features. Feature one supports non-inherited org unit hiding. The goal is to allow hiding nodes in the org unit tree without hiding the child nodes. Among other things, this allows systems to insert org units into the org unit tree for grouping/routing/policy/etc. without exposing that information to the OPAC. This is managed by a new config.global_flag "opac.org_unit.non_inheritied_visibility" which, when enabled, will cause all opac_visible org units to display in the library selector even if their parent org units are hidden.
Feature two aims to support org unit sibling sort order within the tpac library selector. This allows staff to define the display order of each branch as compared to its sibling branches. For example, you could configure a stock Evergreen instance to look like:
CONS
- SYS1
-- BR2
-- BR1
...
Depending on permissions, any level of the tree (that has a parent) can be manually sorted. Sorting is managed via a new admin interface (Admin -> Local Admin -> Library Sort Order).
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/berick/org-unit-opac-visibility-and-sorting |
References :
http://masslnc.cwmars.org/node/2516
http://www.esilibrary.com/esi/docs/?p=841
This bug addresses two tightly linked features. Feature one supports non-inherited org unit hiding. The goal is to allow hiding nodes in the org unit tree without hiding the child nodes. Among other things, this allows systems to insert org units into the org unit tree for grouping/routing/policy/etc. without exposing that information to the OPAC. This is managed by a new config.global_flag "opac.org_unit.non_inheritied_visibility" which, when enabled, will cause all opac_visible org units to display in the library selector even if their parent org units are hidden.
Feature two aims to support org unit sibling sort order within the tpac library selector. This allows staff to define the display order of each branch as compared to its sibling branches. For example, you could configure a stock Evergreen instance to look like:
CONS
- SYS1
-- BR2
-- BR1
...
Depending on permissions, any level of the tree (that has a parent) can be manually sorted. Sorting is managed via a new admin interface (Admin -> Local Admin -> Library Sort Order).
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/berick/org-unit-opac-visibility-and-sorting |
|
