...
- 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:
a) LEVEL_ID – varchar2(40)(Primary key)
b) OBJ_ID – varchar2(Not Null)
c) VER_NBR – Number(8)(Not Null)
d) LEVEL_CD – varchar2(40)(Unique & Not Null)
e) LEVEL_NAME – varchar2(100)(Not Null)
f) PARENT_LEVEL – varchar2(40) (Nullable) - References OLE_LOCN_LEVEL_T.LEVEL_ID. Varchar2(40)
OLE_LOCN_T:
a) LOCN_ID - varchar2(40)(Primary Key)
b) OBJ_ID – varchar2(36)(Not Null)
c) VER_NBR – Number(8)(Not Null)
d) LOCN_CD – varchar2(40)(Unique & Not Null)
e) LOCN_NAME – varchar2(200)(Not Null)
f) LEVEL_ID - varchar2(40)(Not Null) - References OLE_LOCN_LEVEL_T.LEVEL_ID.
g) PARENT_LOCN_ID – varchar2(40)(Nullable)- References OLE_LOCN_T.LOCN_ID
Tests
*Issues :*
NA