Intent
- Through User Interface - Create a "Location Levels" and "Location" Maintenance Screen under "System" panel of the "Maintenance" tab. And It will be possible to search for locations using an ordinary OLE search, using any of the following criteria:
Location Code.
Location Name.
Location Level.
Location Parent Code.
- Through Batch Upload – Locations can be loaded using "Upload Locations" link in "Batch" panel on the "Administration" tab, under a heading "Locations." XML file conforming to Location.xsd can be loaded using the link.
Participants
Collaborations
Configuration/Usage
- OLE_LOCN_LEVEL_T :
| LEVEL_CODE | LEVEL_NAME | PARENT_LEVEL |Where Primary key, object ID and version number fields are generated automatically.INSTITUTION
Institution
NULL
CAMPUS
Campus
INSTITUTION
LIBRARY
Library
CAMPUS
COLLECTION
Collection
LIBRARY
SHELVING
Shelving Location
COLLECTION
2. OLE_LOCN_T:
There is no default data for OLE_LOCN_T.
3. Through Batch Upload,Locations will be rejected if:
- A location's parent location references a location that does not exist.
- location's parent location matches a location at a lower level of the location hierarchy.
- A location's level code does not match a level code in the system.
Note that when loading locations that reference parent locations, the parent locations must already be in the system for the child locations to be created. If you try to load the child locations first, they will be rejected because OLE will not find their location codes. This implies that users need to order the load file so that the parent locations come before the child locations, or load the higher-level locations before the lower-level locations.