Uploaded image for project: 'ERM Platform'
  1. ERM Platform
  2. ERM-1979

Add/Edit configurable OA properties for an Agreement

    XMLWordPrintable

Details

    • ERM Sprint 134, ERM Sprint 135, ERM Sprint 136, ERM Sprint 138, ERM Sprint 139, ERM Sprint 140, ERM Sprint 141, ERM Sprint 142, ERM Sprint 143, ERM Sprint 144, ERM Sprint 145, ERM Sprint 146
    • Bienenvolk
    • Morning Glory R2 2022

    Description

      Purpose:
      Enable users to add/edit the OA properties for an agreement.
      The implementation should closely follow the existing supplementary properties in Agreements - if in doubt, refer to that implementation, and if there are scenarios missing from the story below assume that the behaviour should be identical to the supplementary properties
      As with supplementary properties, the option to edit/add OA properties on an agreement should only display if there are OA properties defined for the tenant

      User story statement(s):
      As a OA Request manager or ERM librarian,
      I want to add an OA property for an agreement
      so that I ensure the appropriate properties are set for an agreement

      As a OA Request manager or ERM librarian,
      I want to edit the OA properties for an agreement
      so that I ensure the appropriate property value is set for an agreement

      Scenarios:

      1. Scenario:
        • Given an Agreement and one or more OA property defined for the tenant
        • When I edit the agreement
        • Then I see "Open Access properties" accordion, open. by default, positioned between the "Usage data" and "Related agreements" accordions
      2. Scenario:
        • Given an Agreement and one or more OA property defined for the tenant with 'Primary property' set to 'yes'
        • When I edit the agreement and view the "Open Access properties"
        • Then I see all primary OA properties
      3. Scenario:
        • Given an Agreement and one or more OA property defined for the tenant with 'Primary property' set to 'no'
        • When I edit the agreement and view the "Open Access properties"
        • Then I see an 'Optional properties' heading with a 'Add property' button
      4. Scenario:
        • Given an Agreement and one or more OA property defined for the tenant with 'Primary property' set to 'no'
        • When I edit the agreement and view the "Open Access properties"
        • Then I see an 'Optional properties' heading with a 'Add property' button

      Development task breakdown

      • Adding a filter to the custom properties view/edit manifest to only display props with context == null
        • This is `filters=ctx isNull` See example for how to add a filter
      • Creating a new manifest entry based on the custom props manifest for "open access properties", but filtering on context == open access (rather than null)
        • This is `filters=ctx==OpenAccess`
      • * Adding open access properties view/edit manifest to agreements display

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                ostephens Owen Stephens
                ostephens Owen Stephens
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases