E-Resource usage data: Calculate and visualize statistics (UXPROD-1253)

[UXPROD-2860] eUsage harvest summary and results Created: 05/Jan/21  Updated: 22/Nov/21  Resolved: 22/Nov/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Kiwi (R3 2021)
Parent: E-Resource usage data: Calculate and visualize statistics

Type: New Feature Priority: P2
Reporter: Kristen Wilson Assignee: Kristen Wilson
Resolution: Done Votes: 0
Labels: erm, eusage, reporting
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UIPER-8 UI work for manual title matching Closed
Epic Link: E-Resource usage data: Calculate and visualize statistics
Development Team: Thor
Kiwi Planning Points (DO NOT CHANGE): 1
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R4
Rank: Lehigh (MVP Summer 2020): R4
Rank: U of AL (MVP Oct 2020): R5

 Description   

Purpose: When usage is harvested, eUsage will try to make a match between the title in the usage report and a title in the KB. If a match cannot be found, the user needs to have a way to create a match manually. We also need to provide a way for users to view and edit existing matches in case they are incorrect. The system should remember manual matches and edits for future loads.

Harvest Workflow:

  1. A COUNTER report is uploaded to the eUsage app (either manually or through an automated harvest)
  2. The data in the report is processed and stored according to UXPROD-2859 Closed
  3. The outcome of the matching process is displayed on the "Matching Summary" section of the eUsage provider record 

Editing matches workflow

  1. The user clicks on the "view/edit results" link
  2. The user is taken to a detailed view of the harvest results that includes a list of titles and their match status
  3. The user can click on the "create match" or "edit match" links for each title to change the link between the eUsage title and a KB title
  4. When the user clicks this link, a pop up window will open that displays a KB search screen.
  5. The user can search for a title in the KB and select it.
  6. The selected KB title will be matched to the selected eUsage record.
    1. If no match was previously available, it will be added
    2. If a previous match was in place, it will be replaced
  7. The user also has the option to ignore a match – in other words, to say they do not want to match it or continue reviewing it in the future.

Mockups

**Mockups with workflow annotations can be found at: https://folio-org.atlassian.net/wiki/display/RM/eUsage+Reports+Harvest+Summary+and+Results



 Comments   
Comment by Mike Taylor [ 04/Jun/21 ]

Note to self: relevant RAML is at https://github.com/folio-org/mod-eusage-reports/blob/master/src/main/resources/openapi/eusage-reports-1.0.yaml

Comment by Mike Taylor [ 11/Jun/21 ]

Kristen Wilson On eUsage pages such as https://folio-snapshot.dev.folio.org/eusage/view/9362de60-f8b2-4073-bee3-01fa5fc8462f?filters=harvestingStatus.active&sort=label the headings are Harvesting configuration, Matching summary (when the in-development plugin is enabled), COUNTER statistics, Non-COUNTER statistics and Notes.

But the description of this issue refers to the Harvest Results section. Is that a new name for one of the existing sections, a synonym for the Matching summary section in the mockup at https://folio-org.atlassian.net/wiki/display/RM/eUsage+Reports+Harvest+Summary+and+Results , a second new section, or something else again?

(The mockup mentions a "harvest summary" being in the Matching summary section, which made me think that if harvest summary and matching summary are the same thing, then maybe harvest results is also the same thing as harvest summary (and therefore the same thing as matching summary.)

Comment by Kristen Wilson [ 11/Jun/21 ]

Mike Taylor Sorry, that's just more inconsistency based on changing vocabulary. The new accordion should be called "Matching summary." I eliminated the reference to the separate "Harvest results" section. We eliminated that. You can take the mock ups as the official record of what this should look like.

Comment by Mike Taylor [ 11/Jun/21 ]

Thank you, Kristen Wilson, this is helpful.

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