Great! Thanks for the insight! -- Don On Tue, Nov 6, 2012 at 10:42 AM, Rogan Hamby <[email protected]>wrote:
> > SCLENDS did the same thing. We came up with the same convention > independently. It also helps a lot when doing various manipulations of > report data. > > -- > > > Rogan Hamby > Manager, Rock Hill Library > 803-981-5853 > > York County Library System > http://www.yclibrary.org | http://www.facebook.com/yorkcountylibrary > > > "You can never get a cup of tea large enough or a book long enough to suit > me." > -- C.S. Lewis <http://www.goodreads.com/author/show/1069006.C_S_Lewis> > > > > > > On 11/6/12 10:38 AM, "Jason Etheridge" <[email protected]> wrote: > > >Don, I see no problems with that. One convention that PINES came up > >with (or inherited from their previous system) was to combine the > >system shortname with the branch shortname to expose a bit of the > >hierarchy at a glance when looking at a specific lib, and to reduce > >the chance of collision with shortnames. > > > >So for example, you may want to consider: > > > >ASLAN > >-> ATS > >->-> ATS-BLF > >->->-> ATS-BLF-SA > >->->-> ATS-BLF-BL > >->-> ATS-MDD > >-> AUL > >->-> AUL-DFK > >->->-> AUL-DFK-UA > >->-> AUL-AUF > > > >-- Jason > > >
