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 :Where Primary key, object ID and version number fields are generated automatically.
LEVEL_CODE
LEVEL_NAME
PARENT_LEVEL
INSTITUTION
Institution
NULL
CAMPUS
Campus
INSTITUTION
LIBRARY
Library
CAMPUS
COLLECTION
Collection
LIBRARY
SHELVING
Shelving Location
COLLECTION
2. OLE_LOCN_T:
...
Info | ||
---|---|---|
| ||
Info | ||
---|---|---|
| ||
OLE Location information will be maintained in the ole-rice2 schema and developed in the ole-rice2 application using the new KRAD maintenance doc framework. This will also be in line with the Instance Editor which has location component to it and being developed using the ole-rice2 framework. |
1. Location Maintenance (Create/Update)
a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Location record.
b. Participants:
c. Framework: Rice2.x
2. Location Search
a. KRAD Design: A simple KRAD maintenance document will be used to search an existing Location record.
b. Participants:
c. Framework: Rice2.x
3. Location Level Maintenance (Create/Update)
a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Location Level record.
b. Participants:
c. Framework: Rice2.x
4. Local Level Search
a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Location Level record.
b. Participants:
c. Framework: Rice2.x
5. Batch Ingest
a. KRAD Design: The ingest screen is going to be similar to the Staff Upload screen in OLE_Rice2.x. Its a simple KRAD form with a view.xml and a controller.
b. Participants:
c. Framework: Rice2.x
d. Workflow
6. Security
a. Roles:
- Operator - Create new Shelving Locations but not new Libraries.
- User- Create new Locations and Libraries for any campus.
- Shelving Location Administrator - Create and edit Shelving Locations.
- Location Administrator - Create and edit institutions, campuses, libraries and collections.Create, view and edit Location levels
b. Permissions to do the following on the below entities:
Location Level
a) Create
b) Edit
c) View(Inquiry)
Location
a) Create
b) Edit
c) View(Inquiry)
Upload Locations
a) Create/Update
7. Services
8. Data Model:The DM for Patron is going to reside in the Rice2.x Schema