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

Single article line chart display (test.parascope.io) #113

Closed
jenniferlin15 opened this issue Dec 12, 2014 · 10 comments
Closed

Single article line chart display (test.parascope.io) #113

jenniferlin15 opened this issue Dec 12, 2014 · 10 comments

Comments

@jenniferlin15
Copy link

The XML downloads have disappeared from the single article line chart display.
Please add this third line to the chart.

Also, the display needs to be cleaned up.
Title: Article Usage over Time

Axis Labels:

  • Total Usage
  • Date
    These should be located on the outside of the graph. The font also needs to be increased - currently not legible due to size.

Graph Legend:

  • HTML Views
  • PDF Downloads
  • XML Downloads
    Make the bubbles in the legend bigger and align the corresponding text with the items (currently too high).

Bubble hover over:

  • [Title]
  • Journal:
  • Date: [convert timestamp. insert month and year.]
  • Usage: [total usage for HTML, PDF, XML for PLOS and PMC]
    The fonts need to be increased - currently not legible due to size.
@jure
Copy link
Contributor

jure commented Dec 12, 2014

Single article bubble chart display? You mean the line chart?

XML wasn't initially included because the API call needs to include info=detail,

"events": [
{
"month": "10",
"year": "2012",
"pdf_views": "177",
"xml_views": "35",
"html_views": "2520"
},

which makes things a bit slower. Given that ALM is plenty fast again, I can include that, sure.

The rest of the feedback sounds good too, thanks!

@mfenner
Copy link
Member

mfenner commented Dec 12, 2014

You can also get the xml downloads without info=detail:

xml = total - (html + pdf)

See https://github.com/articlemetrics/lagotto/blob/master/app/models/sources/counter.rb#L19-L22 for details.

@jure
Copy link
Contributor

jure commented Dec 12, 2014

We're talking about time-series data, right? Not just single point in time. Where in the API response would that be:

{
"name": "counter",
"display_name": "Counter",
"group_name": "viewed",
"events_url": null,
"by_day": [],
"by_month": [
{
"month": 10,
"year": 2012,
"html": 2520,
"pdf": 177
}
}

I only have html and pdf, for the counter, no total.

@jure jure added the line label Dec 12, 2014
@jure jure changed the title Single article bubble chart display (test.parascope.io) Single article line chart display (test.parascope.io) Dec 12, 2014
@mfenner
Copy link
Member

mfenner commented Dec 12, 2014

You are right: https://github.com/articlemetrics/lagotto/blob/master/app/models/history.rb#L137-L150 For counter we have only html and pdf in time series, no total. I didn't care about the xml enough to expose it.

@jenniferlin15 do you really want xml downloads? We would need to change the ALM API for that, which I would rather postpone until we have done the changes in the database backend.

@jure
Copy link
Contributor

jure commented Dec 12, 2014

To be clear, the previous visualization had XML downloads, but it did that by making two requests to the API and combining the results: https://github.com/articlemetrics/alm-report/blob/2e378a5c1bf3eb1d35d4139fbb486aa96ebbf0c1/lib/alm_request.rb#L197-L261

@mfenner
Copy link
Member

mfenner commented Dec 12, 2014

Yes, my point is mostly about making this more efficient. Which might not be so important for a single article, where the API is probably fast enough.

Another consideration is whether we want to include other sources in this, something we can do since mid-2014 since we collect the numbers. We could also display daily stats the first 30 days after publication in a separate chart. That is up to @jenniferlin15, and of course the amount of work that would be needed.

@jure
Copy link
Contributor

jure commented Dec 12, 2014

Actually, sure, this is the single article visualization, which already requests the info=detail, because it needs the locations for Mendeley bookmarks. In that case XML downloads are no additional effort in terms of API, just a matter of including it in the chart. Will do.

@mfenner
Copy link
Member

mfenner commented Dec 12, 2014

Perfect.

@jure
Copy link
Contributor

jure commented Dec 16, 2014

I managed to address some of this feedback:

  • moved the axis labels
  • bigger fonts
  • tooltip changes (partially, due to the fact that every hover event is for a specific point on the chart, and thus can't include data about other points. this is something I need to address still)
  • added XML line
  • some legend feedback (it's not possible at this point to have a custom legend marker, it's constructed from the line name and the axis name, so "Html" + "Views")

image

Leaving this one open, but maybe this is good for now?

@jenniferlin15
Copy link
Author

I think it's fine for now. Please just correct the capitalizatino of the
legend:

  • HTML Views
  • PDF Views
  • XML Views.

Thanks!

On Tue, Dec 16, 2014 at 6:36 AM, Jure Triglav [email protected]
wrote:

I managed to address some of this feedback:

  • moved the axis labels
  • bigger fonts
  • tooltip changes (partially, due to the fact that every hover event
    is for a specific point on the chart, and thus can't include data about
    other points. this is something I need to address still)
  • added XML line
  • some legend feedback (it's not possible at this point to have a
    custom legend marker, it's constructed from the line name and the axis
    name, so "Html" + "Views")

[image: image]
https://cloud.githubusercontent.com/assets/238667/5455146/38012e58-8539-11e4-9831-9e09f951e05f.png

Leaving this one open, but maybe this is good for now?


Reply to this email directly or view it on GitHub
#113 (comment)
.

"The blessed will not care what angle they are regarded from,
Having nothing to hide. Dear, I know nothing of
Either, but when I try to imagine a faultless love
Or the life to come, what I hear is the murmur
Of underground streams, what I see is a limestone landscape."

  • WH Auden

jure added a commit that referenced this issue Dec 17, 2014
@jure jure closed this as completed Dec 17, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants