Page Comparison

...

         OleLocationStatusMaintenanceDocument.xml

         OleLocationStatusLookup.xml

         OleLocationStatus.java

         OleLocationStatusMaintenanceImpl.java

         OleLocationStatusRule.java

         OleLocationStatus_UT.java

    c. Framework: Rice2.x

...

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

...

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

             Image Added

2) Type of Ownership Maintenance Document Technical Specification

1. Type Of Ownership Maintenance (Create/Update/Search)

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

    b. Participants:

         OleTypeOfOwnership.xml

...

         OleTypeOfOwnership.java

         OleTypeOfOwnershipRule.java

         OleTypeOfOwnership_UT.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 Type Of Ownership
• Additional/Permitted Super User - Create ,edit and provide blanket approve forType Of Ownership
• User - Can view the Type Of Ownership

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

        Type Of Ownership

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

      <class-descriptor class="org.kuali.ole.catalog.bo.OleTypeOfOwnership"  table="OLE_CAT_TYPE_OWNERSHIP_T">
              <field-descriptor name="typeOfOwnershipId" column="TYPE_OWNERSHIP_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_TYPE_OWNERSHIP_S" />
              <field-descriptor name="typeOfOwnershipCode" column="TYPE_OWNERSHIP_CD" jdbc-type="VARCHAR" />
              <field-descriptor name="typeOfOwnershipName" column="TYPE_OWNERSHIP_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 Type Of Ownership is going to reside in the Rice2.x Schema

      Image Added

3) Action Maintenance Document Technical Specification

1. Action Maintenance (Create/Update/Search)

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

    b. Participants:

         OleAction.xml

         OleActionMaintenanceDocument.xml

         OleAction.java

         OleActionRule.java

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

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

      Action

       a) Create

       b) Edit

       c) View(Inquiry)

       d) Blanket Approve

3. OJB-Mapping

       <class-descriptor class="org.kuali.ole.catalog.bo.OleAction"  table="OLE_CAT_ACTION_T">
                <field-descriptor name="actionId" column="ACTION_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_ACTION_S" />
                <field-descriptor name="actionCode" column="ACTION_CD" jdbc-type="VARCHAR" />
                <field-descriptor name="actionName" column="ACTION_NM" jdbc-type="VARCHAR" />
                <field-descriptor name="actionDescription" column="ACTION_DESC" 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 Action is going to reside in the Rice2.x Schema

   Image Added

4) Access Method Maintenance Document Technical Specification

1. Access Method Maintenance (Create/Update/Search)

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

    b. Participants:

         OleAccessMethod.xml

...

         OleAccessMethod.java

         OleAccessMethodsRule.java

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

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

      Access Method

       a) Create

       b) Edit

       c) View(Inquiry)

       d) Blanket Approve

3. OJB-Mapping

        <class-descriptor class="org.kuali.ole.catalog.bo.OleAccessMethod" table="OLE_CAT_ACCS_MTHD_T">
                <field-descriptor name="accessMethodId" column="ACCS_MTHD_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_ACCS_MTHD_S" />
                <field-descriptor name="accessMethodCode" column="ACCS_MTHD_CD" jdbc-type="VARCHAR" />
                <field-descriptor name="accessMethodName" column="ACCS_MTHD_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 Access Method is going to reside in the Rice2.x Schema

     Image Added

5) Acquisition Method Maintenance Document Technical Specification

1. Acquisition Method Maintenance (Create/Update/Search)

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

    b. Participants:

         OleAcquisitionMethod.xml

...

         OleAcquisitionMethod.java

         OleAcquisitionMethodsRule.java

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

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

      Acquisition Method

       a) Create

       b) Edit

       c) View(Inquiry)

       d) Blanket Approve

3. OJB-Mapping

       <class-descriptor class="org.kuali.ole.catalog.bo.OleAcquisitionMethod" table="OLE_CAT_ACQ_MTHD_T">
           <field-descriptor name="acquisitionMethodId" column="ACQ_MTHD_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_ACQ_MTHD_S" />
           <field-descriptor name="acquisitionMethodCode" column="ACQ_MTHD_CD" jdbc-type="VARCHAR" />
           <field-descriptor name="acquisitionMethodName" column="ACQ_MTHD_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 Acquisition Method is going to reside in the Rice2.x Schema

