Page Comparison

...

    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

         OleTypeOfOwnershipMaintenanceDocument.xml

         OleTypeOfOwnership.java

    c. Framework: Rice2.x

2. Security

...

        d) Blanket Approve

3. OJB-Mapping

4. Services

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

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:

    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

4. Services

      <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

...

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 Access Method Action record.

    b. Participants:

         OleAction.xml

         OleActionMaintenanceDocument.xml

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

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

      Access Method Action

       a) Create

       b) Edit

       c) View(Inquiry)

       d) Blanket Approve

3. OJB-Mapping

4. Services

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

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:

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

...

4)

...

Access Method Maintenance Document Technical Specification

1.

...

Access Method 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 Completeness Access Method record. 

    b. Participants:    c.

         OleAccessMethod.xml

         OleAccessMethodMaintenanceDocument.xml

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

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

        Completeness

                Access Method

       a) Create

                 b) Edit

                 c) View(Inquiry)

                 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

        <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

...

5)

...

Acquisition Method Maintenance Document Technical Specification

1.

...

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

    b. Participants:

         OleAcquisitionMethod.xml

         OleAcquisitionMethodMaintenanceDocument.xml

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

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

        Encoding Level      Acquisition Method

         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

...

       <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

...

6)

...

Completeness Maintenance Document Technical Specification

1.

...

Completeness 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 Completeness record. 

    b. Participants:

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

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

            General Retention PolicyCompleteness

          a) Create

          b) Edit

...

          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 maintenance document will be used to create and update a new or an existing Lending Policy ElARelationship record. 

    b. Participants:

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

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

       Lending Policy

                ElARelationship

         a) Create

                 b) Edit

                 c) View(Inquiry)

                 d) Blanket Approve

3. OJB-Mapping

4. Services

5. Data Model:The DM for

...

ElARelationship is going to reside in the Rice2.x Schema

...

8)

...

Encoding Level Maintenance Document Technical Specification

1.

...

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

    b. Participants:         OleNotationType.xml    

    OleNotationTypeMaintenanceDocument.xml

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

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

       Notation Type

                Encoding Level

         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 maintenance document will be used to create and update a new or an existing Privacy Field Encoding Level 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

...

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

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

       Privacy

                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 maintenance document will be used to create and update a new or an existing Receipt Status General Retention Policy 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

...

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

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

       Receipt Status

                General Retention Policy

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

    b. Participants:

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

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

       Record TypeLending Policy

        a) Create

        b) Edit

...

        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

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

    b. Participants:

         OleReproductionPolicyOleNotationType.xml

         OleReproductionPolicyMaintenanceDocumentOleNotationTypeMaintenanceDocument.xml

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

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

       Reproduction PolicyNotation Type

        a) Create

        b) Edit

...

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

    b. Participants:

         OleShelvingOrderOleReceiptStatus.xml

         OleShelvingOrderMaintenanceDocumentOleReceiptStatusMaintenanceDocument.xml

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

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

       Shelving OrderReceipt Status

        a) Create

        b) Edit

...

        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

...

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

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

    b. Participants:

         OleShelvingSchemeOleReproductionPolicy.xml

         OleShelvingSchemeMaintenanceDocumentOleReproductionPolicyMaintenanceDocument.xml

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

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

       Shelving SchemaReproduction Policy

        a) Create

        b) Edit

...

        d) Blanket Approve

3. OJB-Mapping

           <class-descriptor class="org.kuali.ole.catalog.bo.OleShelvingSchemeOleReproductionPolicy" table="OLE_CAT_SHVLGREPRO_SCHMPOL_T">
        <field-descriptor name="shelvingSchemeIdreproductionPolicyId" column="SHVLGREPRO_SCHMPOL_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_SHVLGREPRO_SCHMPOL_S" />
        <field-descriptor name="shelvingSchemeCodereproductionPolicyCode" column="SHVLGREPRO_SCHMPOL_CD" jdbc-type="VARCHAR" />
        <field-descriptor name="shelvingSchemeNamereproductionPolicyName" column="SHVLGREPRO_SCHMPOL_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

...

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

    b. Participants:

         OleSeperateOrCompositeReportOleShelvingOrder.xml

         OleSeperateOrCompositeReportMaintenanceDocumentOleShelvingOrderMaintenanceDocument.xml

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

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

       Separate or Composite ReportShelving Order

        a) Create

        b) Edit

