OLE Instance Editor Maintenance Documents Technical Specifications

Technical Specifications for the 25 Maintenance Documents to be created for the Instance Editor.

1) Location Status Maintenance Document Technical Specification

1. Location Status Maintenance (Create/Update)

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

    b. Participants:

    c. Framework: Rice2.x

2. Location Status Search

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

   b. Participants:

   c. Framework: Rice2.x

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

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

       Location Status

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

7. Services

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

2) Type of Ownership Maintenance Document Technical Specification

1. Type Of Ownership Maintenance (Create/Update)

    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:

    c. Framework: Rice2.x

2. Type Of Ownership 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:

    c. Framework: Rice2.x

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

7. Services

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

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

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

7. Services

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

    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:

    c. Framework: Rice2.x

2. Access Method 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:

    c. Framework: Rice2.x

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

7. Services

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

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

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

7. Services

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

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

    b. Participants:

    c. Framework: Rice2.x

2. Location Status Search

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

    b. Participants:

    c. Framework: Rice2.x

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

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

        Completeness

          a) Create

          b) Edit

          c) View(Inquiry)

          d) Blanket Approve

7. Services

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

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

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

7. Services

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

    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:

    c. Framework: Rice2.x

2. EncodingLevel 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:

    c. Framework: Rice2.x

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

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

        Encoding Level

         a) Create

         b) Edit

         c) View(Inquiry)

         d) Blanket Approve

7. Services

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

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

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

7. Services

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

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

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

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

        General Retention Policy

          a) Create

          b) Edit

          c) View(Inquiry)

          d) Blanket Approve

7. Services

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

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

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

7. Services

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