OLE Instance Editor Maintenance Documents Technical Specifications

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

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

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

12) Notation Type Maintenance Document Technical Specification

1. Notation Type Maintenance (Create/Update)

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

    b. Participants:

    c. Framework: Rice2.x

2. Notation Type Search

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

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

        Notation Type

         a) Create

         b) Edit

         c) View(Inquiry)

         d) Blanket Approve

7. Services

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

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

    b. Participants:

    c. Framework: Rice2.x

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

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

7. Services

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

    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:

    c. Framework: Rice2.x

2. Receipt Status 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:

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

7. Services

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

21) Instance Item Type Maintenance Document Technical Specification

1. Instance Item Type Maintenance (Create/Update)

    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:

    c. Framework: Rice2.x

2. Instance Item Type 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:

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

7. Services

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

    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:

    c. Framework: Rice2.x

2. Specific Retention Policy Type Unit 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:

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

7. Services

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

    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:

    c. Framework: Rice2.x

2. Source Of Term 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:

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

7. Services

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