Image Added

6) Completeness Maintenance Document Technical Specification

...

    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

         c. Framework: Rice2OleCompletenessMaintenanceDocument.xml

         OleCompleteness.java

         OleCompletenessLookup.java

         OleCompletenessRule.java

         OleCompleteness_UT.java

    c. Framework: Rice2.x

2. Security

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

...

          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

...

      <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

...

Completeness is going to reside in the Rice2.x

...

Schema 

     Image Added
  

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

         OleElectronicLocationAndAccessRelationshipLookup.java

         OleElectronicLocationAndAccessRelationshipRule.java

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

4. Services

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

...

       <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 

     Image Added

8) Encoding Level Maintenance Document Technical Specification

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 General Retention Policy Encoding Level record. 

    b. Participants:

    c. Framework: Rice2.x

2. Security

    OLE_         OleEncodingLevel.xml

         OleEncodingLevelMaintenanceDocument.xml

         OleEncodingLevel.java

         OleEncodingLevelLookup.java

         OleEncodingLevelRule.java

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

...

• Encoding Level

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

        General Retention Policy            Encoding Level

         a) Create

                   b) Edit

                   c) View(Inquiry)

                   d) Blanket Approve

3. OJB-Mapping

4. Services

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

11) Lending Policy Maintenance Document Technical Specification

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

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

       Lending Policy

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

4. Services

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

12) Notation Type Maintenance Document Technical Specification

...

       <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

    Image Added

9) Field Encoding Level Maintenance Document Technical Specification

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

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

    b. Participants:

         OleNotationTypeOleFieldEncodingLevel.xml

         OleNotationTypeMaintenanceDocumentOleFieldEncodingLevelMaintenanceDocument.xml         OleNotationType

         OleFieldEncodingLevel.java

         OleFieldEncodingLevelLookup.java

         OleFieldEncodingLevelRule.java

         OleFieldEncodingLevel_UT.java

        c. Framework: Rice2.x

2. Security

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

...

• OLE_Cataloging_Admin - Create ,edit and provide blanket approve for Notation TypeField Encoding Level
• Additional/Permitted Super User - Create ,edit and provide blanket approve for Notation TypeField Encoding Level
• User - Can view the Notation TypeField Encoding Level

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

       Notation Type

                Field Encoding Level

          a) Create

                  b) Edit

                  c) View(Inquiry)

                  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

3. OJB-Mapping

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

4. Services

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

15) Record Type Maintenance Document Technical Specification

1. Record 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 Record Type record.

    b. Participants:

    c. Framework: Rice2.x

2. Security

    OLE_CAT namespace will be used for defining some        <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

          Image Added

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

         OleGeneralRetentionPolicyLookup.java

         OleGeneralRetentionPolicyRule.java

         OleGeneralRetentionPolicy_UT.java

    c. Framework: Rice2.x

2. Security

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

...

• OLE_Cataloging_Admin - Create ,edit and provide blanket approve for Record TypeGeneral Retention Policy
• Additional/Permitted Super User - Create ,edit and provide blanket approve for Record TypeGeneral Retention Policy
• User - Can view the Record TypeGeneral Retention Policy

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

       Record Type

                General Retention Policy

          a) Create

                  b) Edit

                  c) View(Inquiry)

                  d) Blanket Approve

3. OJB-Mapping

4. Services

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

16) Reproduction Policy Maintenance Document Technical Specification

1. Reproduction 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 Reproduction Policy record.

    b. Participants:

         OleReproductionPolicy.xml

         OleReproductionPolicyMaintenanceDocument.xml

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

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

       Reproduction Policy

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

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        <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" />
        <field-descriptor name="reproductionPolicyName" column="REPRO_POL_NM" 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"/>
        <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

...

     </class-descriptor>

4. Services

5. Data Model:The DM for

...

General Retention Policy is going to reside in the Rice2.x Schema  

Image Added

...

11)

...

Lending Policy Maintenance Document Technical Specification

1.

...

