Page Comparison

...

         OleLocationStatusMaintenanceDocument.xml

         OleLocationStatusLookup.xml

         OleLocationStatus.java

         OleLocationStatusMaintenanceImpl.java

         OleLocationStatusRule.java

         OleLocationStatus_UT.java

    c. Framework: Rice2.x

...

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

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

         OleAcquisitionMethodMaintenanceDocument.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: Rice2.x

2. Security

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

3. OJB-Mapping

4. Services

...

      <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

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:

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

    b. Participants:

         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:

         OleLendingPolicy.xml

         OleLendingPolicyMaintenanceDocument.xml

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

       <class-descriptor class="org.kuali.ole.catalog.bo.OleLendingPolicy" table="OLE_CAT_LND_POL_T">
            <field-descriptor name="lendingPolicyId" column="LND_POL_ID " jdbc-type="INTEGER" primarykey="true" index="true" autoincrement="true" sequence-name="OLE_CAT_LND_POL_s "></field-descriptor>
            <field-descriptor name="lendingPolicyCode" column="LND_POL_CD" jdbc-type="VARCHAR"></field-descriptor>
            <field-descriptor name="lendingPolicyName" column="LND_POL_NM" jdbc-type="VARCHAR"></field-descriptor>
            <field-descriptor name="source" column="SRC" jdbc-type="VARCHAR"></field-descriptor>
            <field-descriptor name="sourceDate" column="SRC_DT" jdbc-type="DATE"></field-descriptor>
            <field-descriptor name="objectId" column="OBJ       <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 will be used to create and update a new or an existing Field Encoding Level record. 

    b. Participants:

         OleFieldEncodingLevel.xml

         OleFieldEncodingLevelMaintenanceDocument.xml

         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

    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="VARCHARINTEGER" indexprimarykey="true" autoincrement="true" sequence-name="OLE_CAT_FLD_ENCD_LVL_S"/>
                         <field-descriptor name="versionNumberfieldEncodingLevelCode" column="VER_NBRFLD_ENCD_LVL_CD" jdbc-type="BIGINTVARCHAR" locking="true" />
                         <field-descriptor name="activefieldEncodingLevelName" column="ROWFLD_ENCD_ACTLVL_INDNM" jdbc-type="VARCHAR"   conversion="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion/>
             <field-descriptor name="source" column="SRC" jdbc-type="VARCHAR" />
     </class-descriptor>

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

1. Notation Type Maintenance (Create/Update/Search)

    a. KRAD Design: A simple KRAD maintenance document will be              <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 Notation Type General Retention Policy record. 

    b. Participants:

         OleNotationTypeOleGeneralRetentionPolicy.xml

         OleNotationTypeMaintenanceDocumentOleGeneralRetentionPolicyMaintenanceDocument.xml

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

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

       Notation Type

                General Retention Policy

          a) Create

                  b) Edit

                  c) View(Inquiry)

                  d) Blanket Approve

3. OJB-Mapping

               <class-descriptor class="org.kuali.ole.catalog.bo.OleNotationTypeOleGeneralRetentionPolicy" table="oleOLE_CAT_catGEN_ntnRTN_typPOL_tT">
                         <field-descriptor name="notationTypeIdgeneralRetentionPolicyId" column="NTNGEN_RTN_TYPPOL_ID" jdbc-type="VARCHARINTEGER" primarykey="true" autoincrement="true" sequence-name="oleOLE_CAT_catGEN_ntnRTN_typPOL_sS"/>
                         <field-descriptor name="notationTypeCodegeneralRetentionPolicyCode" column="NTNGEN_RTN_TYPPOL_CD" jdbc-type="VARCHAR" />
                         <field-descriptor name="notationTypeNamegeneralRetentionPolicyName" column="NTNGEN_RTN_TYPPOL_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="objectIdactive" column="OBJROW_ACT_IDIND" jdbc-type="VARCHAR" indexconversion="trueorg.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion" />
                         <field-descriptor name="versionNumberobjectId" column="VEROBJ_NBRID" jdbc-type="BIGINTVARCHAR" lockingindex="true"/>
                         <field-descriptor name="activeversionNumber" column="ROWVER_ACT_INDNBR" jdbc-type="VARCHARBIGINT"   conversionlocking="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversiontrue"/>
          </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 Privacy Lending Policy record.

    b. Participants:

         OlePrivacyOleLendingPolicy.xml

         OlePrivacyMaintenanceDocumentOleLendingPolicyMaintenanceDocument.xml

         OlePrivacyOleLendingPolicy.java

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

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

       PrivacyLending Policy

        a) Create

        b) Edit

