> 
> 
> 
> 
Note
Please click here for technical documentation.
The goals of the location system are to:
Model the organization’s structure clearly and accurately.
Support storing configuration information at the appropriate level of the organizational structure.
Allow libraries to establish policies for a location that apply to the organization’s components. This makes administration easier.
Support modeling relationships between parts of the organization.
Support consortial models.
The general idea is that a location’s setting or policy will automatically apply to the location’s children, unless the children override the setting.
Note
Only users with an OLE-PTRN Shelving Location Administrator or OLE-PTRN Location Administrator role may create and manage Locations.
 |
The OLE Location document includes the Add/Edit Location tab. The system automatically enters data into both the Old and New sections in this tab. Selected data fields are available for editing.
Add/Edit Location tab definition
|
Title |
Description |
|
Location Code |
The code to identify the location of the Instance Record. Each location must have a unique code with a maximum length of 40 characters. |
|
Location Name |
Required. The familiar title of the location. Maximum length is 100 characters. |
|
Location Level |
Required. The numerical representation of the location hierarchy. Locally configured, valid values are 1-5. |
|
Parent Location |
If the location level is NOT 1, chose a parent location by clicking on the magnifying glass icon. A valid parent location must be at a higher level than the new location being created. |
Each Location must have a Location Code, a Location Name, and a Location Level (Location Level Id). Each Location may have a Parent Location (displayed as the Location Name and, in brackets, the Location Code) of a location with a higher location level than its own level. Note the Parent Location does not have to be one defined at the next higher location level – it can be a location with any level higher than its own level. Its parent cannot be at the same level as itself or at a level below its own.
There is one other restriction when building an institution’s Locations. The lowest level of Locations must be defined using the Location Level 5 Id. Additionally, the Location Codes for Level 5 must be completely unique from any other Location Codes.
If your institution does not want to use Institution or Collection Levels, just Campuses, Libraries, and Shelving levels, you can leave the Location Level definitions alone. You construct your Locations and have the highest level be a 2, Libraries (level 3’s) with Level 2 parents, and Shelvings (Level 5’s) with level 2 or level 3 parents.
If your institution wants a different 3 level structure like Campus, Library, and Collection, you can do that as well although it may not look as clean as the previous example. Your Collections locations must use a Level 5 definition (lowest level must be Level 5). This is going to look a bit messy if the Location Level Code for Level ID 5 cannot be changed (must be left as “SHELVING”). Your institution could at least change the Level Name of the Level ID 5 record to read “Collection”. Then proceed building the Locations using Level Id’s 2, 3, and 5.
