...
- KRIM_ROLE_T - Insert a record to create role
- KRIM_PERM_T - Insert a record to create permission for role created
- KRIM_ROLE_PERM_T - Insert a record to map role with permission
- KRIM_PERM_ATTR_DATA_T - Insert a record for permission details
- KRIM_ROLE_MBR_T - Insert a record to map a user with a role
4. XML Ingest for KRMS Builder:
Sample xml for creating Rules: Loan_Patron.xml
1) The above xml contains list of Agendas and Agenda can be selected based on Borrower Type (e.g:Faculty,etc).
2) Each Borrower Type will have Item Type as attributes (e.g:BOOK,AUDIOCD) which contains period - term (e.g:10-DAY,5-HOUR etc).
3) An Agenda contains list of Rules,each rule contains either a simple proposition or compound proposition.
a) A Simple proposition can be validated in two different ways namely
LHS & RHS validations (LHS-Term,RHS-Constant)
Function validations(Term as argument).
b) A Compound proposition is a collection of Simple proposition with an operand.
The Following rules are implemented:
a) Rule1 (barcodeStatusCheck) : Checks whether the patron barcode status is active.
b) Rule2 (membershipExpirationDateCheck) : Checks whether patron's expiration date exceeds current date.
c) Rule3 (borrowerLimitCheck) : Checks whether a number of items loaned exceeds 5.
d) Rule4 (itemAvailableCheck) : Checks item status availability.
c) Rule5 (itemUnavailableCheck) : Checks item status should not be MISSING,LOST etc..
d) Rule6 (itemDueDateCheck) : Checks whether due date is calculated or not, if not we have to manually enter due date.
5. Data Model
| Info | ||
|---|---|---|
| ||
The OLE_DLVR_ITEM_AVAIL_STAT_T table in the DM is a maint. table, values of which will be used to update the item information in docstore. This table doesn't have a direct co-relation to the Loan UI |
...
6. Performance Metrics
...
7. Sign-off
Review complete? No (Sr.Technical Architect) - Absent
Review with Core (Handoff #2)? Yes (OLE Core Team/S&A Team) - June 26th, 2012
...