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

Correct - here's a screenshot from our test system: [image: image.png] On Wed, Jan 24, 2024 at 4:18 PM Lussier, Kathy wrote: > Thanks for the links Andrea! To be clear, the copy location group work > adds those groups as a separate filter, rather than a part of the library > selector, right? >

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

Hi Mike! OP here, aka kmlussier. Thanks for adding your thoughts! My comments are below. To reiterate the reason we kept the library groups and location groups > selector separate from the library (org unit) selector, and also > combined them into one UI element: both library and location groups

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

Thanks for the links Andrea! To be clear, the copy location group work adds those groups as a separate filter, rather than a part of the library selector, right? Kathy -- Kathy Lussier she/her Executive Director NOBLE: North of Boston Library Exchange Danvers, MA 978-777-8844 x201

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

Hi all, This is a great discussion. Thanks for the feedback on this project. Unfortunately, I was away from email yesterday and am just catching up with these suggestions. I'll try to respond in the order that the messages were sent. [1] As Jason Stephenson suggested, adding a staff_visible

[Evergreen-general] Job Posting: Executive Director - Bibliomation, Inc.

*Executive Director – Bibliomation, Inc.* Bibliomation, Inc .’s Board of Directors seeks a creative, forward-thinking leader to serve as Executive Director to guide this dynamic organization as it advances its vision for member libraries and staff. The next Executive

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

Hi all, As Andrea mentioned, we've been working on functionality adjacent to the main topic of this thread for a bit. The pullrequest branch is attached to the Library Groups LP bug she pointed to, and you can find it here: