Landing page: Citation details outdated/broken #522
Comments
|
Continuing the discussion from #524, It seems like google scholar technically do not allow scraping and since the github action servers might be using IP ranges which could be blacklisted by google. One option would be use to add Eg: |
|
I am not sure which solution would be the easiest to implement, but both sound sustainable to me if they do the job. Does the Semantic Scholar API report the same numbers as Google Scholar, or will we confuse people if we link to the one and get numbers from the other? Alternative: Do you think we could (mis)use this GitHub Action to get what we need? https://github.com/marketplace/actions/google-scholar-fetcher |
|
I tried with the Semantic API and the citation count is different from what we have from google scholar.
|
|
I would expect all buttons to be next to each other, potentially with shorter text or some grouping. |
|
Reverted back to google scholar due to citation mismatch with semantic API, fetching these results using |
|
"preCICE" is clear from context. Maybe simply "v2 citations (134)"? Or:
|
|
Do you feel the whitespace below needs to be reduced ? |
|
I think the whitespace is ok, but I would really put the buttons next to each other. |
|
Something like this ? |
|
Yes, perfect! Maybe:
|
|
I tried playing around with the github action mentioned earlier. Apparently they use user ID as a filter not the paper ID. |
|
Since that Action is rather new, it might make sense contacting the developer (via an issue) to investigate whether adding an option for a paper id would make sense. If the addition seems to be clear, you could also directly implement it and open a pull request. But I would do this only if there is some indication that this approach will actually not face the same access issues. |
|
What about moving this logic to the user end via javascript ? |
|
If that works, of course! |
In the landing page:
Maybe it's time to replace the counter with the v2 paper, or add both somehow. We should also fix the link issue.
The text was updated successfully, but these errors were encountered: