Versions Compared

Version Old Version 33 New Version 34
Changes made by

Prem Kumar Balu (Unlicensed)

Prem Kumar Balu (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Wiki Markup
Technical Specifications for the 25 Maintenance Documents to be created for the Instance Editor.

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2806|https://jira.kuali.org/browse/OLE-2806]

{info}

h2. *1)* Location Status *Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Location Status information will be maintained in the ole-rice2 schema and   developed  in   the ole-rice2 application using the new KRAD maintenance   doc   framework.
{info}

h4.


h4. 1. Location Status Maintenance (Create/Update/Search)

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

    b. Participants:

         OleLocationStatus.xml

         OleLocationStatusMaintenanceDocument.xml

         OleLocationStatus.java

    c. Framework: Rice2.x


h4. 2. 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 Location Status
* Additional/Permitted Super User - 	Create ,edit and provide blanket approve for Location Status
* User - Can view the Location Status

    b. Permissions to do the following on the below entities:

       Location Status

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

h4. 3. OJB-Mapping

&nbsp;&nbsp;&nbsp; <class-descriptor table="ole_cat_loc_status_t">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <field-descriptor name="locationStatusId" column="LOC_STATUS_ID" jdbc-type="VARCHAR" primarykey="true" autoincrement="true" sequence-name="ole_cat_loc_status_s" />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <field-descriptor name="locationStatusCode" column="LOC_STATUS_CD" jdbc-type="VARCHAR" />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <field-descriptor name="locationStatusName" column="LOC_STATUS_NM" jdbc-type="VARCHAR" />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <field-descriptor name="objectId" column="OBJ_ID" jdbc-type="VARCHAR" index="true"/>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <field-descriptor name="versionNumber" column="VER_NBR" jdbc-type="BIGINT" locking="true" />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <field-descriptor name="source" column="SRC" jdbc-type="VARCHAR" />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <field-descriptor name="sourceDate" column="SRC_DT" jdbc-type="DATE" />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <field-descriptor name="active" column="ROW_ACT_IND" jdbc-type="VARCHAR"
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; conversion="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion" />
&nbsp;&nbsp;&nbsp; </class-descriptor>

h4. 4. Services


h4. 5. Workflow xml

&nbsp;&nbsp;&nbsp;&nbsp; <documentType>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <name>OLE_LSMD</name>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <parent>RiceDocument</parent>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <description>Ole Location Status</description>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <label>Ole Location Status</label>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <postProcessorName>org.kuali.rice.krad.workflow.postprocessor.KualiPostProcessor</postProcessorName>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <superUserGroupName namespace="KR-WKFLW">WorkflowAdmin</superUserGroupName>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <blanketApproveGroupName namespace="KR-WKFLW">WorkflowAdmin</blanketApproveGroupName>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <defaultExceptionGroupName namespace="KR-WKFLW">WorkflowAdmin</defaultExceptionGroupName>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <docHandler>${kr.krad.url}/maintenance?methodToCall=docHandler</docHandler>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <active>true</active>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <routingVersion>2</routingVersion>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <routePaths>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <routePath>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <start name="Initiated" />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </routePath>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </routePaths>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <routeNodes>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <start name="Initiated">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <activationType>P</activationType>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </start>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </routeNodes>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </documentType>


h4. 6. Data Model:The DM for Location Status is going to reside in the Rice2.x Schema

h2. *2)* Type of Ownership *Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Type of Ownership information will be maintained in the ole-rice2 schema and  developed  in   the ole-rice2 application using the new KRAD maintenance  doc   framework.
{info}


