Hello Matthew You can have a public branch and a private branch. One way to do it is indicating in the Org Unit Configuration (Administration --> Server Administration --> Organizational Units) that the private branch is not OPAC visible and then it's holdings would not display in the OPAC. You could also create a set of shelving locations that are not OPAC visible if you have parts of the collection that are not visible while other shelving locations are visible.
You could also scope your OPAC in a way that is only showing the public branches, but that's beyond my skill set, so I will defer to others with that knowledge. Depending on the number of your locations you could consider having a system of public locations and another system for all the private locations. It all depends on how you want to lend materials and if your locations resource share. Some reference documentation: https://docs.evergreen-ils.org/docs/latest/admin_initial_setup/describing_your_organization.html https://docs.evergreen-ils.org/docs/latest/opac/visibility_on_the_web.html [cid:acac35c6-dadf-457b-96ff-1e56153407b5]Elizabeth Davis (she/her), Program Manager Pennsylvania Integrated Library System (PaILS) | SPARK (717) 256-1627 | [email protected]<mailto:[email protected]> support.sparkpa.org<https://support.sparkpa.org/> | [email protected]<mailto:[email protected]> ________________________________ From: matt.robertson--- via Evergreen-general <[email protected]> Sent: Thursday, January 22, 2026 1:21 AM To: [email protected] <[email protected]> Cc: [email protected] <[email protected]> Subject: [Evergreen-general] Separating catalog records by organisational unit We are currently testing a migration path to Evergreen and are looking for some advice on organisational unit structure. We have a publicly searchable catalog of items, however we also catalog other libraries materials where we need to keep the record separate from our public data. My initial thought was to create a public branch and a private branch, but I don't see any mechanism to indicate which branch unit a record is attached to. We're coming from Aleph which has several libraries setup and staff switch in the interface to the one they need to create the record for. I'd appreciate any information you can give me as I might be going about it in the wrong way and should be looking at another part of Evergreen to get the desired result _______________________________________________ Evergreen-general mailing list -- [email protected] To unsubscribe send an email to [email protected]
_______________________________________________ Evergreen-general mailing list -- [email protected] To unsubscribe send an email to [email protected]