...

        d) Blanket Approve

3. OJB-Mapping

            <class-descriptor class="org.kuali.ole.catalog.bo.OleSeperateOrCompositeReportOleShelvingOrder" table="OLE_CAT_SPCPSHVLG_RPTORD_T">
        <field-descriptor name="seperateOrCompositeReportIdshelvingOrderId" column="SPCPSHVLG_RPTORD_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_SPCPSHVLG_RPTORD_S" />
        <field-descriptor name="seperateOrCompositeReportCodeshelvingOrderCode" column="SPCPSHVLG_RPTORD_CD" jdbc-type="VARCHAR" />
        <field-descriptor name="seperateOrCompositeReportNameshelvingOrderName" column="SPCPSHVLG_RPTORD_NM" jdbc-type="VARCHAR" />
        <field-descriptor name="objectId" column="OBJ_ID" jdbc-type="VARCHAR" index="true"/>
        <field-descriptor name="versionNumber" column="VER_NBR" jdbc-type="BIGINT" locking="true" />
        <field-descriptor name="source" column="SRC" jdbc-type="VARCHAR" />
        <field-descriptor name="sourceDate" column="SRC_DT" jdbc-type="DATE" />
        <field-descriptor name="active" column="ROW_ACT_IND" jdbc-type="VARCHAR" conversion="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion" />
    </class-descriptor>

4. Services

5. Data Model:The DM for

...

Shelving Order is going to reside in the Rice2.x Schema

...

18) Shelving Schema Maintenance Document Technical Specification

1.

...

Shelving Schema Maintenance (Create/Update/Search)

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

    b. Participants:

         OleSpecificRetentionPolicyTypeOleShelvingScheme.xml

         OleSpecificRetentionPolicyTypeMaintenanceDocumentOleShelvingSchemeMaintenanceDocument.xml

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

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

       Retention Policy TypeShelving Schema

        a) Create

        b) Edit

...

        d) Blanket Approve

3. OJB-Mapping

           <class-descriptor class="org.kuali.ole.catalog.bo.OleSpecificRetentionPolicyTypeOleShelvingScheme" table="OLE_CAT_SPFC_RTN_POL_TYPSHVLG_SCHM_T">
        <field-descriptor name="specificRetentionPolicyTypeIdshelvingSchemeId" column="SPFCSHVLG_RTN_POLSCHM_TYP_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_SPFCSHVLG_RTNSCHM_POL_TYP_S" />
        <field-descriptor name="specificRetentionPolicyTypeCodeshelvingSchemeCode" column="SPFC_RTN_POL_TYPSHVLG_SCHM_CD" jdbc-type="VARCHAR" />
        <field-descriptor name="specificRetentionPolicyTypeNameshelvingSchemeName" column="SPFC_RTN_POL_TYPSHVLG_SCHM_NM" jdbc-type="VARCHAR" />
        <field-descriptor name="objectId" column="OBJ_ID" jdbc-type="VARCHAR" index="true"/>
        <field-descriptor name="versionNumber" column="VER_NBR" jdbc-type="BIGINT" locking="true" />
        <field-descriptor name="source" column="SRC" jdbc-type="VARCHAR" />
        <field-descriptor name="sourceDate" column="SRC_DT" jdbc-type="DATE" />
        <field-descriptor name="active" column="ROW_ACT_IND" jdbc-type="VARCHAR" conversion="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion" />
    </class-descriptor>

4. Services

5. Data Model:The DM for

...

Shelving Schema is going to reside in the Rice2.x Schema

...

19) Separate or Composite Report Maintenance Document Technical Specification

1.

...

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

    a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Instance Item type Separate or Composite Report record.

    b. Participants:

         OleInstanceItemTypeOleSeperateOrCompositeReport.xml

         OleInstanceItemTypeOleSeperateOrCompositeReportMaintenanceDocument.xml

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

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

       Instance Item typeSeparate or Composite Report

        a) Create

        b) Edit

...

        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

         OleSpecificRetentionPolicyTypeUnit.xml

         OleSpecificRetentionPolicyTypeUnit.java

    c. Framework: Rice2.x

