Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

15) Record Type Maintenance Document Technical Specification

Info
titleJira

https://jira.kuali.org/browse/OLE-2909

Info
titleRice2.x Framework

Record Type information will be maintained in the ole-rice2 schema and developed in the ole-rice2 application using the new KRAD maintenance doc framework.

1. Record Type Maintenance (Create/Update)

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

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

7. Services

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

16) Reproduction Policy Maintenance Document Technical Specification

Info
titleJira

https://jira.kuali.org/browse/OLE-2909

Info
titleRice2.x Framework

Reproduction Policy information will be maintained in the ole-rice2 schema and developed in the ole-rice2 application using the new KRAD maintenance doc framework.

1. Reproduction Policy Maintenance (Create/Update)

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

    b. Participants:

    c. Framework: Rice2.x

2. Reproduction Policy Search

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

    b. Participants:

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

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

        Reproduction Policy

         a) Create

         b) Edit

         c) View(Inquiry)

         d) Blanket Approve

7. Services

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

17) Shelving Order Maintenance Document Technical Specification

Info
titleJira

https://jira.kuali.org/browse/OLE-2909

Info
titleRice2.x Framework

Shelving Order information will be maintained in the ole-rice2 schema and developed in the ole-rice2 application using the new KRAD maintenance doc framework.

1. Shelving Order Maintenance (Create/Update)

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

    b. Participants:

    c. Framework: Rice2.x

2. Shelving Order Search

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

   b. Participants:

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

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

       Shelving Order

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

7. Services

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

18) *Shelving Schema *Maintenance Document Technical Specification

Info
titleJira

https://jira.kuali.org/browse/OLE-2909

Info
titleRice2.x Framework

Shelving Schema information will be maintained in the ole-rice2 schema and developed in the ole-rice2 application using the new KRAD maintenance doc framework.

1. Shelving Schema Maintenance (Create/Update)

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

    b. Participants:

    c. Framework: Rice2.x

2. Shelving Schema Search

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

   b. Participants:

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

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

       Shelving Schema

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

7. Services

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

Info
titleJira

https://jira.kuali.org/browse/OLE-2909

Info
titleRice2.x Framework

Separate or Composite Report information will be maintained in the ole-rice2 schema and developed in the ole-rice2 application using the new KRAD maintenance doc framework.

1. Separate or Composite Report Maintenance (Create/Update)

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

    b. Participants:

    c. Framework: Rice2.x

2. Separate or Composite Report Search

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

   b. Participants:

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

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

       Separate or Composite Report

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

7. Services

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

Info
titleJira

https://jira.kuali.org/browse/OLE-2909

Info
titleRice2.x Framework

Retention Policy Type information will be maintained in the ole-rice2 schema and developed in the ole-rice2 application using the new KRAD maintenance doc framework.

1. Retention Policy Type Maintenance (Create/Update)

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

    b. Participants:

    c. Framework: Rice2.x

2. Retention Policy Type Search

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

   b. Participants:

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

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

       Retention Policy Type

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

7. Services

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

...

    c. Framework: Rice2.x

3. Security

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

...

        d) Blanket Approve

7. Services

8. Data Model:The DM for Instance Item Type is going to reside in the Rice2.x Schema

...

    c. Framework: Rice2.x

3. Security

    OLE_CAT namespace will be used for defining some Cataloging roles, and edocs
    a. Roles:

...

        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

...

    c. Framework: Rice2.x

3. Security

    OLE_CAT namespace will be used for defining some Cataloging roles, and edocs
    a. Roles:

...

       d) Blanket Approve

7. Services

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

...