Hi, all.
On 1/22/24 17:57, Lussier, Kathy via Evergreen-general wrote:
Thanks Galen.
It sounds like an option is in order then, and I'm now wondering if a
global flag is appropriate or something that allows us to determine
staff catalog visibility on an OU by OU basis.
We talked about this
Another…
A library building is undergoing remodeling or repairs, during which part of
the collection has been stored in a way (or at a location) that is not readily
accessible to the public. But staff still needs to be able to see what is
there.
Have actually done that twice here in our
Thanks Galen.
It sounds like an option is in order then, and I'm now wondering if a
global flag is appropriate or something that allows us to determine staff
catalog visibility on an OU by OU basis.
Yes, NOBLE has OUs that left the consortium that are completely disused.
Another issue is that,
Hi,
On Mon, Jan 22, 2024 at 12:09 PM Lussier, Kathy via Evergreen-general <
evergreen-general@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
Kathy,
Just a question – in the NOBLE public catalog, I see where the library shelving
location groups appear in the Advanced Search. I notice that when a library
shelving location group is selected, it does not populate the included shelving
locations in the “location” field in the same way
Great! This is very intriguing and your use of shelving location groups is
also pretty inspiring.
Ruth Frasur Davis (she/they)
Coordinator
Evergreen Indiana Library Consortium
Evergreen Community Development Initiative
Indiana State Library
140 N. Senate Ave.
Indianapolis, IN 46204
(317)
Hi Ruth,
Great question! Yes, that piece is included in the more detailed
requirements, but was not mentioned in my email. It's the piece of the
project that we're willing to save for a future date if it turns out to be
too complex to incorporate in this project, but we're hoping we can make
Hi all,
NOBLE is proceeding with a project to make some changes to the library
selector in the Angular staff catalog. I'm sharing our requirements with
the community first to ensure the project doesn't conflict with any desired
behavior for the selector.
The full requirements are available at
