Page Comparison

...

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

    b. Participants:

         OleCompleteness.xml

         OleCompletenessMaintenanceDocument.xml

         OleCompleteness.java

    c. Framework: Rice2.x

...

          d) Blanket Approve

3. OJB-Mapping

4. Services

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

7)  ELA Relationship Document Technical Specification

1. ElARelationship Maintenance (Create/Update/Search)

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

    b. Participants:

    c. Framework: Rice2.x

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 ElARelationship
• Additional/Permitted Super User - Create ,edit and provide blanket approve for ElARelationship
• User - Can view the ElARelationship

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

        ElARelationship

         a) Create

         b) Edit

         c) View(Inquiry)

         d) Blanket Approve

3. OJB-Mapping

...

      <class-descriptor class="org.kuali.ole.catalog.bo.OleCompleteness" table="OLE_CAT_CMPLT_T">
           <field-descriptor name="completenessId" column="CMPLT_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_CMPLT_S"/>
           <field-descriptor name="completenessCode" column="CMPLT_CD" jdbc-type="VARCHAR" />
           <field-descriptor name="completenessName" column="CMPLT_NM" jdbc-type="VARCHAR" />
           <field-descriptor name="source" column="SRC" jdbc-type="VARCHAR" />
           <field-descriptor name="sourceDate" column="SRC_DT" jdbc-type="DATE" />
           <field-descriptor name="active" column="ROW_ACT_IND" jdbc-type="VARCHAR" conversion="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion" />
           <field-descriptor name="objectId" column="OBJ_ID" jdbc-type="VARCHAR" index="true"/>
           <field-descriptor name="versionNumber" column="VER_NBR" jdbc-type="BIGINT" locking="true"/>
    </class-descriptor>

4. Services

5. Data Model:The DM for

...

Location Status is going to reside in the Rice2.x

...

Schema 

...

7)  ELA Relationship Document Technical Specification

1.

...

ElARelationship Maintenance (Create/Update/Search)

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

    b. Participants:

         OleElectronicLocationAndAccessRelationship.xml

         OleElectronicLocationAndAccessRelationshipMaintenanceDocument.xml

         OleElectronicLocationAndAccessRelationship.java

    c. Framework: Rice2.x

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 Encoding LevelElARelationship
• Additional/Permitted Super User - Create ,edit and provide blanket approve for Encoding LevelElARelationship
• User - Can view the Encoding LevelElARelationship

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

        Encoding Level  ElARelationship

                  a) Create

         b) Edit

                  c) View(Inquiry)

         d) Blanket Approve

3. OJB-Mapping

4. Services

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

9) Field Encoding Level Maintenance Document Technical Specification

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

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

    b. Participants:

    c. Framework: Rice2.x

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 Field Encoding Level
• Additional/Permitted Super User - Create ,edit and provide blanket approve for Field Encoding Level
• User - Can view the Field Encoding Level

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

        Field Encoding Level

          a) Create

          b) Edit

          c) View(Inquiry)

          d) Blanket Approve

3. OJB-Mapping

...

       <class-descriptor class="org.kuali.ole.catalog.bo.OleElectronicLocationAndAccessRelationship" table="OLE_CAT_ELA_RLSHP_T">
             <field-descriptor name="elaRelationshipId" column="ELE_RLSHP_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_ELA_RLSHP_S"/>
             <field-descriptor name="elaRelationshipCode" column="ELE_RLSHP_CD" jdbc-type="VARCHAR" />
             <field-descriptor name="elaRelationshipName" column="ELE_RLSHP_NM" jdbc-type="VARCHAR" />
             <field-descriptor name="source" column="SRC" jdbc-type="VARCHAR" />
             <field-descriptor name="sourceDate" column="SRC_DT" jdbc-type="DATE" />
             <field-descriptor name="active" column="ROW_ACT_IND" jdbc-type="VARCHAR" conversion="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion" />
             <field-descriptor name="objectId" column="OBJ_ID" jdbc-type="VARCHAR" index="true"/>
             <field-descriptor name="versionNumber" column="VER_NBR" jdbc-type="BIGINT" locking="true"/>
    </class-descriptor>

4. Services

5. Data Model:The DM for

...

ElARelationship is going to reside in the Rice2.x Schema

...

8)

...

Encoding Level Maintenance Document Technical Specification

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

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

    b. Participants:

    c. Framework: Rice2.x

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 General Retention Policy
• Additional/Permitted Super User - Create ,edit and provide blanket approve for General Retention Policy
• User - Can view the General Retention Policy

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

        General Retention Policy

          a) Create

          b) Edit

          c) View(Inquiry)

          d) Blanket Approve

...

