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

Add Embargo to "E-resource in package" and "Agreement line" display

    XMLWordPrintable

Details

    • ERM Sprint 86, ERM Sprint 87, ERM Sprint 88
    • Bienenvolk

    Description

      Following implementation of Embargo a.k.a "Moving wall" data in the Agreements local KB, we should display this information alongside coverage statements.
      See ERM-800 for information on where this will be returned in JSON

      The information should be displayed for a PCI in the "Coverage" column underneath any coverage statements. There should be vertical spacing between the moving wall information and any coverage data. See the mockup for examples

      A PCI can have a maximum of 1 ‘"Moving wall start" and a maximum of 1 "moving wall end"

      Scenario 1: display moving wall start

      Display "Moving wall start:" [Length] and the appropriate Unit ("days", "months", "years"). E.g.

      Moving wall start: 365 days

      or

      Moving wall start: 6 months

      Scenario 2: display moving wall end

      Display "Moving wall end:" [Length] and the appropriate Unit ("days", "months", "years"). E.g.

      Moving wall end: 250 days

      Testing file
      simple_package_simple_title_with_embargo.json

      TestRail: Results

        Attachments

          1. coverage_embargo.png
            coverage_embargo.png
            26 kB
          2. coverage_embargo2.png
            coverage_embargo2.png
            25 kB
          3. monograph.png
            monograph.png
            19 kB
          4. screenshot-1.png
            screenshot-1.png
            58 kB
          5. screenshot-2.png
            screenshot-2.png
            29 kB
          6. screenshot-3.png
            screenshot-3.png
            18 kB
          7. simple_package_simple_title_with_embargo.json
            1.0 kB

          Issue Links

            defines

            New Feature - New feature requests UXPROD-2344 Agreements | Local KB | Support KBART style Embargo statements

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            is blocked by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ERM-800 Add "Embargo" to local KB data model and imports

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            is cloned by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ERM-807 Add Embargo to PCI in Agreement exports

            • TBD - To be determined
            • Closed
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ERM-875 Use standard coverage display in "Agreements for this resource" and "Options for acquiring e-resource"

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ERM-800 Add "Embargo" to local KB data model and imports

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Activity

              People

                sosguthorpe Steve Osguthorpe
                ostephens Owen Stephens
                Gill Osguthorpe Gill Osguthorpe
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases