[ERM-108] Agreements App | Suppress Agreements app features available in eholdings app Created: 02/Mar/19  Updated: 08/Apr/19  Resolved: 08/Apr/19

Status: Closed
Project: ERM Platform
Components: ui-agreements
Affects versions: None
Fix versions: None

Type: Story Priority: P3
Reporter: Khalilah Gambrell Assignee: Unassigned
Resolution: Done Votes: 0
Labels: eholdings_integration, erm
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-1548 Agreements work: EBSCO KB + Agreement... Closed
Sub-tasks:
Key
Summary
Type
Status
Assignee
ERM-111 Build settings page Sub-task Closed  
ERM-112 Build wrapper component for suppression Sub-task Closed  
ERM-113 Use wrapper component in agreements Sub-task Closed  
ERM-114 Write tests Sub-task Closed  
Sprint: ERM Sprint 60
Story Points: 4
Development Team: Bienenvolk

 Description   

As a librarian using the eholdings app
I do not want to see non-supported features on the Agreements app
Because it is a poor UX.

Requirements

  • For users of the eholdings app, the following features should be suppressed from the Agreements UI
    • e-Resources tab
    • e-Resource detail record
    • E-resources covered by this agreement section
    • Basket
  • Implementation
    • must be flexible to easily suppress additional features (e.g. title history)
    • must be flexible to support implementing any suppressed feature if desired at a later date
    • Goal - if it is decided to implement a once suppressed feature it needs to be a seamless as possible and does not require significant refactoring of the app.

Acceptance Criteria
Given my library has configured the Agreements app to use the eholdings app for searching AND attaching an e-Resource(s) to an Agreement
When I access the Agreements app
Then I should not see the following features
– e-Resources tab
– e-Resource detail record
– E-resources covered by this agreement section
– Basket

Screenshot
Slides 5 and 6: https://docs.google.com/presentation/d/1bmdHz35Wuj_URPIDlxDdHKkXRwPo9ZDGSvBo_w6cE1o/edit#slide=id.g52294d025a_0_23



 Comments   
Comment by Khalilah Gambrell [ 12/Mar/19 ]

Ian Ibbotson (Use this one), I believe there are features (e.g. title history) that are planned for Agreements. No EBSCO KB API endpoint can provide this information. So in this case is there a way to not show this option? That is the only feature I can think of at this time. Does that make sense?

Generated at Fri Feb 09 00:16:31 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.