1. EncodingLevel Maintenance (Create/Update/Search)

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

    b. Participants:

         OleEncodingLevel.xml

         OleEncodingLevelMaintenanceDocument.xml

         OleEncodingLevel.java

    c. Framework: Rice2.x

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 Encoding Level
• Additional/Permitted Super User - Create ,edit and provide blanket approve for Encoding Level
• User - Can view the Encoding Level

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

        Encoding Level

         a) Create

         b) Edit

         c) View(Inquiry)

         d) Blanket Approve

3. OJB-Mapping

       <class-descriptor class="org.kuali.ole.catalog.bo.OleEncodingLevel" table="OLE_CAT_ENCD_LVL_T">
             <field-descriptor name="encodingLevelId" column="ENCD_LVL_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_ENCD_LVL_S"/>
             <field-descriptor name="encodingLevelCode" column="ENCD_LVL_CD" jdbc-type="VARCHAR" />
             <field-descriptor name="encodingLevelName" column="ENCD_LVL_NM" jdbc-type="VARCHAR" />
             <field-descriptor name="source" column="SRC" jdbc-type="VARCHAR" />
             <field-descriptor name="sourceDate" column="SRC_DT" jdbc-type="DATE" />
             <field-descriptor name="active" column="ROW_ACT_IND" jdbc-type="VARCHAR" conversion="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion" />
             <field-descriptor name="objectId" column="OBJ_ID" jdbc-type="VARCHAR" index="true"/>
             <field-descriptor name="versionNumber" column="VER_NBR" jdbc-type="BIGINT" locking="true"/>
    </class-descriptor>

4. Services

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

9) Field Encoding Level Maintenance Document Technical Specification

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

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

    b. Participants:

         OleFieldEncodingLevel.xml

         OleFieldEncodingLevelMaintenanceDocument.xml

         OleFieldEncodingLevel.java

    c. Framework: Rice2.x

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 Field Encoding Level
• Additional/Permitted Super User - Create ,edit and provide blanket approve for Field Encoding Level
• User - Can view the Field Encoding Level

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

        Field Encoding Level

          a) Create

          b) Edit

          c) View(Inquiry)

          d) Blanket Approve

3. OJB-Mapping

       <class-descriptor class="org.kuali.ole.catalog.bo.OleFieldEncodingLevel" table="OLE_CAT_FLD_ENCD_LVL_T">
             <field-descriptor name="fieldEncodingLevelId" column="FLD_ENCD_LVL_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_FLD_ENCD_LVL_S"/>
             <field-descriptor name="fieldEncodingLevelCode" column="FLD_ENCD_LVL_CD" jdbc-type="VARCHAR" />
             <field-descriptor name="fieldEncodingLevelName" column="FLD_ENCD_LVL_NM" jdbc-type="VARCHAR" />
             <field-descriptor name="source" column="SRC" jdbc-type="VARCHAR" />
             <field-descriptor name="sourceDate" column="SRC_DT" jdbc-type="DATE" />
             <field-descriptor name="active" column="ROW_ACT_IND" jdbc-type="VARCHAR" conversion="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion" />
             <field-descriptor name="objectId" column="OBJ_ID" jdbc-type="VARCHAR" index="true"/>
             <field-descriptor name="versionNumber" column="VER_NBR" jdbc-type="BIGINT" locking="true"/>
      </class-descriptor>

4. Services

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

10) General Retention Maintenance Document Technical Specification

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

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

    b. Participants:

         OleGeneralRetentionPolicy.xml

         OleGeneralRetentionPolicyMaintenanceDocument.xml

         OleGeneralRetentionPolicy.java

    c. Framework: Rice2.x

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 General Retention Policy
• Additional/Permitted Super User - Create ,edit and provide blanket approve for General Retention Policy
• User - Can view the General Retention Policy

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

        General Retention Policy

          a) Create

          b) Edit

          c) View(Inquiry)

          d) Blanket Approve

3. OJB-Mapping

        <class-descriptor class="org.kuali.ole.catalog.bo.OleGeneralRetentionPolicy" table="OLE_CAT_GEN_RTN_POL_T">
              <field-descriptor name="generalRetentionPolicyId" column="GEN_RTN_POL_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_GEN_RTN_POL_S"/>
              <field-descriptor name="generalRetentionPolicyCode" column="GEN_RTN_POL_CD" jdbc-type="VARCHAR" />
              <field-descriptor name="generalRetentionPolicyName" column="GEN_RTN_POL_NM" jdbc-type="VARCHAR" />
              <field-descriptor name="source" column="SRC" jdbc-type="VARCHAR" />
              <field-descriptor name="sourceDate" column="SRC_DT" jdbc-type="DATE" />
              <field-descriptor name="active" column="ROW_ACT_IND" jdbc-type="VARCHAR" conversion="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion" />
              <field-descriptor name="objectId" column="OBJ_ID" jdbc-type="VARCHAR" index="true"/>
              <field-descriptor name="versionNumber" column="VER_NBR" jdbc-type="BIGINT" locking="true"/>
     </class-descriptor>

4. Services

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

...