Technical Specifications for the 25 Maintenance Documents to be created for the Instance Editor.
1) Completeness Maintenance Document Technical Specification
Rice2.x Framework
Completeness information will be maintained in the ole-rice2 schema and developed in the ole-rice2 application using the new KRAD maintenance doc framework.
1. Completeness Maintenance (Create/Update)
a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Completeness record.
b. Participants:
c. Framework: Rice2.x
2. Location Status Search
a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Completeness record.
b. Participants:
c. Framework: Rice2.x
3. Security
OLE_CAT namespace will be used for defining some Cataloging roles, and edocs
a. Roles:
- OLE_Cataloging_Admin - Create ,edit and provide blanket approve for Completeness
- Additional/Permitted Super User - Create ,edit and provide blanket approve for Completeness
- User - Can view the Completeness
b. Permissions to do the following on the below entities:
Completeness
a) Create
b) Edit
c) View(Inquiry)
d) Blanket Approve
7. Services
8. Data Model:The DM for Location Status is going to reside in the Rice2.x Schema
12) Notation Type Maintenance Document Technical Specification
Rice2.x Framework
Notation Type information will be maintained in the ole-rice2 schema and developed in the ole-rice2 application using the new KRAD maintenance doc framework.
1. Notation Type Maintenance (Create/Update)
a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Notation Type record.
b. Participants:
c. Framework: Rice2.x
2. Notation Type Search
a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Notation Type record.
b. Participants:
c. Framework: Rice2.x
3. Security
OLE_CAT namespace will be used for defining some Cataloging roles, and edocs
a. Roles:
- OLE_Cataloging_Admin - Create ,edit and provide blanket approve for Notation Type
- Additional/Permitted Super User - Create ,edit and provide blanket approve for Notation Type
- User - Can view the Notation Type
b. Permissions to do the following on the below entities:
Notation Type
a) Create
b) Edit
c) View(Inquiry)
d) Blanket Approve
7. Services
8. Data Model:The DM for Notation Type is going to reside in the Rice2.x Schema
13) Privacy Maintenance Document Technical Specification
Rice2.x Framework
Privacy information will be maintained in the ole-rice2 schema and developed in the ole-rice2 application using the new KRAD maintenance doc framework.
1.Privacy Maintenance (Create/Update)
a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Privacy record.
b. Participants:
c. Framework: Rice2.x
2. Privacy Search
a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Privacy record.
b. Participants:
c. Framework: Rice2.x
3. Security
OLE_CAT namespace will be used for defining some Cataloging roles, and edocs
a. Roles:
- OLE_Cataloging_Admin - Create ,edit and provide blanket approve for Privacy
- Additional/Permitted Super User - Create ,edit and provide blanket approve for Privacy
- User - Can view the Privacy
b. Permissions to do the following on the below entities:
Privacy
a) Create
b) Edit
c) View(Inquiry)
d) Blanket Approve