Lending 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 Shelving Order Lending Policy record.

    b. Participants:

         OleShelvingOrderOleLendingPolicy.xml

         OleShelvingOrderMaintenanceDocumentOleLendingPolicyMaintenanceDocument.xml

         OleLendingPolicy.java

         OleShelvingOrderOleLendingPolicyRule.java

         OleLendingPolicy_UT.java

    c. Framework: Rice2.x

2. Security

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

...

• OLE_Cataloging_Admin - Create ,edit and provide blanket approve for Shelving OrderLending Policy
• Additional/Permitted Super User - Create ,edit and provide blanket approve for Shelving OrderLending Policy
• User - Can view the Shelving OrderLending Policy

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

       Shelving OrderLending Policy

        a) Create

        b) Edit

...

        d) Blanket Approve

3. OJB-Mapping

            <class-descriptor class="org.kuali.ole.catalog.bo.OleShelvingOrderOleLendingPolicy" table="OLE_CAT_SHVLGLND_ORDPOL_T">
                    <field-descriptor name="shelvingOrderIdlendingPolicyId" column="SHVLGLND_ORDPOL_ID " jdbc-type="INTEGER" primarykey="true" index="true" autoincrement="true" sequence-name="OLE_CAT_SHVLGLND_ORDPOL_Ss "></>field-descriptor>
                    <field-descriptor name="shelvingOrderCodelendingPolicyCode" column="SHVLGLND_ORDPOL_CD" jdbc-type="VARCHAR"></>field-descriptor>
                    <field-descriptor name="shelvingOrderNamelendingPolicyName" column="SHVLGLND_ORDPOL_NM" jdbc-type="VARCHAR"></>
        field-descriptor>
            <field-descriptor name="objectIdsource" column="OBJ_ID" SRC" jdbc-type="VARCHAR" index="true"/>
        ></field-descriptor>
            <field-descriptor name="versionNumbersourceDate" column="VERSRC_NBRDT" jdbc-type="BIGINT" locking="true" />
        DATE"></field-descriptor>
            <field-descriptor name="sourceobjectId" column="SRCOBJ_ID" jdbc-type="VARCHAR" index="true"/>
                    <field-descriptor name="sourceDateversionNumber" column="SRCVER_DTNBR" jdbc-type="DATEBIGINT" 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

...

Lending Policy is going to reside in the Rice2.x Schema

...

    Image Added

12) Notation Type Maintenance Document Technical Specification

1.

...

Notation 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 Shelving Schema Notation Type record.

    b. Participants:

         OleShelvingSchemeOleNotationType.xml

         OleShelvingSchemeMaintenanceDocumentOleNotationTypeMaintenanceDocument.xml

         OleShelvingSchemeOleNotationType.java

    c. Framework:          OleNotationTypeRule.java

         OleNotationType_UT.java

    c. Framework: Rice2.x

2. Security

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

...

• OLE_Cataloging_Admin - Create ,edit and provide blanket approve for Shelving SchemaNotation Type
• Additional/Permitted Super User - Create ,edit and provide blanket approve for Shelving SchemaNotation Type
• User - Can view the Shelving SchemaNotation Type

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

       Shelving SchemaNotation Type

        a) Create

        b) Edit

...

        d) Blanket Approve

3. OJB-Mapping

            <class-descriptor class="org.kuali.ole.catalog.bo.OleShelvingSchemeOleNotationType" table="OLEole_CATcat_SHVLGntn_SCHMtyp_Tt">
                   <field-descriptor name="shelvingSchemeIdnotationTypeId" column="SHVLGNTN_SCHMTYP_ID" jdbc-type="INTEGERVARCHAR" primarykey="true" autoincrement="true" sequence-name="OLEole_CATcat_SHVLGntn_SCHMtyp_Ss"/>
                   <field-descriptor name="shelvingSchemeCodenotationTypeCode" column="SHVLGNTN_SCHMTYP_CD" jdbc-type="VARCHAR" />
                   <field-descriptor name="shelvingSchemeNamenotationTypeName" column="SHVLGNTN_SCHMTYP_NM" jdbc-type="VARCHAR" />
                   <field-descriptor name="objectIdsource" column="OBJ_IDSRC" jdbc-type="VARCHAR" index=" true" />
                   <field-descriptor name="versionNumbersourceDate" column="VERSRC_NBRDT" jdbc-type="BIGINT" locking="trueDATE" />
                   <field-descriptor name="sourceobjectId" column="SRCOBJ_ID" jdbc-type="VARCHAR" index="true"/>
                   <field-descriptor name="sourceDateversionNumber" column="SRCVER_DTNBR" jdbc-type="BIGINT" locking="DATEtrue"/>
                   <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

        Image Added

