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]
