Page Comparison

...

3. OJB-Mapping

      <class-descriptor class="org.kuali.ole.catalog.bo.OleReproductionPolicy" table="OLE_CAT_REPRO_POL_T">
        <field-descriptor name="reproductionPolicyId" column="REPRO_POL_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_REPRO_POL_S" />
        <field-descriptor name="reproductionPolicyCode" column="REPRO_POL_CD" jdbc-type="VARCHAR" />
        <field-descriptor name="reproductionPolicyName" column="REPRO_POL_NM" jdbc-type="VARCHAR" />
        <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="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" />
     </class-descriptor>

...

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

    b. Participants:

         OleShelvingOrder.xml

         OleShelvingOrderMaintenanceDocument.xml

         OleShelvingOrder.java

    c. Framework: Rice2.x

...

        d) Blanket Approve

3. OJB-Mapping

4. Services

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

18) Shelving Schema Maintenance Document Technical Specification

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

    a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Shelving Schema 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 Shelving Schema
• Additional/Permitted Super User - Create ,edit and provide blanket approve for Shelving Schema
• User - Can view the Shelving Schema

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

       Shelving Schema

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

4. Services

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

19) Separate or Composite Report Maintenance Document Technical Specification

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

    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.

    b. Participants:

    c. Framework: Rice2.x

2. Security

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

    a. Roles:

...

     <class-descriptor class="org.kuali.ole.catalog.bo.OleShelvingOrder" table="OLE_CAT_SHVLG_ORD_T">
        <field-descriptor name="shelvingOrderId" column="SHVLG_ORD_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_SHVLG_ORD_S" />
        <field-descriptor name="shelvingOrderCode" column="SHVLG_ORD_CD" jdbc-type="VARCHAR" />
        <field-descriptor name="shelvingOrderName" column="SHVLG_ORD_NM" jdbc-type="VARCHAR" />
        <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="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" />
    </class-descriptor>

4. Services

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

18) Shelving Schema Maintenance Document Technical Specification

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

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

    b. Participants:

         OleShelvingScheme.xml

         OleShelvingSchemeMaintenanceDocument.xml

         OleShelvingScheme.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 Separate or Composite ReportShelving Schema
• Additional/Permitted Super User - Create ,edit and provide blanket approve for Separate or Composite ReportShelving Schema
• User - Can view the Separate or Composite ReportShelving Schema

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

       Separate or Composite ReportShelving Schema

        a) Create

        b) Edit

...

        d) Blanket Approve

3. OJB-Mapping

4. Services

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

20) Retention Policy Type Maintenance Document Technical Specification

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

    a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Retention Policy Type 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 Retention Policy Type
• Additional/Permitted Super User - Create ,edit and provide blanket approve for Retention Policy Type
• User - Can view the Retention Policy Type

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

       Retention Policy Type

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

...

     <class-descriptor class="org.kuali.ole.catalog.bo.OleShelvingScheme" table="OLE_CAT_SHVLG_SCHM_T">
        <field-descriptor name="shelvingSchemeId" column="SHVLG_SCHM_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_SHVLG_SCHM_S" />
        <field-descriptor name="shelvingSchemeCode" column="SHVLG_SCHM_CD" jdbc-type="VARCHAR" />
        <field-descriptor name="shelvingSchemeName" column="SHVLG_SCHM_NM" jdbc-type="VARCHAR" />
        <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="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" />
    </class-descriptor>

4. Services

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

19) Separate or Composite Report Maintenance Document Technical Specification

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

    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.

    b. Participants:

         OleSeperateOrCompositeReport.xml

         OleSeperateOrCompositeReportMaintenanceDocument.xml

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

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

       Separate or Composite Report

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

       <class-descriptor class="org.kuali.ole.catalog.bo.OleSeperateOrCompositeReport" table="OLE_CAT_SPCP_RPT_T">
        <field-descriptor name="seperateOrCompositeReportId" column="SPCP_RPT_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_SPCP_RPT_S" />
        <field-descriptor name="seperateOrCompositeReportCode" column="SPCP_RPT_CD" jdbc-type="VARCHAR" />
        <field-descriptor name="seperateOrCompositeReportName" column="SPCP_RPT_NM" jdbc-type="VARCHAR" />
        <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="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" />
    </class-descriptor>

4. Services

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

20) Retention Policy Type Maintenance Document Technical Specification

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

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

    b. Participants:

         OleSpecificRetentionPolicyType.xml

         OleSpecificRetentionPolicyTypeMaintenanceDocument.xml

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

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

       Retention Policy Type

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

      <class-descriptor class="org.kuali.ole.catalog.bo.OleSpecificRetentionPolicyType" table="OLE_CAT_SPFC_RTN_POL_TYP_T">
        <field-descriptor name="specificRetentionPolicyTypeId" column="SPFC_RTN_POL_TYP_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_SPFC_RTN_POL_TYP_S" />
        <field-descriptor name="specificRetentionPolicyTypeCode" column="SPFC_RTN_POL_TYP_CD" jdbc-type="VARCHAR" />
        <field-descriptor name="specificRetentionPolicyTypeName" column="SPFC_RTN_POL_TYP_NM" jdbc-type="VARCHAR" />
        <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="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" />
    </class-descriptor>

4. Services

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

...