...

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 Separate or Composite Report Privacy record.

    b. Participants:

         OleSeperateOrCompositeReportOlePrivacy.xml

         OleSeperateOrCompositeReportMaintenanceDocumentOlePrivacyMaintenanceDocument.xml

         OleSeperateOrCompositeReportOlePrivacy.java

         OlePrivacyRule.java

         OlePrivacy_UT.java

    c. Framework: Rice2.x

2. Security

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

...

• OLE_Cataloging_Admin - Create ,edit and provide blanket approve for Separate or Composite ReportPrivacy
• Additional/Permitted Super User - Create ,edit and provide blanket approve for Separate or Composite ReportPrivacy
• User - Can view the Separate or Composite ReportPrivacy

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

       Separate or Composite ReportPrivacy

        a) Create

        b) Edit

...

        d) Blanket Approve

3. OJB-Mapping

       <class-descriptor class="org.kuali.ole.catalog.bo.OleSeperateOrCompositeReportOlePrivacy" table="OLEole_CATcat_SPCPprvcy_RPT_Tt">
                  <field-descriptor name="seperateOrCompositeReportIdprivacyId" column="SPCP_RPTPRVCY_ID" jdbc-type="INTEGERVARCHAR" primarykey="true" autoincrement="true" sequence-name="OLEole_CATcat_SPCPprvcy_RPT_Ss"/>
                  <field-descriptor name="seperateOrCompositeReportCodeprivacyCode" column="SPCP_RPTPRVCY_CD" jdbc-type="VARCHAR" />
                  <field-descriptor name="seperateOrCompositeReportNameprivacyName" column="SPCP_RPTPRVCY_NM" jdbc-type="VARCHAR" />
                  <field-descriptor name="objectIdsource" column="OBJ_IDSRC" jdbc-type="VARCHAR" index="true" />
                  <field-descriptor name="versionNumbersourceDate" column="VERSRC_NBRDT" jdbc-type="BIGINT" locking="trueDATE" />
                  <field-descriptor name="sourceobjectId" column="SRCOBJ_ID" jdbc-type="VARCHAR" index="true"/>
                  <field-descriptor name="sourceDateversionNumber" column="SRCVER_DTNBR" jdbc-type="DATEBIGINT" 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

    Image Added

...

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 Retention Policy Type Receipt Status record.

    b. Participants:

         OleSpecificRetentionPolicyTypeOleReceiptStatus.xml

         OleSpecificRetentionPolicyTypeMaintenanceDocumentOleReceiptStatusMaintenanceDocument.xml

         OleReceiptStatus.java

         OleSpecificRetentionPolicyTypeOleReceiptStatusRule.java

         OleReceiptStatus_UT.java

    c. Framework: Rice2.x

2. Security

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

...

• OLE_Cataloging_Admin - Create ,edit and provide blanket approve for Retention Policy TypeReceipt Status
• Additional/Permitted Super User - Create ,edit and provide blanket approve for Retention Policy TypeReceipt Status
• User - Can view the Retention Policy TypeReceipt Status

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

       Retention Policy TypeReceipt Status

        a) Create

        b) Edit

...

        d) Blanket Approve

