Live data from Hacker News

Google Scholar PDF Reader

scholar.googleblog.com

121–130 of 165 posts

Re: Google Scholar PDF Reader

#121

Earlier quoted context omitted.

Zotero does a good job at it, doesn't it?

As a daily Zotero user, not really. The nicest thing I can say about it is, it has plugins and is FOSS. Maybe the new 7.0 release will blow me away, but I've been waiting for it to get out of beta forever. More fundamentally, we need to stop disseminating scholarly work as PDFs, a format primarily designed for print. Plain HTML would be an improvement. Even better than HTML would be an extended variant with scholarly…

So I'm a researcher that almost always uses pdfs... Does HTML have the reproducibility that PDF promises? My feeling is that if I store a PDF, it'll look the same in a decade. But is HTML the same way? It seems like it relies on the web browser and many other things... How would one manage things like images and gifs? Is there a way to keep everything into one HTML file that's easily shareable and feels secure?

Re: Google Scholar PDF Reader

#123
post #104
post #53

Does anyone have a research paper reading tool they're happy with? Zotero is what meets most of my needs but I wish I could organize the papers faster and I wish the annotation tools were better. AI-assisted reading is a plus too.

Readwise Reader has a nice pdf reader with highlighting, notes, and an AI reader tool. I organize sources using tags. It's very new and in active development. Academic research is not it's main focus, though, so it probably won't add mindblowing academic tools. (like citation support/ backlinks. although it does have internet backlinks that tell you want articles link to the one you're reading)

Readwise Reader is a poor PDF reader, unfortunately. Where it shines is making readable text documents out of PDFs, so it depends on the type that you’re reading.

Re: Google Scholar PDF Reader

#124
post #53

Does anyone have a research paper reading tool they're happy with? Zotero is what meets most of my needs but I wish I could organize the papers faster and I wish the annotation tools were better. AI-assisted reading is a plus too.

pdf-tools [1] + org-ref [2] in Emacs.

[1] https://github.com/vedang/pdf-tools

[2] https://github.com/jkitchin/org-ref

Re: Google Scholar PDF Reader

#125
post #101

Already counting the days until this inevitably gets killed. I've been burned too many times to rely on Google for anything, except tracking me and pushing ads, which they indeed do better every day.

Scholar is heavily used internally, it’s unlikely to be discontinued even if it has never brought any money to Google.

This is about a PDF reader though, not Google Scholar itself.

Re: Google Scholar PDF Reader

#126
post #101

Already counting the days until this inevitably gets killed. I've been burned too many times to rely on Google for anything, except tracking me and pushing ads, which they indeed do better every day.

[flagged]

Where did you see the announcement they sunset it?

Re: Google Scholar PDF Reader

#128
post #101

Already counting the days until this inevitably gets killed. I've been burned too many times to rely on Google for anything, except tracking me and pushing ads, which they indeed do better every day.

Scholar is heavily used internally, it’s unlikely to be discontinued even if it has never brought any money to Google.

Google Reader and RSS feeds were also heavily used internally :(

Re: Google Scholar PDF Reader

#129
post #127

Earlier quoted context omitted.

Where did you see the announcement they sunset it?

In an effort to accelerate the development life-cycle, Google will now release sunset announcements before the product release.

I saw that announcement, but I thought they changed their mind about a week before it was announced?

Re: Google Scholar PDF Reader

#130

Earlier quoted context omitted.

As a daily Zotero user, not really. The nicest thing I can say about it is, it has plugins and is FOSS. Maybe the new 7.0 release will blow me away, but I've been waiting for it to get out of beta forever. More fundamentally, we need to stop disseminating scholarly work as PDFs, a format primarily designed for print. Plain HTML would be an improvement. Even better than HTML would be an extended variant with scholarly…

So I'm a researcher that almost always uses pdfs... Does HTML have the reproducibility that PDF promises? My feeling is that if I store a PDF, it'll look the same in a decade. But is HTML the same way? It seems like it relies on the web browser and many other things... How would one manage things like images and gifs? Is there a way to keep everything into one HTML file that's easily shareable and feels secure?

The potential to freeze an HTML page in time with minimal changes at render time is already there. [0] Such an ability can even be baked directly into the rendered HTML page so the viewer would be able to download a copy of the page as it is seen at a given time. Other archiving facilities, such as archive.org, take static snapshots of accessible pages if allowed by the publisher of the page and requested by anyone who wants to make that snapshot.

My point is that it is possible to achieve in principle and in practice, albeit that might be practiced as often as one would like to see.

-------

[0] See SingleFile by gildas at https://addons.mozilla.org/en-US/firefox/addon/single-file/: “Save an entire web page—including images and styling—as a single HTML file.”

Post reply on HN