> Since we are a single system, am I right in thinking we don't need the System > layer in the hierarchy? I renamed the system level to a library name and > then added additional Consortium childs so that the new structure is: > Consortium -> Library
Hi Roma, that looks good to me. You just want to make sure that the org unit types you have defined make sense with your actual org unit hierarchy (your top-most org unit should have an org type with a depth of 0, and its immediate children should have an org type with a depth of 1, and the Can Have Volumes and Can Have Users flags on the org unit types should be adjusted). Some folks even do System -> Branch. Leaving room to grow without requiring drastic changes is always a good idea. Be sure to re-run autogen.sh after changing the org hierarchy! That updates some static javascript files used by the OPAC and staff client. -- Jason Etheridge | VP, Community Support and Advocacy | Equinox Software, Inc. / The Evergreen Experts | phone: 1-877-OPEN-ILS (673-6457) | email: [email protected] | web: http://www.esilibrary.com
