<div dir="ltr">PINES is also in favor of a staff visibility flag that is separate from the OPAC-visibility flag. <br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jan 22, 2024 at 7:12 PM Jason Stephenson via Evergreen-general <<a href="mailto:evergreen-general@list.evergreen-ils.org">evergreen-general@list.evergreen-ils.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi, all.<br>
<br>
On 1/22/24 17:57, Lussier, Kathy via Evergreen-general wrote:<br>
> Thanks Galen.<br>
> <br>
> It sounds like an option is in order then, and I'm now wondering if a <br>
> global flag is appropriate or something that allows us to determine <br>
> staff catalog visibility on an OU by OU basis.<br>
<br>
We talked about this internally at C/W MARS and thought that a field for <br>
staff catalog visibility on the org. unit would be appropriate.<br>
<br>
HtH,<br>
Jason<br>
<br>
> <br>
> Yes, NOBLE has OUs that left the consortium that are completely disused. <br>
> Another issue is that, in Massachusetts, we have very few multi-branch <br>
> libraries. Displaying a system level and the branch level in the catalog <br>
> search selector is redundant for all but four of our libraries. We also <br>
> need an org unit for our statewide sharing system, which is not <br>
> something that gets searched. There may be some other use cases, but, <br>
> overall, we've found it very useful to have control over how the org <br>
> units display in that specific library selector.<br>
> <br>
> Kathy<br>
> --<br>
> Kathy Lussier<br>
> she/her<br>
> Executive Director<br>
> NOBLE: North of Boston Library Exchange<br>
> Danvers, MA<br>
> 978-777-8844 x201<br>
> <a href="http://www.noblenet.org" rel="noreferrer" target="_blank">www.noblenet.org</a> <<a href="http://www.noblenet.org" rel="noreferrer" target="_blank">http://www.noblenet.org</a>><br>
> <br>
> <br>
> <br>
> <br>
> On Mon, Jan 22, 2024 at 5:46 PM Galen Charlton <<a href="mailto:gmc@equinoxoli.org" target="_blank">gmc@equinoxoli.org</a> <br>
> <mailto:<a href="mailto:gmc@equinoxoli.org" target="_blank">gmc@equinoxoli.org</a>>> wrote:<br>
> <br>
> Hi,<br>
> <br>
> On Mon, Jan 22, 2024 at 12:09 PM Lussier, Kathy via<br>
> Evergreen-general <<a href="mailto:evergreen-general@list.evergreen-ils.org" target="_blank">evergreen-general@list.evergreen-ils.org</a><br>
> <mailto:<a href="mailto:evergreen-general@list.evergreen-ils.org" target="_blank">evergreen-general@list.evergreen-ils.org</a>>> wrote:<br>
> > #2 introduces new behavior that hasn't been used in previous staff<br>
> > catalogs. We could not think of a use case where an org unit<br>
> > should be invisible in the public catalog when performing a<br>
> > search, but should be visible in the staff catalog search. However,<br>
> > if there is one, let us know so that we can add an option,<br>
> > most likely a global flag.<br>
> <br>
> I can think of several:<br>
> <br>
> - Library joining a consortium. Most any migration workflow I can<br>
> imagine will result in a period of at least a few days, and<br>
> sometimes longer, where an OU exists and has holdings attached to it<br>
> but shouldn't be visible in the OPAC, but where staff nonetheless<br>
> need to be able to do staff-side searches limited to that OU.<br>
> - Library opening a new branch with an opening day collection. This<br>
> could lead to an even longer period where the OU exists but is not<br>
> yet ready to be visible to patrons<br>
> - An explicitly hidden or resource collection<br>
> <br>
> Does NOBLE have OUs that are completely disused?<br>
> <br>
> Regards,<br>
> <br>
> Galen<br>
> --<br>
> Galen Charlton<br>
> Implementation and IT Manager<br>
> Equinox Open Library Initiative<br>
> gmc@equinoxOLI.org<br>
> <a href="https://www.equinoxOLI.org" rel="noreferrer" target="_blank">https://www.equinoxOLI.org</a> <<a href="https://www.equinoxOLI.org" rel="noreferrer" target="_blank">https://www.equinoxOLI.org</a>><br>
> phone: 877-OPEN-ILS (673-6457)<br>
> direct: 770-709-5581<br>
> <br>
> <br>
> _______________________________________________<br>
> Evergreen-general mailing list<br>
> <a href="mailto:Evergreen-general@list.evergreen-ils.org" target="_blank">Evergreen-general@list.evergreen-ils.org</a><br>
> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a><br>
_______________________________________________<br>
Evergreen-general mailing list<br>
<a href="mailto:Evergreen-general@list.evergreen-ils.org" target="_blank">Evergreen-general@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a><br>
</blockquote></div>