Hi Matt, Doing a public and private branch can certainly work, especially if you have in house circulation rules you want to apply only to the private branch. If it is more of discrete collections you can also mark shelving locations non-opac visible, non-holdable, non-circulating.
Now, when you talk about keeping records separate it depends on what kinds of records. Bibs are "owned" by the entire installation. However, volume/call number records are scoped to org units (such as branches). Copies are also owned by branches. So, if you want to go the multi-branch route you can have volumes/call numbers owned by distinct branches, as well as the copies of course. On Thu, Jan 22, 2026 at 1:21 AM matt.robertson--- via Evergreen-general < [email protected]> wrote: > 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]
