-
Notifications
You must be signed in to change notification settings - Fork 0
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
Research Library Services #14
Comments
When in conversations with people, I often get into these "ahh there's this article / paper" which I remember a partial title or the name of the author... except there's no Internet and I cannot recall the exact article. I think it'd be cool if there's a searchable offline library on site where I can say "why don't we walk over to the library and print this paper!" I think people will find this a useful resource. I also wonder if the larger discussion of "local access to digitally archived content" can have some discussion space. Like where you mentioned:
There may be some shared discussions with @mitra42's idea on #3 In terms of logistics, we are planning an indoor space that should have wired connections to the local mesh. Imagine a table with a couple seats in a large hall with wire drops where you can connect a NAS or a Raspberry Pi tied to an external HDD, where you can also put a laser printer, perhaps put up a schedule of some discussion activities...
I think this is very helpful and as long as the resource is pull-based (searched) rather than pushed onto people, it's not an intrusion at all! |
Right ... we'll have at least one mini-server (RPI or Rachel or could be something bigger) on site that can Crawl / Proxy / Serve content from the Archive. |
Is this and #3 the same project, or different? My original understanding is they are similar, but @bnewbold's is more specific to https://fatcat.wiki and papers, whereas #3 is another front-end and perhaps with multimedia content (e.g. 2018 recordings of DWeb Summit)? |
These are different projects, #3 is a generic IA server, the UI is a subset of the Archive UI, the content is standard UI collections, while if I understand @bnewbold 's its specialized/optimized to research papers. In particular #3 is actually intended to be part of a decentralized internet archive, to complement the other servers (Wikipedia, Khan Academy, Open Street Maps etc) typically installed in especially disconnected or marginally connected community networks. |
This project is published onto https://dwebcamp.org/proposals/ thanks for submitting @bnewbold :) |
@bnewbold can we try this out at https://www.eventbrite.com/e/all-day-hackathon-for-dweb-camp-tickets-63718679285 |
Cross-referencing to hackmd.io: |
I think it would be helpful to provide local access to the "scholarly record": research papers, perhaps books, notable blog posts, etc. This would enable participants to check citations and dig in to knowledge a layer deeper than an encyclopedia. It also provides a convenient content set / corpus for people experimenting with distributed storage and communication systems on-site.
The most basic service to provide is a simple lookup when somebody already knows an identifier (DOI) or title/author, and return a PDF, though an HTTP web interface. More advanced services, which would be progressively harder to provide, are a dedicated lookup station (large monitor, seat, etc; would work if local network is down); print-out services (double-sided; color?); access over multiple protocols; accepting deposits and metadata edits (wiki-style); fulltext search and other rich "discovery" services (eg, "show me the best paper/book about carrot night vision"); additional media types (eg, XML, HTML); expanded coverage of books and web content.
I'm interested in trying to run such a service; it overlaps with the papers archiving work I do at the archive (https://fatcat.wiki). My basic plan would be to run:
Happy to collaborate if others want to bite off some of the more ambitious options! Other brainstorm-y ideas:
Some more thoughts:
The text was updated successfully, but these errors were encountered: