E-Resource usage data: Report management (UXPROD-576)

[UXPROD-954] Input and storing of SUSHI-credentials Created: 18/Jun/18  Updated: 16/Sep/20  Resolved: 14/Jan/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q4 2018
Parent: E-Resource usage data: Report management

Type: New Feature Priority: P3
Reporter: Annika Schröer Assignee: Annika Schröer
Resolution: Done Votes: 0
Labels: ERM
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: E-Resource usage data: Report management
Analysis Estimate: Medium < 5 days
Front End Estimate: Medium < 5 days
Front-End Confidence factor: High
Back End Estimate: Medium < 5 days
Development Team: Leipzig
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R4
Rank: Lehigh (MVP Summer 2020): R4
Rank: TAMU (MVP Jan 2021): R4

 Description   
  • Store SUSHI credentials (requestor ID, ...) with the Usage statistics providers.


 Comments   
Comment by Cate Boerema (Inactive) [ 13/Sep/18 ]

Hi Owen Stephens and Richard Redweik. UXPROD features should be assigned to the PO. We assign work to developers at the story level. Hope it's okay - I'm going to swap Richard out for Owen on this. Thx!

Comment by Cate Boerema (Inactive) [ 13/Sep/18 ]

Per Owen Stephens, I am assigning all the features for the usage data epic to Annika.

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