more flexible,
> >> and (3) more maintainable.
> >>
> >> If we were/are voting, that'd definitely get my vote.
> >>
> >> Thanks!
> >>
> >> --
> >> Mike Rylander
> >> Research and Development Manager
> >> Equino
main "hide certain orgs" concept from the OP, on
>> >> balance, it definitely feels to me like a job for custom org trees
>> >> with a new "purpose" (the one existing purpose being: "opac"),
>> >> especially given the variable shape o
ler, (2) more flexible,
> >> and (3) more maintainable.
> >>
> >> If we were/are voting, that'd definitely get my vote.
> >>
> >> Thanks!
> >>
> >> --
> >> Mike Rylander
> >> Research and Development Manager
eted work on these related
>> > bugs:
>> >
>> > https://bugs.launchpad.net/evergreen/+bug/1949109 - Add Library Groups to
>> > Angular Staff Catalog
>> > https://bugs.launchpad.net/evergreen/+bug/1861701 - Angular staff catalog
>> > copy location group
; --------------
>>> *From:* Evergreen-general <
>>> evergreen-general-boun...@list.evergreen-ils.org> on behalf of Terran
>>> McCanna via Evergreen-general
>>> *Sent:* Tuesday, January 23, 2024 7:13 AM
>>> *To:* Evergreen Discussion
>> > 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
>> *From:* Evergreen-general <
>> evergreen-general-boun...@list.evergreen-ils.org> on behalf of Terran
>> McCanna via Evergreen-general
>> *Sent:* Tuesday, January 23, 2024 7:13 AM
>> *To:* Evergreen Discussion Group <
>> evergreen-ge
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 colum
t; ____________
>> From: Evergreen-general
>> on behalf of Terran McCanna via Evergreen-general
>>
>> Sent: Tuesday, January 23, 2024 7:13 AM
>> To: Evergreen Discussion Group
>> Cc: Terran McCanna
>> Subject: Re: [Evergreen-general
>
> --
> *From:* Evergreen-general <
> evergreen-general-boun...@list.evergreen-ils.org> on behalf of Terran
> McCanna via Evergreen-general
> *Sent:* Tuesday, January 23, 2024 7:13 AM
> *To:* Evergreen Discussion Group >
> *Cc:* Terra
t: Re: [Evergreen-general] Sharing plans for changing library selector in
Angular staff catalog
About disused Org Units - even after a branch closes completely and all of the
active materials and patrons have been moved off of it so we don't want it to
appear in most dropdown lists, we someti
Hi,
On Mon, Jan 22, 2024 at 5:57 PM Lussier, Kathy
wrote:
> 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.
Various options I see are.
[1] As Jason Stephe
About disused Org Units - even after a branch closes completely and all of
the active materials and patrons have been moved off of it so we don't want
it to appear in most dropdown lists, we sometimes still need to run reports
on it. It would be nice to have the option in the reporter to include
no
I like the idea of bringing shelving location groups to the staff client, yay
for feature parity!
I won't join in on the listing of potential reasons why #2 is necessary as
there are already several, but I would like to lean hard toward adding a
staff_visible flag to OUs or something similar be
: Evergreen-general On
Behalf Of Terran McCanna via Evergreen-general
Sent: Tuesday, January 23, 2024 10:06 AM
To: Evergreen Discussion Group
Cc: Terran McCanna
Subject: Re: [Evergreen-general] Sharing plans for changing library selector in
Angular staff catalog
This is an EXTERNAL email
PINES is also in favor of a staff visibility flag that is separate from the
OPAC-visibility flag.
On Mon, Jan 22, 2024 at 7:12 PM Jason Stephenson via Evergreen-general <
evergreen-general@list.evergreen-ils.org> wrote:
> Hi, all.
>
> On 1/22/24 17:57, Lussier, Kathy via Evergreen-general wrote:
Hi all,
Thanks for the use cases. We will definitely add an option for this, most
likely in the way that Jason suggested.
Kathy
--
Kathy Lussier
she/her
Executive Director
NOBLE: North of Boston Library Exchange
Danvers, MA
978-777-8844 x201
www.noblenet.org
On Tue, Jan 23, 2024 at 9:35 AM Jo
We have several locations that staff make use of but are hidden from the
public catalog.
ILL Locations - We have a central ILL OU for each region. That isn't
something that most staff need, only the ILL staff. We have a local
customization to hide ILL items from staff search results unless the I
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
rgreen-general On
Behalf Of Galen Charlton via Evergreen-general
Sent: Monday, January 22, 2024 2:46 PM
To: Evergreen Discussion Group
Cc: Galen Charlton
Subject: Re: [Evergreen-general] Sharing plans for changing library selector in
Angular staff catalog
[WARNING! This email came from outsi
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, in
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 catal
: [Evergreen-general] Sharing plans for changing library selector in
Angular staff catalog
This is an EXTERNAL email. Exercise caution. DO NOT open attachments or
click links from unknown senders or unexpected email.
Hi all,
NOBLE is proceeding with a project
-3691
From: Lussier, Kathy
Sent: Monday, January 22, 2024 12:34 PM
To: Frasur, Ruth
Cc: Evergreen Discussion Group
Subject: Re: [Evergreen-general] Sharing plans for changing library selector in
Angular staff catalog
This is an EXTERNAL email. Exercise caution. DO NOT open attachments or
.org> *On Behalf Of *Lussier,
> Kathy via Evergreen-general
> *Sent:* Monday, January 22, 2024 12:09 PM
> *To:* Evergreen Discussion Group >
> *Cc:* Lussier, Kathy
> *Subject:* [Evergreen-general] Sharing plans for changing library
> selector in Angul
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 the
26 matches
Mail list logo
