[ERM-110] Agreement Detail Record | View attached EBSCO KB e-Resource and access details from eholdings app Created: 01/Mar/19  Updated: 08/Apr/19  Resolved: 08/Apr/19

Status: Closed
Project: ERM Platform
Components: mod-agreements, 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
Gantt End to Start
has to be done before ERM-109 Support the ability to create an Agre... Closed
Requires
requires UIEH-628 Show Package Record: Allow a user to ... Closed
Sub-tasks:
Key
Summary
Type
Status
Assignee
ERM-115 Provide correct data for agreement li... Sub-task Closed  
ERM-116 Dynamically get correct data for agre... Sub-task Closed  
ERM-117 Extend mod-agreements to provide link... Sub-task Closed  
ERM-118 Write back-end tests Sub-task Closed  
ERM-119 Update Agreement Line UI Sub-task Closed md331  
ERM-120 Present non-local links in agreement ... Sub-task Closed md331  
ERM-121 Write front-end tests Sub-task Closed md331  
Sprint: ERM Sprint 60
Story Points: 5
Development Team: Bienenvolk

 Description   

As an electronic resource librarian
I want access to resource metadata to review its status and to make insightful purchasing decisions

Agreements App requirements

  • Allow a user to access EBSCO KB e-Resource metadata via Agreements under E-resources - agreement lines section
  • EBSCO KB e-Resource attached to an Agreement should link to its eholdings app record

Acceptance Criteria
Given I have attached an EBSCO e-Resource [Harvard Business Review in the Business Source Premier package] to an Agreement
When I view/edit that Agreement
Then display the EBSCO KB e-Resource name hyperlinked under the E-resources - agreement lines accordion

Given I have attached an EBSCO e-Resource [Academic Search Premier] to an Agreement
When I click the EBSCO KB-eResource name while editing or viewing
Then display it's eholdings app detail record

Screenshot
See 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 ]

Adding Ian's 3/12 email response
"On 12 Mar 2019, at 16:57, Ian Ibbotson <ian.ibbotson@k-int.com> wrote:
Adding Steve in so he can double check my workings out.
OK - Firstly, there are some prerequisites - Obviously, we need the codex package search endpoint for this to be completed - Can you confirm that is in the testing build and working as expected? We'll assume so.
1. Agreements App: Search EBSCO KB via eResources Tab
2. Agreements app: Access EBSCO KB package and title metadata
Open Unassigned
3. Agreements app: Attach an EBSCO KB package or title to an Agreement line

  • Subtasks on these three:
  • .5d to update the UI to provide radio button toggles to allow users to select between local-kb, Codex-Titles and Codex-Packages (Unless codex no supports unified search over titles and packages) - and assuming that UX is acceptable to you?
  • Define the internal abstract class for searching KB sources - done 0d
  • Implement that class for local-kb - Done - 0d
  • Implement that class for Codex-Titles - .5d for baseline, .5d for converting the filter params
  • Implement that class for Codex-Packages - .5d + .5d as above, assuming this component is available and working
  • Update ui-agreements to use this new layout in eResources search results screen - .5d
  • Define abstract interface for returning availability options -.5d
  • Implement for local-KB - .5d
  • Implement for codex-titles - .5d
  • Implement for codex-packages - .5d
  • Extend interface for fetching existing entitlements/agreements via external reference - 1d
  • Optionally - add default settings for default radio button source on KB select - 1d (New backend interface needed, so bit longer than you might expect) "
Comment by Khalilah Gambrell [ 21/Mar/19 ]

This comment is no longer applicable as we have decided on another implentation approach.

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