Comments (5)
I see. I guess I'm more of a "bulk" guy. :) I also use the -read
option, generate an HTML page, open it in a browser and mark all the emails as read (now I'm realizing that I should use -mark
for that). After that, I go through this HTML page and open all the links I'm interested in. I usually get 45-50 alert emails every couple days which results in 60-70 unique papers, out of which I usually open a dozen or two and save 30-50% of them as PDFs to Mendeley (or just locally) for further reading or send them to my students. So I guess I mostly use this tool as a preliminary filter.
from scholar-alert-digest.
To make it clear - this is just to share a preliminary idea, will be very happy to get other feedback/requests on what kind of interactions would be more useful.
Will not start working on it yet, until there is some feedback on it's urgency.
At any rate, some mocks should be shared first here, before spending time on any implementation.
from scholar-alert-digest.
Do you have a use case in mind when "mark as read" at this granularity could be useful? I find it quite tiresome to click all these checkboxes. :) I usually scan the list top to bottom and open some of the links. If I get interrupted, it's usually no problem to find the spot to continue afterward.
from scholar-alert-digest.
Do you have a use case in mind when "mark as read" at this granularity could be useful? I find it quite tiresome to click all these checkboxes. :)
Really good question :) This idea was born out of the frustration of going back to gmail to mark things as "read". I guess one can call my use case, or reading pattern, not a "bulk" but the opposite, a "cherry-pick" one. Basically I rarely go though all the papers in a report on single sitting. Many papers hang around until I find them interesting enough to take a look, but when that is done - I want to exclude them from all further reports, so they only contain the rest of unread (or "delayed") papers.
I usually scan the list top to bottom and open some of the links. If I get interrupted, it's usually no problem to find the spot to continue afterward.
Thanks for sharing your use case - so how do you mark emails as read? I know @m09 is using -read
so that addresses it by, so to say, "bulk export" of all unread papers from email to the report and then -archive
as well, to be able to get back to those later. And how do you do that?
from scholar-alert-digest.
@jzuken thanks for, as always, a very useful input!
If I think more about the "bulk" use case in the context of having this tool running on a server:
- I guess, we should have such "bulk" +
-read
as a default behaviour - we should save all the reports/HTML per user, so one could get back to each of them later
- (each user) should have a page with a list of such reports
Then "mark as read" action could become "mark as relevant/important", and even implicit, remembering those links that the user "open a dozen or two". This might help us with the filtering, e.g as we already know such papers are "relevant", we do not need to include them in the next reports.
WDYT?
from scholar-alert-digest.
Related Issues (20)
- web server improvements HOT 1
- switch to a better way of accessing gmail API
- feature request: visible authors HOT 4
- Experiment: add auto-generated TLDRs
- Doc: add Input/Output examples in README
- HTMLRenderer crashes when special characters appear in digests HOT 2
- Missing header data in json response from server HOT 1
- URL Regex doesn't match .co.uk scholar urls
- Backend: "cluster URL" support
- Interaction model HOT 1
- Paper cache + reload button
- installation issues HOT 3
- Idea: Launch script HOT 1
- Marking more than 1000 email as read fails HOT 1
- Error on extracting papers from email \w 'Showing less relevant results' HOT 1
- Refactor gmail API lib usage
- Add -v CLI flag that prints all paper parsing errors
- Handle "clusters" on paper extraction
- Update/fix usage instructions HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from scholar-alert-digest.