Page Comparison

...

a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing patron Location record. 

b. Participants:

c. Framework: Rice2.x

...

a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing patron Location record. 

b. Participants:

c. Framework: Rice2.x

...

a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing patron Location Level record. 

b. Participants:

c. Framework: Rice2.x

...

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

...

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

...

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

• Create                                           
• Edit
• View(Inquiry)

     Location

• Create
• Edit
• View(Inquiry)

     Upload Locations

• Create

7. Services

8. Data Model

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

 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.

...

•       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:

...

 Tests :

     Location_UT.java

...