3. OJB-Mapping

      <class-descriptor class="org.kuali.ole.catalog.bo.OleSpecificRetentionPolicyTypeOleReceiptStatus" table="OLEole_CATcat_SPFCrcpt_RTN_POL_TYP_Tstat_t">
                     <field-descriptor name="specificRetentionPolicyTypeIdreceiptStatusId" column="SPFCRCPT_RTN_POLSTAT_TYP_ID" jdbc-type="INTEGERVARCHAR" primarykey="true" autoincrement="true" sequence-name="OLEole_CATcat_SPFCrcpt_RTN_POL_TYP_Sstat_s"/>
                     <field-descriptor name="specificRetentionPolicyTypeCodereceiptStatusCode" column="SPFCRCPT_RTN_POLSTAT_TYP_CD" jdbc-type="VARCHAR" />
                     <field-descriptor name="specificRetentionPolicyTypeNamereceiptStatusName" column="SPFCRCPT_RTNSTAT_POL_TYP_NM" jdbc-type="VARCHAR" />
                     <field-descriptor name="objectIdsource" column="OBJ_IDSRC" jdbc-type="VARCHAR" index="true" />
                     <field-descriptor name="versionNumbersourceDate" column="VERSRC_NBRDT" jdbc-type="BIGINT" locking="trueDATE" />
                     <field-descriptor name="sourceobjectId" column="SRCOBJ_ID" jdbc-type="VARCHAR" index="true"/>
                     <field-descriptor name="sourceDateversionNumber" column="SRCVER_DTNBR" jdbc-type="DATE"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

...

          Image Added

15) Record Type Maintenance Document Technical Specification

1.

...

Record 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 Instance Item type Record Type record.

    b. Participants:

         OleInstanceItemTypeOleRecordType.xml

         OleInstanceItemTypeMaintenanceDocumentOleRecordTypeMaintenanceDocument.xml

         OleRecordType.java

         OleRecordTypeRule.java

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

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

       Instance Item type

        a) Create

        b) Edit

        c) View(Inquiry)

        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

...

    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

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

       Record Type

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

       <class-descriptor class="org.kuali.ole.catalog.bo.OleRecordType" table="OLE_CAT_REC_TYP_T">
             <field-descriptor name="recordTypeId" column="REC_TYP_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_REC_TYP_S" />
             <field-descriptor name="recordTypeCode" column="REC_TYP_CD" jdbc-type="VARCHAR" />
             <field-descriptor name="recordTypeName" column="REC_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 Record Type is going to reside in the Rice2.x Schema

   Image Added

16) Reproduction Policy Maintenance Document Technical Specification

1. Reproduction 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 Reproduction Policy record.

    b. Participants:

         OleReproductionPolicy.xml

         OleReproductionPolicyMaintenanceDocument.xml

         OleReproductionPolicy.java

         OleReproductionPolicyRule.java

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

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

       Reproduction Policy

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

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>

4. Services

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

   Image Added

17) Shelving Order Maintenance Document Technical Specification

1. Shelving Order 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 Order record.

    b. Participants:

         OleShelvingOrder.xml

         OleShelvingOrderMaintenanceDocument.xml

         OleShelvingOrder.java

         OleShelvingOrderRule.java

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

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

       Shelving Order

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

     <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

     Image Added

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

         OleShelvingSchemeRule.java

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

     <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

    Image Added

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

         OleSeperateOrCompositeReportRule.java

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

    Image Added

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

         OleSpecificRetentionPolicyTypeRule.java

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

    Image Added

21) Instance Item type Maintenance Document Technical Specification

1. Instance Item 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 Instance Item type record.

    b. Participants:

         OleInstanceItemType.xml

         OleInstanceItemTypeMaintenanceDocument.xml

         OleInstanceItemType.java

         OleInstanceItemTypeRule.java

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

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

       Instance Item type

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

       <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

    Image Added

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

         OleSpecificRetentionPolicyTypeUnitRule.java

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

    Image Added

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

         OleSourceOfTermRule.java

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

    Image Added

24) Statistical Searching Codes Maintenance Document Technical Specification

...

         OleStatisticalSearchingCodes.java

         OleStatisticalSearchingCodesRule.java

         OleStatisticalSearchingCodes_UT.java

    c. Framework: Rice2.x

...

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

Image Added 

25) Country Codes Maintenance Document Technical Specification

...

         OleCountryCodesMaintenanceDocument.xml

         OleCountryCodes.java

         OleCountryCodesRule.java

         OleCountryCodes_UT.java

    c. Framework: Rice2.x

...

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

Image Added