Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Researcher Profile MVP Internal Feedback Collection #285

Closed
kjgarza opened this issue Jan 13, 2020 · 4 comments
Closed

Researcher Profile MVP Internal Feedback Collection #285

kjgarza opened this issue Jan 13, 2020 · 4 comments
Assignees

Comments

@kjgarza
Copy link
Contributor

kjgarza commented Jan 13, 2020

The issue to collect internal feedback

Detailed Specification of the RP for MVP https://docs.google.com/document/d/1y4M8hkdkP28s-kaaxYYiJRnGMtIjkjTlbq-DqpNYKPg/edit

Researcher Profile MVP FEature Summary

  • List of DOIs associated with that ORCID iD
  • Each DOI will display a citation and usage count for that item (if available)
  • Chart of DOIs per year
  • Chart of DOIs by resource type
  • Total citation and usage counts for the researcher

Visit the survey for feedback about the UI
https://www.surveymonkey.de/r/J9RBNK6 t

@kjgarza kjgarza self-assigned this Jan 14, 2020
@kjgarza
Copy link
Contributor Author

kjgarza commented Jan 20, 2020

Ok, I have closed the internal feedback collection for the researcher profile.

It would be fair to say that, from the internal feedback, we need to make improvements to the Researcher Profile Landing Page (Info tab), and the DOI results need small changes. The landing page seems to be not very understandable, so we will need to add some extra information to make it clearer. I have divided the feedback summary into three sections. The first two sections are about the feedback we should definitely include in the MVP for the Landing Page and the DOI List. The third section is the feedback we should consider post-MVP and beyond. The separation mostly radiates in that we have restricted time to make all the changes. The full report of the feedback can be found in https://www.surveymonkey.com/results/SM-ZQ598VCR7/

MVP Landing Page

  • Add textual help to understand the number of counts is for totals. add a legend to the header: "total," similar to "by year."
  • think about making numbers > 0 clickable to send users to that information (e.g., filtering of DOIs in the list view that includes a citation).
  • Link ORCID ID to the ORCID record
  • Move metric counters to their Row
  • Modify the metric counters to include a ring and a smaller size.

MVP DOI list

  • reduce the spacing between summary numbers and URL (I suggest to use the same spacing as without the summary numbers. )
  • use a different coloring for the summary numbers gray might be not active.
  • move the CC icons below the summary numbers.
  • Remove schema version facet (probably doesn't make sense to most researchers.)

POST MVP

Landing Page

  • Tooltips and hover are needed for the resource type and the chart. Fabrica has a problem to show TOOLTIPS; we need to solve this dependency first.
  • Add legends for Resource type chart. This is something already discussed in the MVP and will include post-MVP.

DOI list

  • Think to include facets that allow filtering by DOIs that have citations, views, and/or downloads. This would need further time estimation and planning. Probably the most time-consuming changes would be in the API.
  • Sort by highly cited/downloaded. It cannot be done at the moment but soon.

@kjgarza
Copy link
Contributor Author

kjgarza commented Jan 20, 2020

@kjgarza
Copy link
Contributor Author

kjgarza commented Jan 20, 2020

image

Here its a mockup of how the metric counters can include a ring around.

@kjgarza
Copy link
Contributor Author

kjgarza commented Jan 20, 2020

two new issues were create to track feedback incorporation

@kjgarza kjgarza closed this as completed Jan 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant