[Evergreen-general] Sharing plans for changing library selector in Angular staff catalog

[Galen Charlton]

Hi,

On Mon, Jan 22, 2024 at 12:09 PM Lussier, Kathy via Evergreen-general <
evergreen-general at list.evergreen-ils.org> wrote:
> #2 introduces new behavior that hasn't been used in previous staff
> catalogs. We could not think of a use case where an org unit
> should be invisible in the public catalog when performing a
> search, but should be visible in the staff catalog search. However,
>  if there is one, let us know so that we can add an option,
> most likely a global flag.

I can think of several:

- Library joining a consortium. Most any migration workflow I can imagine
will result in a period of at least a few days, and sometimes longer, where
an OU exists and has holdings attached to it but shouldn't be visible in
the OPAC, but where staff nonetheless need to be able to do staff-side
searches limited to that OU.
- Library opening a new branch with an opening day collection. This could
lead to an even longer period where the OU exists but is not yet ready to
be visible to patrons
- An explicitly hidden or resource collection

Does NOBLE have OUs that are completely disused?

Regards,

Galen
--
Galen Charlton
Implementation and IT Manager
Equinox Open Library Initiative
gmc at equinoxOLI.org
https://www.equinoxOLI.org
phone: 877-OPEN-ILS (673-6457)
direct: 770-709-5581
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-general/attachments/20240122/696339c9/attachment-0001.htm>