...

        d) Blanket Approve

3. OJB-Mapping

       <class-descriptor class="org.kuali.ole.catalog.bo.OlePrivacyOleLendingPolicy" table="oleOLE_CAT_catLND_prvcyPOL_tT">
                      <field-descriptor name="privacyIdlendingPolicyId" column="PRVCYLND_POL_ID " jdbc-type="VARCHARINTEGER" primarykey="true" index="true" autoincrement="true" sequence-name="oleOLE_CAT_catLND_prvcyPOL_s "></>
          field-descriptor>
            <field-descriptor name="privacyCodelendingPolicyCode" column="PRVCYLND_POL_CD" jdbc-type="VARCHAR"></>
          field-descriptor>
            <field-descriptor name="privacyNamelendingPolicyName" column="PRVCYLND_POL_NM" jdbc-type="VARCHAR"></>field-descriptor>
            <field-descriptor name="source" column="SRC" jdbc-type="VARCHAR"></>field-descriptor>
                      <field-descriptor name="sourceDate" column="SRC_DT" jdbc-type="DATE"></>
          field-descriptor>
            <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

...

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

    b. Participants:

         OleReceiptStatusOleNotationType.xml

         OleReceiptStatusMaintenanceDocumentOleNotationTypeMaintenanceDocument.xml

         OleNotationType.java

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

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

       Receipt StatusNotation Type

        a) Create

        b) Edit

...

        d) Blanket Approve

3. OJB-Mapping

             <class-descriptor class="org.kuali.ole.catalog.bo.OleReceiptStatusOleNotationType" table="ole_cat_rcptntn_stattyp_t">
                        <field-descriptor name="receiptStatusIdnotationTypeId" column="RCPTNTN_STATTYP_ID" jdbc-type="VARCHAR" primarykey="true" autoincrement="true" sequence-name="ole_cat_rcptntn_stattyp_s"/>
                        <field-descriptor name="receiptStatusCodenotationTypeCode" column="RCPTNTN_STATTYP_CD" jdbc-type="VARCHAR" />
                        <field-descriptor name="receiptStatusNamenotationTypeName" column="RCPTNTN_STATTYP_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

...

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

    b. Participants:

         OlePrivacy.xml

         OlePrivacyMaintenanceDocument.xml

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

    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

...

. 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

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

    b. Participants:

         OleReceiptStatus.xml

         OleReceiptStatusMaintenanceDocument.xml

         OleReceiptStatus.java

         OleReceiptStatusRule.java

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

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

    b. Participants:

         OleRecordType.xml

         OleRecordTypeMaintenanceDocument.xml

         OleRecordType.java

         OleRecordTypeRule.java

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

...

         OleReproductionPolicyMaintenanceDocument.xml

         OleReproductionPolicy.java

         OleReproductionPolicyRule.java

         OleReproductionPolicy_UT.java

    c. Framework: Rice2.x

...

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

...

         OleShelvingOrderMaintenanceDocument.xml

         OleShelvingOrder.java

         OleShelvingOrderRule.java

         OleShelvingOrder_UT.java

    c. Framework: Rice2.x

...

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

...

         OleShelvingSchemeMaintenanceDocument.xml

         OleShelvingScheme.java

         OleShelvingSchemeRule.java

         OleShelvingScheme_UT.java

    c. Framework: Rice2.x

...

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

...

         OleSeperateOrCompositeReport.java

         OleSeperateOrCompositeReportRule.java

         OleSeperateOrCompositeReport_UT.java

    c. Framework: Rice2.x

...

       <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

...

         OleSpecificRetentionPolicyType.java

         OleSpecificRetentionPolicyTypeRule.java

         OleSpecificRetentionPolicyType_UT.java

    c. Framework: Rice2.x

...

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

...

         OleInstanceItemType.java

         OleInstanceItemTypeRule.java

         OleInstanceItemType_UT.java

    c. Framework: Rice2.x

...

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

...

         OleSpecificRetentionPolicyTypeUnitMaintenanceDocument.xml

         OleSpecificRetentionPolicyTypeUnit.java

         OleSpecificRetentionPolicyTypeUnitRule.java

         OleSpecificRetentionPolicyTypeUnit_UT.java

    c. Framework: Rice2.x

...

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

...

         OleSourceOfTermMaintenanceDocument.xml

         OleSourceOfTerm.java

         OleSourceOfTermRule.java

         OleSourceOfTerm_UT.java

    c. Framework: Rice2.x

...

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

...

         OleStatisticalSearchingCodesMaintenanceDocument.xml

         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