{color:#000000}{*}1. Type Of Ownership Maintenance (Create/Update)*{color}

{color:#000000}&nbsp;&nbsp;&nbsp;{color} {color:#000000}a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Type Of Ownership record.{color}

{color:#000000}&nbsp;&nbsp;&nbsp; b. Participants:{color}

{color:#000000}&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x{color}

{color:#000000}{*}2. Type Of Ownership Search{*}{color}

{color:#000000}&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Type Of Ownership record.{color}

{color:#000000}&nbsp;&nbsp;&nbsp; b. Participants:{color}

{color:#000000}&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x{color}

{color:#000000}{*}3. Security{*}{color}

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

{color:#000000}&nbsp;&nbsp;&nbsp;{color} {color:#000000}a. Roles:{color}
* {color:#000000}OLE_Cataloging_Admin 	- Create ,edit and provide blanket approve for Type Of Ownership{color}
* {color:#000000}Additional/Permitted 	Super User - Create ,edit and provide blanket approve forType Of 	Ownership{color}
* {color:#000000}User 	- Can view the Type Of Ownership{color}

{color:#000000}&nbsp;&nbsp;&nbsp;{color} {color:#000000}b. Permissions to do the following on the below entities:{color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type Of Ownership{color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#000000}a) Create{color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#000000}b) Edit{color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color}&nbsp; {color:#000000}c) View(Inquiry){color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color}&nbsp; {color:#000000}d) Blanket Approve{color}

{color:#000000}{*}7. Services{*}{color}

{color:#000000}{*}8. Data Model:The DM for Type Of Ownership is going to reside in the Rice2.x Schema{*}{color}\\

h2. *3) Action Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Action information will be maintained in the ole-rice2 schema and  developed in   the ole-rice2 application using the new KRAD maintenance  doc  framework.
{info}


{color:#000000}{*}1. Action Maintenance (Create/Update)*{color}

{color:#000000}&nbsp;&nbsp;&nbsp;{color} {color:#000000}a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Action record.{color}

{color:#000000}&nbsp;&nbsp;&nbsp; b. Participants:{color}

{color:#000000}&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x{color}

{color:#000000}{*}2. Action Search{*}{color}

{color:#000000}&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Action record.{color}

{color:#000000}&nbsp;&nbsp;&nbsp; b. Participants:{color}

{color:#000000}&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x{color}

{color:#000000}{*}3. Security{*}{color}

&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

{color:#000000}&nbsp;&nbsp;{color} {color:#000000}a. Roles:{color}
* {color:#000000}OLE_Cataloging_Admin 	- Create ,edit and provide blanket approve for Action{color}
* {color:#000000}Additional/Permitted 	Super User - Create ,edit and provide blanket approve for Action{color}
* {color:#000000}User 	- Can view the Action{color}

{color:#000000}&nbsp;&nbsp;{color} {color:#000000}b. Permissions to do the following on the below entities:{color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#000000}Action{color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#000000}a) Create{color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#000000}b) Edit{color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#000000}c) View(Inquiry){color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#000000}d) Blanket Approve{color}



{color:#000000}{*}7. Services{*}{color}

{color:#000000}{*}8. Data Model:The DM for Action is going to reside in the Rice2.x Schema{*}{color}\\

h2. *4) Access Method Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Access Method information will be maintained in the ole-rice2 schema and developed in   the ole-rice2 application using the new KRAD maintenance doc  framework.
{info}


{color:#000000}{*}1. Access Method Maintenance (Create/Update)*{color}

{color:#000000}&nbsp;&nbsp;&nbsp;{color} {color:#000000}a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Access Method record.{color}

{color:#000000}&nbsp;&nbsp;&nbsp; b. Participants:{color}

{color:#000000}&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x{color}

{color:#000000}{*}2. Access Method Search{*}{color}

{color:#000000}&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Access Method record.{color}

{color:#000000}&nbsp;&nbsp;&nbsp; b. Participants:{color}

{color:#000000}&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x{color}

{color:#000000}{*}3. Security{*}{color} &nbsp;&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

{color:#000000}&nbsp;&nbsp;&nbsp; a. Roles:{color}
* {color:#000000}OLE_Cataloging_Admin 	- Create ,edit and provide blanket approve for Access Method{color}
* {color:#000000}Additional/Permitted 	Super User - Create ,edit and provide blanket approve for Access 	Method{color}
* {color:#000000}User 	- Can view the Access Method{color}

{color:#000000}&nbsp;&nbsp;{color} {color:#000000}b. Permissions to do the following on the below entities:{color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#000000}Access Method{color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#000000}a) Create{color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#000000}b) Edit{color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#000000}c) View(Inquiry){color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#000000}d) Blanket Approve{color}

{color:#000000}{*}7. Services{*}{color}

{color:#000000}{*}8. Data Model:The DM for Access Method is going to reside in the Rice2.x Schema{*}{color}

h2. *5) Acquisition Method Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Acquisition Method information will be maintained in the ole-rice2 schema and  developed in   the ole-rice2 application using the new KRAD maintenance  doc  framework.
{info}

{color:#000000}{*}1. Acquisition Method Maintenance (Create/Update)*{color}

{color:#000000}&nbsp;&nbsp;&nbsp;{color} {color:#000000}a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Acquisition Method record.{color}

{color:#000000}&nbsp;&nbsp;&nbsp; b. Participants:{color}

{color:#000000}&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x{color}

{color:#000000}{*}2. Acquisition Method Search{*}{color}

{color:#000000}&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Acquisition Method record.{color}

{color:#000000}&nbsp;&nbsp;&nbsp; b. Participants:{color}

{color:#000000}&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x{color}

{color:#000000}{*}3. Security{*}{color}

&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs


{color:#000000}&nbsp;&nbsp;{color} {color:#000000}a. Roles:{color}
* {color:#000000}OLE_Cataloging_Admin 	- Create ,edit and provide blanket approve for Acquisition Method{color}
* {color:#000000}Additional/Permitted 	Super User - Create ,edit and provide blanket approve for 	Acquisition Method{color}
* {color:#000000}User 	- Can view the Acquisition Method{color}

{color:#000000}&nbsp;&nbsp;{color} {color:#000000}b. Permissions to do the following on the below entities:{color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#000000}Acquisition Method{color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#000000}a) Create{color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#000000}b) Edit{color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#000000}c) View(Inquiry){color}

{color:#000000}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{color} {color:#000000}d) Blanket Approve{color}

{color:#000000}{*}7. Services{*}{color}

{color:#000000}{*}8. Data Model:The DM for Acquisition Method is going to reside in the Rice2.x Schema{*}{color}\\

h2. *6) Completeness Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=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.
{info}

h4. 1. Completeness Maintenance (Create/Update)

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance&nbsp;document will be used to create and update a new or an existing Completeness record.&nbsp;

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x

h4. 2. Location Status Search

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance&nbsp;document will be used to create and update a new or an existing Completeness record.&nbsp;

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x

h4. 3. Security

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; 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

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp; &nbsp; &nbsp; &nbsp; Completeness

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; d) Blanket Approve

h4. 7. Services


h4. 8. Data Model:The DM for Location Status is going to reside in the Rice2.x Schema&nbsp;


h2. *7)&nbsp; ELA Relationship Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
ELA Relationship information will be maintained in the ole-rice2 schema and developed in   the ole-rice2 application using the new KRAD maintenance doc  framework.
{info}


*1. ElARelationship Maintenance (Create/Update)*

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance&nbsp;document will be used to create and update a new or an existing ElARelationship record.&nbsp;

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x

 *2. ElARelationship Search*

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance&nbsp;document will be used to create and update a new or an existing ElARelationship record.&nbsp;

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x

*3. Security*

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; a. Roles:
* OLE_Cataloging_Admin 	- Create ,edit and provide blanket approve for ElARelationship
* Additional/Permitted 	Super User - Create ,edit and provide blanket approve for ElARelationship
* User 	- Can view the ElARelationship

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp; &nbsp; &nbsp;&nbsp;ElARelationship

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; d) Blanket Approve
\\

*7. Services*

*8. Data Model:The DM for ElARelationship is going to reside in the Rice2.x Schema*

h2. *8) Encoding Level Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Encoding Level information will be maintained in the ole-rice2 schema and developed in   the ole-rice2 application using the new KRAD maintenance doc  framework.
{info}

*1. EncodingLevel Maintenance (Create/Update)*

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance&nbsp;document will be used to create and update a new or an existing Encoding Level record.&nbsp;

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x

 *2. EncodingLevel Search*

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance&nbsp;document will be used to create and update a new or an existing Encoding Level record.&nbsp;

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x

*3. Security*

&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp; a. Roles:
* OLE_Cataloging_Admin 	- Create ,edit and provide blanket approve for Encoding Level
* Additional/Permitted 	Super User - Create ,edit and provide blanket approve for Encoding Level
* User 	- Can view the Encoding Level

&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp; &nbsp; &nbsp;&nbsp;Encoding Level

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; d) Blanket Approve
\\

*7. Services*

*8. Data Model:The DM for EncodingLevel is going to reside in the Rice2.x Schema*

h2. *9) Field Encoding Level Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Field encoding level information will be maintained in the ole-rice2 schema and developed in   the ole-rice2 application using the new KRAD maintenance doc  framework.
{info}


*1. Field Encoding Level Maintenance (Create/Update)*

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance&nbsp;document will be used to create and update a new or an existing Field Encoding Level record.&nbsp;

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x

 *2. Field Encoding Level Search*

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance&nbsp;document will be used to create and update a new or an existing Field Encoding Level record.&nbsp;

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x

*3. Security*

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; a. Roles:
* OLE_Cataloging_Admin 	- Create ,edit and provide blanket approve for Field Encoding Level
* Additional/Permitted 	Super User - Create ,edit and provide blanket approve for Field 	Encoding Level
* User 	- Can view the Field Encoding Level

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; Field Encoding Level

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; d) Blanket Approve
\\
\\

*7. Services*

*8. Data Model:The DM for Field Encoding Level is going to reside in the Rice2.x Schema*

h2. *10) General Retention Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}
{info:title=Rice2.x Framework}
General Retention information will be maintained in the ole-rice2 schema and  developed in    the ole-rice2 application using the new KRAD maintenance  doc   framework.
{info}

*1. General Retention Policy Maintenance (Create/Update)*

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance&nbsp;document will be used to create and update a new or an existing General Retention Policy record.&nbsp;

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x

 *2. Country Codes Search*

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance&nbsp;document will be used to create and update a new or an existing General Retention Policy record.&nbsp;

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp;&nbsp; c. Framework: Rice2.x

*3. Security*

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; a. Roles:
* OLE_Cataloging_Admin 	- Create ,edit and provide blanket approve for General Retention Policy
* Additional/Permitted 	Super User - Create ,edit and provide blanket approve for General 	Retention Policy
* User 	- Can view the General Retention Policy

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; General Retention Policy

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; d) Blanket Approve
\\

*7. Services*

*8. Data Model:The DM for General Retention Policy is going to reside in the Rice2.x Schema*

h2. *11)* Lending Policy *Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Lending Policy information will be maintained in the ole-rice2 schema and  developed  in   the ole-rice2 application using the new KRAD maintenance  doc   framework.
{info}


h4.


h4. 1. Lending Policy Maintenance (Create/Update)

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used  to create and update a new or an existing Lending Policy record.

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp; &nbsp; c. Framework: Rice2.x

h4. 2. Lending Policy Search

&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to  create and update a new or an existing Lending Policy record.

&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp; c. Framework: Rice2.x

h4. 3. Security

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; a. Roles:
* OLE_Cataloging_Admin - Create 	,edit and provide blanket approve for Lending Policy
* Additional/Permitted Super User - 	Create ,edit and provide blanket approve for Lending Policy
* User - Can view the Lending Policy

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Lending Policy

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; d) Blanket Approve

h4. 7. Services


h4. 8. Data Model:The DM for Lending Policy is going to reside in the Rice2.x Schema


h2. *12)* Notation Type *Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=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.
{info}

h4.


h4. 1. Notation Type Maintenance (Create/Update)

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used    to create and update a new or an existing Notation Type record.

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp; &nbsp; c. Framework: Rice2.x

h4. 2. Notation Type Search

&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to    create and update a new or an existing Notation Type record.

&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp; c. Framework: Rice2.x

h4. 3. Security

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; 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

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Notation Type

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; d) Blanket Approve

h4. 7. Services


h4. 8. Data Model:The DM for Notation Type is going to reside in the Rice2.x Schema


h2. *13)* Privacy *Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=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.
{info}

h4.


h4. 1. Privacy Maintenance (Create/Update)

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used    to create and update a new or an existing Privacy record.

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp; &nbsp; c. Framework: Rice2.x

h4. 2. Privacy Search

&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to    create and update a new or an existing Privacy record.

&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp; c. Framework: Rice2.x

h4. 3. Security

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; 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

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Privacy

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; d) Blanket Approve

h4. 7. Services


h4. 8. Data Model:The DM for Privacy is going to reside in the Rice2.x Schema


h2. *14)* Receipt Status *Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Receipt Status information will be maintained in the ole-rice2 schema and    developed  in   the ole-rice2 application using the new KRAD maintenance    doc   framework.
{info}

h4.


h4. 1. Receipt Status Maintenance (Create/Update)

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used    to create and update a new or an existing Receipt Status record.

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp; &nbsp; c. Framework: Rice2.x

h4. 2. Receipt Status Search

&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to    create and update a new or an existing Receipt Status record.

&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp; c. Framework: Rice2.x

h4. 3. Security

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; a. Roles:
* OLE_Cataloging_Admin - Create 	,edit and provide blanket approve for Receipt Status
* Additional/Permitted Super User - 	Create ,edit and provide blanket approve for Receipt Status
* User - Can view the Receipt Status

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Receipt Status

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; d) Blanket Approve

h4. 7. Services


h4. 8. Data Model:The DM for Receipt Status is going to reside in the Rice2.x Schema


h2. *15)* Record Type *Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Record Type information will be maintained in the ole-rice2 schema and    developed  in   the ole-rice2 application using the new KRAD maintenance    doc   framework.
{info}

h4.


h4. 1. Record Type Maintenance (Create/Update)

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used    to create and update a new or an existing Record Type record.

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp; &nbsp; c. Framework: Rice2.x

h4. 2. Record Type Search

&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to    create and update a new or an existing Record Type record.

&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp; c. Framework: Rice2.x

h4. 3. Security

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; a. Roles:
* OLE_Cataloging_Admin - Create 	,edit and provide blanket approve for Record Type
* Additional/Permitted Super User - 	Create ,edit and provide blanket approve for Record Type
* User - Can view the Record Type

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Record Type

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; d) Blanket Approve

h4. 7. Services


h4. 8. Data Model:The DM for Record Type is going to reside in the Rice2.x Schema


h2. *16)* Reproduction Policy *Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Reproduction Policy information will be maintained in the ole-rice2 schema and    developed  in   the ole-rice2 application using the new KRAD maintenance    doc   framework.
{info}

h4.


h4. 1. Reproduction Policy Maintenance (Create/Update)

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used    to create and update a new or an existing Reproduction Policy record.

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp; &nbsp; c. Framework: Rice2.x

h4. 2. Reproduction Policy Search

&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to    create and update a new or an existing Reproduction Policy record.

&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp; c. Framework: Rice2.x

h4. 3. Security

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; a. Roles:
* OLE_Cataloging_Admin - Create 	,edit and provide blanket approve for Reproduction Policy
* Additional/Permitted Super User - 	Create ,edit and provide blanket approve for Reproduction Policy
* User - Can view the Reproduction Policy

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Reproduction Policy

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; d) Blanket Approve

h4. 7. Services


h4. 8. Data Model:The DM for Reproduction Policy is going to reside in the Rice2.x Schema


h2. *17)* Shelving Order *Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Shelving Order information will be maintained in the ole-rice2 schema and    developed  in   the ole-rice2 application using the new KRAD maintenance    doc   framework.
{info}

h4.


h4. 1. Shelving Order Maintenance (Create/Update)

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used    to create and update a new or an existing Shelving Order record.

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp; &nbsp; c. Framework: Rice2.x

h4. 2. Shelving Order Search

&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to    create and update a new or an existing Shelving Order record.

&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp; c. Framework: Rice2.x

h4. 3. Security

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; a. Roles:
* OLE_Cataloging_Admin - Create 	,edit and provide blanket approve for Shelving Order
* Additional/Permitted Super User - 	Create ,edit and provide blanket approve for Shelving Order
* User - Can view the Shelving Order

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Shelving Order

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; d) Blanket Approve

h4. 7. Services


h4. 8. Data Model:The DM for Shelving Order is going to reside in the Rice2.x Schema


h2. *18)* Shelving Schema *Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Shelving Schema information will be maintained in the ole-rice2 schema and    developed  in   the ole-rice2 application using the new KRAD maintenance    doc   framework.
{info}

h4.


h4. 1. Shelving Schema Maintenance (Create/Update)

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used    to create and update a new or an existing Shelving Schema record.

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp; &nbsp; c. Framework: Rice2.x

h4. 2. Shelving Schema Search

&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to    create and update a new or an existing Shelving Schema record.

&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp; c. Framework: Rice2.x

h4. 3. Security

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; a. Roles:
* OLE_Cataloging_Admin - Create 	,edit and provide blanket approve for Shelving Schema
* Additional/Permitted Super User - 	Create ,edit and provide blanket approve for Shelving Schema
* User - Can view the Shelving Schema

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Shelving Schema

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; d) Blanket Approve

h4. 7. Services


h4. 8. Data Model:The DM for Shelving Schema is going to reside in the Rice2.x Schema


h2. *19)* Separate or Composite Report *Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Separate or Composite Report information will be maintained in the ole-rice2 schema and    developed  in   the ole-rice2 application using the new KRAD maintenance    doc   framework.
{info}

h4.


h4. 1. Separate or Composite Report Maintenance (Create/Update)

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used    to create and update a new or an existing Separate or Composite Report record.

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp; &nbsp; c. Framework: Rice2.x

h4. 2. Separate or Composite Report Search

&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to    create and update a new or an existing Separate or Composite Report record.

&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp; c. Framework: Rice2.x

h4. 3. Security

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; a. Roles:
* OLE_Cataloging_Admin - Create 	,edit and provide blanket approve for Separate or Composite Report
* Additional/Permitted Super User - 	Create ,edit and provide blanket approve for Separate or Composite Report
* User - Can view the Separate or Composite Report

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Separate or Composite Report

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; d) Blanket Approve

h4. 7. Services


h4. 8. Data Model:The DM for Separate or Composite Report is going to reside in the Rice2.x Schema


h2. *20)* Retention Policy Type *Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Retention Policy Type information will be maintained in the ole-rice2 schema and    developed  in   the ole-rice2 application using the new KRAD maintenance    doc   framework.
{info}

h4.


h4. 1. Retention Policy Type Maintenance (Create/Update)

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used    to create and update a new or an existing Retention Policy Type record.

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp; &nbsp; c. Framework: Rice2.x

h4. 2. Retention Policy Type Search

&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to    create and update a new or an existing Retention Policy Type record.

&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp; c. Framework: Rice2.x

h4. 3. Security

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; a. Roles:
* OLE_Cataloging_Admin - Create 	,edit and provide blanket approve for Retention Policy Type
* Additional/Permitted Super User - 	Create ,edit and provide blanket approve for Retention Policy Type
* User - Can view the Retention Policy Type

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Retention Policy Type

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; d) Blanket Approve

h4. 7. Services


h4. 8. Data Model:The DM for Retention Policy Type is going to reside in the Rice2.x Schema


h2. *21)* Instance Item type *Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Instance Item type information will be maintained in the ole-rice2 schema and     developed  in   the ole-rice2 application using the new KRAD  maintenance    doc   framework.
{info}

h4.


h4. 1. Instance Item type Maintenance (Create/Update)

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used     to create and update a new or an existing Instance Item type  record.

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp; &nbsp; c. Framework: Rice2.x

h4. 2. Instance Item type Search

&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to     create and update a new or an existing Instance Item type record.

&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp; c. Framework: Rice2.x

h4. 3. Security

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; a. Roles:
* OLE_Cataloging_Admin - Create 	,edit and provide blanket approve for Instance Item type
* Additional/Permitted Super User - 	Create ,edit and provide blanket approve for Instance Item type
* User - Can view the Instance Item type

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Instance Item type

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; d) Blanket Approve

h4. 7. Services


h4. 8. Data Model:The DM for Instance Item type is going to reside in the Rice2.x Schema


h2. *22)* Specific Retention Policy Type Unit *Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Specific Retention Policy Type Unit information will be maintained in the ole-rice2 schema and     developed  in   the ole-rice2 application using the new KRAD  maintenance    doc   framework.
{info}

h4.


h4. 1. Specific Retention Policy Type Unit Maintenance (Create/Update)

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used     to create and update a new or an existing Specific Retention Policy Type Unit  record.

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp; &nbsp; c. Framework: Rice2.x

h4. 2. Specific Retention Policy Type Unit Search

&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to     create and update a new or an existing Specific Retention Policy Type Unit record.

&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp; c. Framework: Rice2.x

h4. 3. Security

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; a. Roles:
* OLE_Cataloging_Admin - Create 	,edit and provide blanket approve for Specific Retention Policy Type Unit
* Additional/Permitted Super User - 	Create ,edit and provide blanket approve for Specific Retention Policy Type Unit
* User - Can view the Specific Retention Policy Type Unit

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Specific Retention Policy Type Unit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; d) Blanket Approve

h4. 7. Services


h4. 8. Data Model:The DM for Specific Retention Policy Type Unit is going to reside in the Rice2.x Schema


h2. *23)* Source of Term *Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Source of Term information will be maintained in the ole-rice2 schema and     developed  in   the ole-rice2 application using the new KRAD  maintenance    doc   framework.
{info}

h4.


h4. 1. Source of Term Maintenance (Create/Update)

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used     to create and update a new or an existing Source of Term  record.

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp; &nbsp; c. Framework: Rice2.x

h4. 2. Source of Term Search

&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to     create and update a new or an existing Source of Term record.

&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp; c. Framework: Rice2.x

h4. 3. Security

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; a. Roles:
* OLE_Cataloging_Admin - Create 	,edit and provide blanket approve for Source of Term
* Additional/Permitted Super User - 	Create ,edit and provide blanket approve for Source of Term
* User - Can view the Source of Term

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Source of Term

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; d) Blanket Approve

h4. 7. Services


h4. 8. Data Model:The DM for Source of Term is going to reside in the Rice2.x Schema


h2. *24)* Statistical Searching Codes *Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Statistical Searching Codes information will be maintained in the ole-rice2 schema and     developed  in   the ole-rice2 application using the new KRAD  maintenance    doc   framework.
{info}

h4.


h4. 1. Statistical Searching Codes Maintenance (Create/Update)

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used     to create and update a new or an existing Statistical Searching Codes  record.

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp; &nbsp; c. Framework: Rice2.x

h4. 2. Statistical Searching Codes Search

&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to     create and update a new or an existing Statistical Searching Codes record.

&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp; c. Framework: Rice2.x

h4. 3. Security

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; a. Roles:
* OLE_Cataloging_Admin - Create 	,edit and provide blanket approve for Statistical Searching Codes
* Additional/Permitted Super User - 	Create ,edit and provide blanket approve for Statistical Searching Codes
* User - Can view the Statistical Searching Codes

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Statistical Searching Codes

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; d) Blanket Approve

h4. 7. Services


h4. 8. Data Model:The DM for Statistical Searching Codes is going to reside in the Rice2.x Schema


h2. *25)* Country Codes *Maintenance Document Technical Specification*

{info:title=Jira}
[https://jira.kuali.org/browse/OLE-2|https://jira.kuali.org/browse/OLE-2894]909
{info}

h3.

{info:title=Rice2.x Framework}
Country Codes information will be maintained in the ole-rice2 schema and     developed  in   the ole-rice2 application using the new KRAD  maintenance    doc   framework.
{info}

h4.


h4. 1. Country Codes Maintenance (Create/Update)

&nbsp;&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used     to create and update a new or an existing Country Codes  record.

&nbsp;&nbsp;&nbsp; b. Participants:

&nbsp; &nbsp; c. Framework: Rice2.x

h4. 2. Country Codes Search

&nbsp;&nbsp; a. KRAD Design: A simple KRAD maintenance document will be used to     create and update a new or an existing Country Codes record.

&nbsp;&nbsp; b. Participants:

&nbsp;&nbsp; c. Framework: Rice2.x

h4. 3. Security

&nbsp;&nbsp;&nbsp; OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

&nbsp;&nbsp;&nbsp; a. Roles:
* OLE_Cataloging_Admin - Create 	,edit and provide blanket approve for Country Codes
* Additional/Permitted Super User - 	Create ,edit and provide blanket approve for Country Codes
* User - Can view the Country Codes

&nbsp;&nbsp;&nbsp; b. Permissions to do the following on the below entities:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Country Codes

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Create

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Edit

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) View(Inquiry)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; d) Blanket Approve

h4. 7. Services


h4. 8. Data Model:The DM for Country Codes is going to reside in the Rice2.x Schema