OLE Location Technical Specification

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 patron record. 

b. Participants:

c. Framework: Rice2.x

2. Location Search

a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing patron 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 patron 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 patron record. 

b. Participants:

c. Framework: Rice2.x

5. Batch Ingest

6. Security

7. Services

8. Data Model

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: 

1. Location Code.
2. Location Name.
3. Location Level.
4. 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

1. OLE_LOCN_LEVEL_T :
   | LEVEL_CODE | LEVEL_NAME | PARENT_LEVEL |

   INSTITUTION	Institution	NULL
   CAMPUS	Campus	INSTITUTION
   LIBRARY	Library	CAMPUS
   COLLECTION	Collection	LIBRARY
   SHELVING	Shelving Location	COLLECTION

   Where Primary key, object ID and version number fields are generated automatically.

   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.

  4.  Location permissions and Roles:

•       Locations belonging to each location level will have independent view, create and edit permissions. For instance, it will be possible to allow an operator to create new Shelving Locations but not new Libraries, etc.

•       It will not be possible to limit the scope of these permissions to specific locations right now. For instance, if a user has the 'create library' permission, the user can create libraries in any campus. It is desirable to add scopes to the permissions but this can wait.

•       Most user roles will have the view permission for locations. An independent "Shelving Location Administrator" role will be created with the create and edit permissions for shelving locations. A separate "Location Administrator" role will be created with the ability to add or edit institutions, campuses, libraries and collections.

•       Location levels will have a distinct view, create and edit permissions, but the "Shelving Location Administrator" role will have these permissions.

Data modeling

Tables involved as per the requirement given in LocationhandlinginOLE.pdf and JIRA No. OLE-2558 OLE_LOCN_LEVEL_T and OLE_LOCN_T

OLE_LOCN_LEVEL_T:

•   LEVEL_ID – varchar2(40)(Primary key)
•   OBJ_ID – varchar2(Not Null)
•   VER_NBR – Number(8)(Not Null)
•   LEVEL_CD – varchar2(40)(Unique & Not Null)
•   LEVEL_NAME – varchar2(100)(Not Null)
•   PARENT_LEVEL – varchar2(40) (Nullable) - References OLE_LOCN_LEVEL_T.LEVEL_ID. Varchar2(40)

 OLE_LOCN_T:

• LOCN_ID - varchar2(40)(Primary Key)
• OBJ_ID – varchar2(36)(Not Null)
• VER_NBR – Number(8)(Not Null)
• LOCN_CD – varchar2(40)(Unique & Not Null)
• LOCN_NAME – varchar2(200)(Not Null)
• LEVEL_ID  - varchar2(40)(Not Null) - References  OLE_LOCN_LEVEL_T.LEVEL_ID.
• PARENT_LOCN_ID – varchar2(40)(Nullable)- References  OLE_LOCN_T.LOCN_ID

 Tests :

     Location_UT.java

•    testSave
•    testFindMatching
•    testDelete

      LocationLevel_UT.java

•    testSave
•    testFindMatching
•    testDelete

  Issues :

                        NA