Page Comparison

...

    <class-descriptor class="org.kuali.ole.catalog.bo.OleLocationStatus" table="ole_cat_loc_status_t">
        <field-descriptor name="locationStatusId" column="LOC_STATUS_ID" jdbc-type="VARCHAR" primarykey="true" autoincrement="true" sequence-name="ole_cat_loc_status_s" />
        <field-descriptor name="locationStatusCode" column="LOC_STATUS_CD" jdbc-type="VARCHAR" />
        <field-descriptor name="locationStatusName" column="LOC_STATUS_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>

...

        d) Blanket Approve

3. OJB-Mapping

4. Services

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

13) Privacy Maintenance Document Technical Specification

1. Privacy Maintenance (Create/Update/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:

         OlePrivacy.xml

         OlePrivacyMaintenanceDocument.xml

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

...

       <class-descriptor class="org.kuali.ole.catalog.bo.OleNotationType" table="ole_cat_ntn_typ_t">
           <field-descriptor name="notationTypeId" column="NTN_TYP_ID" jdbc-type="VARCHAR" primarykey="true" autoincrement="true" sequence-name="ole_cat_ntn_typ_s"/>
           <field-descriptor name="notationTypeCode" column="NTN_TYP_CD" jdbc-type="VARCHAR" />
           <field-descriptor name="notationTypeName" column="NTN_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

...

Notation Type is going to reside in the Rice2.x Schema

...

13)

...

Privacy Maintenance Document Technical Specification

1.

...

Privacy Maintenance (Create/Update/Search)

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

    b. Participants:

         OleReceiptStatusOlePrivacy.xml

         OleReceiptStatusMaintenanceDocumentOlePrivacyMaintenanceDocument.xml

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

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

       Receipt Status

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

...

    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

3. OJB-Mapping

       <class-descriptor class="org.kuali.ole.catalog.bo.OlePrivacy" table="ole_cat_prvcy_t">
          <field-descriptor name="privacyId" column="PRVCY_ID" jdbc-type="VARCHAR" primarykey="true" autoincrement="true" sequence-name="ole_cat_prvcy_s"/>
          <field-descriptor name="privacyCode" column="PRVCY_CD" jdbc-type="VARCHAR" />
          <field-descriptor name="privacyName" column="PRVCY_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 Privacy is going to reside in the Rice2.x Schema

14) Receipt Status Maintenance Document Technical Specification

1. Receipt 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 Receipt Status record.

    b. Participants:

         OleReceiptStatus.xml

         OleReceiptStatusMaintenanceDocument.xml

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

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

       Receipt Status

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

      <class-descriptor class="org.kuali.ole.catalog.bo.OleReceiptStatus" table="ole_cat_rcpt_stat_t">
             <field-descriptor name="receiptStatusId" column="RCPT_STAT_ID" jdbc-type="VARCHAR" primarykey="true" autoincrement="true" sequence-name="ole_cat_rcpt_stat_s"/>
             <field-descriptor name="receiptStatusCode" column="RCPT_STAT_CD" jdbc-type="VARCHAR" />
             <field-descriptor name="receiptStatusName" column="RCPT_STAT_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 Receipt Status is going to reside in the Rice2.x Schema

...