2. Security

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

    a. Roles:

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

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

       Specific Retention Policy Type Unit

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

       <class-descriptor class="org.kuali.ole.catalog.bo.OleSeperateOrCompositeReport" table="OLE_CAT_SPCP_RPT_T">
        <field-descriptor name="seperateOrCompositeReportId" column="SPCP_RPT_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_SPCP_RPT_S" />
        <field-descriptor name="seperateOrCompositeReportCode" column="SPCP_RPT_CD" jdbc-type="VARCHAR" />
        <field-descriptor name="seperateOrCompositeReportName" column="SPCP_RPT_NM" jdbc-type="VARCHAR" />
        <field-descriptor name="objectId" column="OBJ_ID" jdbc-type="VARCHAR" index="true"/>
        <field-descriptor name="versionNumber" column="VER_NBR" jdbc-type="BIGINT" locking="true" />
        <field-descriptor name="source" column="SRC" jdbc-type="VARCHAR" />
        <field-descriptor name="sourceDate" column="SRC_DT" jdbc-type="DATE" />
        <field-descriptor name="active" column="ROW_ACT_IND" jdbc-type="VARCHAR" conversion="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion" />
    </class-descriptor>

4. Services

5. Data Model:The DM for

...

Separate or Composite Report is going to reside in the Rice2.x Schema

...

20) Retention Policy Type Maintenance Document Technical Specification

1.

...

Retention Policy Type Maintenance (Create/Update/Search)

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

    b. Participants:

         OleSourceOfTermOleSpecificRetentionPolicyType.xml

         OleSourceOfTermMaintenanceDocumentOleSpecificRetentionPolicyTypeMaintenanceDocument.xml

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

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

       Source of TermRetention Policy Type

        a) Create

        b) Edit

...

        d) Blanket Approve

3. OJB-Mapping

4. Services

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

24) Statistical Searching Codes Maintenance Document Technical Specification

1. Statistical Searching Codes Maintenance (Create/Update/Search)

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

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

       Statistical Searching Codes

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

4. Services

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

25) Country Codes Maintenance Document Technical Specification

1. Country Codes Maintenance (Create/Update/Search)

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

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

       Country Codes

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

...

      <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

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

    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

3. OJB-Mapping

4. Services

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

24) Statistical Searching Codes Maintenance Document Technical Specification

1. Statistical Searching Codes Maintenance (Create/Update/Search)

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

    b. Participants:

         OleStatisticalSearchingCodes.xml

         OleStatisticalSearchingCodesMaintenanceDocument.xml

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

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

       Statistical Searching Codes

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

       <class-descriptor class="org.kuali.ole.catalog.bo.OleStatisticalSearchingCodes" table="OLE_CAT_STAT_SRCH_CD_T">
           <field-descriptor name="statisticalSearchingCodeId" column="STAT_SRCH_CD_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_STAT_SRCH_CD_S" />
           <field-descriptor name="statisticalSearchingCode" column="STAT_SRCH_CD" jdbc-type="VARCHAR" />
           <field-descriptor name="statisticalSearchingName" column="STAT_SRCH_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 Statistical Searching Codes is going to reside in the Rice2.x Schema

25) Country Codes Maintenance Document Technical Specification

1. Country Codes Maintenance (Create/Update/Search)

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

    b. Participants:

         OleCountryCodes.xml

         OleCountryCodesMaintenanceDocument.xml

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

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

       Country Codes

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

         <class-descriptor class="org.kuali.ole.catalog.bo.OleCountryCodes" table="OLE_CAT_LOC_COUNTRY_CD_T">
             <field-descriptor name="countryCodeId" column="LOC_COUNTRY_CD_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" sequence-name="OLE_CAT_LOC_COUNTRY_CD_S" />
             <field-descriptor name="countryCode" column="LOC_COUNTRY_CD" jdbc-type="VARCHAR" />
             <field-descriptor name="countryName" column="LOC_COUNTRY_NM" jdbc-type="VARCHAR" />
             <field-descriptor name="countryRegionName" column="LOC_COUNTRY_REGION_NM" jdbc-type="VARCHAR" />
             <field-descriptor name="countryNameSequence" column="LOC_COUNTRY_SEQUENCE_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 Country Codes is going to reside in the Rice2.x Schema