-
Notifications
You must be signed in to change notification settings - Fork 10
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
Address handling of paywall'ed articles #12
Comments
Me wearing my licensing hat now -- I prefer not uploading/hosting files that we have murky rights to distribute. Another option is to dis-aggregate pdfs from the repo and have 'em elsewhere (e.g. a dropbox folder or gdoc), that way they aren't public and we can avoid slow size creep for this repo |
One practice that has served me well is linking to things that are already online, but not actively hosting them ourselves (even Google does that). We could also notate which articles are behind a paywall. |
@jschell42 I think you're right, that linking is the way to go for the public view of the research docs. Unfortunately, I probably won't be able to take the time to add annotations about what's paywalled or not. Spending time figuring out what is paywalled can take more time than I can afford to give it. (Not saying this to be pompous, just making an assessment of available time.) @dcwalk Putting the PDFs elsewhere is a good idea. For right now, I could move those PDFs out of the repo into a new location, and then later we can think about how to make the process efficient in the future. Is there a Dropbox location already for such things, or should I put them in a personal Dropbox folder? (And if the latter, who should be given access?) |
In recent additions to this research, I added PDFs of articles that may in some cases be under paywall even if I managed to find them on the internet. We need to decide on a policy about including such PDFs. Some initial options that come to mind:
The text was updated successfully, but these errors were encountered: