Page Comparison

...

        d) Blanket Approve

3. OJB-Mapping

4. Services

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

22) Specific Retention Policy Type Unit Maintenance Document Technical Specification

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

    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.

    b. Participants:

         OleSpecificRetentionPolicyTypeUnit.xml

         OleSpecificRetentionPolicyTypeUnitMaintenanceDocument.xml

         OleSpecificRetentionPolicyTypeUnit.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 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

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

       Specific Retention Policy Type Unit

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

4. Services

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

23) Source of Term Maintenance Document Technical Specification

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

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

    b. Participants:

         OleSourceOfTerm.xml

         OleSourceOfTermMaintenanceDocument.xml

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

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

       Source of Term

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

...

       <class-descriptor class="org.kuali.ole.catalog.bo.OleInstanceItemType" table="ole_cat_itm_typ_t">
            <field-descriptor name="instanceItemTypeId" column="ITM_TYP_CD_ID" jdbc-type="VARCHAR" primarykey="true" autoincrement="true" sequence-name="ole_cat_itm_typ_s"/>
            <field-descriptor name="instanceItemTypeCode" column="ITM_TYP_CD" jdbc-type="VARCHAR" />
            <field-descriptor name="instanceItemTypeName" column="ITM_TYP_NM" jdbc-type="VARCHAR" />
            <field-descriptor name="instanceItemTypeDesc" column="ITM_TYP_DESC" 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="objectId" column="OBJ_ID" jdbc-type="VARCHAR" index="true"/>
            <field-descriptor name="versionNumber" column="VER_NBR" jdbc-type="BIGINT" locking="true"/>
            <field-descriptor name="active" column="ROW_ACT_IND" jdbc-type="VARCHAR"  conversion="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion" />
    </class-descriptor>

4. Services

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

22) Specific Retention Policy Type Unit Maintenance Document Technical Specification

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

    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.

    b. Participants:

         OleSpecificRetentionPolicyTypeUnit.xml

         OleSpecificRetentionPolicyTypeUnitMaintenanceDocument.xml

         OleSpecificRetentionPolicyTypeUnit.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 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

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

       Specific Retention Policy Type Unit

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

        <class-descriptor class="org.kuali.ole.catalog.bo.OleSpecificRetentionPolicyTypeUnit" table="ole_cat_spfc_rtn_pol_unt_typ_t">
             <field-descriptor name="specificPolicyUnitTypeId" column="SPFC_RTN_POL_UNT_TYP_ID" jdbc-type="VARCHAR" primarykey="true" autoincrement="true" sequence-name="ole_cat_spfc_rtn_pol_unt_typ_s"/>
             <field-descriptor name="specificPolicyUnitTypeCode" column="SPFC_RTN_POL_UNT_TYP_CD" jdbc-type="VARCHAR" />
             <field-descriptor name="specificPolicyUnitTypeName" column="SPFC_RTN_POL_UNT_TYP_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="objectId" column="OBJ_ID" jdbc-type="VARCHAR" index="true"/>
             <field-descriptor name="versionNumber" column="VER_NBR" jdbc-type="BIGINT" locking="true"/>
             <field-descriptor name="active" column="ROW_ACT_IND" jdbc-type="VARCHAR"  conversion="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion" />
    </class-descriptor>

4. Services

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

23) Source of Term Maintenance Document Technical Specification

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

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

    b. Participants:

         OleSourceOfTerm.xml

         OleSourceOfTermMaintenanceDocument.xml

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

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

       Source of Term

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

       <class-descriptor class="org.kuali.ole.catalog.bo.OleSourceOfTerm" table="ole_cat_src_trm_t">
          <field-descriptor name="sourceOfTermId" column="SRC_TRM_ID" jdbc-type="VARCHAR" primarykey="true" autoincrement="true" sequence-name="ole_cat_src_trm_s"/>
          <field-descriptor name="sourceOfTermCode" column="SRC_TRM_CD" jdbc-type="VARCHAR" />
          <field-descriptor name="sourceOfTermName" column="SRC_TRM_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="objectId" column="OBJ_ID" jdbc-type="VARCHAR" index="true"/>
          <field-descriptor name="versionNumber" column="VER_NBR" jdbc-type="BIGINT" locking="true"/>
          <field-descriptor name="active" column="ROW_ACT_IND" jdbc-type="VARCHAR"  conversion="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion" />
    </class-descriptor>

4. Services

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

...