My talk about how we can create real digital libraries. Those which not just archive publications, but provide social interactions around books as well. In short: involve the community to build tools for various social interactions around digital publications and for that to be possible publishers should offer APIs.
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
✓ Live Streaming✓ Interactive Chat✓ Private Shows✓ HD Quality
Anya is LIVE right now
FREE
Free to watch • No registration required • HD streaming
PeerLibrary 0.3 is here featuring improved importing, privacy settings everywhere, feedback on publications processing, lists of all entities to navigate, improved invitations, optimized loading time, and many many more fixes and improvements around.
Proactive federation of commons is better than just federation
For PeerLibrary project we had discussions on how much distributed or centralized should we make it. It is a cloud service and centralizing (unifying) user base and content has clear benefits for both end users and developers. End users have better user experience and ease of use, all content is available quickly and easily, and all other users are there, making social experience better. For developers, code can be much simpler and maintenance of only one instance makes it easier to deploy new versions and push security fixes quickly. It is easier to collect statistics and do A/B testing on a large sample. On the other hand, having multiple instances of PeerLibrary distributed around the world makes whole system more robust, specialized instances could be offered, privacy of users increased. Having PeerLibrary distributed would make forkability easier, encouraging more community control of both the project and the content (commons), preventing corruption of the main instance or core project.
I argue that what if we want a distributed system, what we in fact want is what I call "proactive federation" and not simple federation.
By simple federation I have in mind a project that supports running multiple instances which communicate to each other and sync between themselves. This gives a promise of data not being siloed, a promise of data being open and for everyone to use. But I believe we can do better. It is not so important that data is stored in different locations, but that data is used for different purposes and processed in different systems and simple federation does not addresses this.
With proactive federation I have in mind a platform which proactively pushes its data to other, different, platforms. Other platforms which have different use cases and do different things with data. Proactively means that platform itself takes care of distributing data to other platforms. Important part is that they are different platforms, different codebases, different organizations, different reasons for their existence. This makes data really useful: it finds use in use cases not imagined or possible by original project. It makes sure that data is assured longevity because different projects take care of it. It makes sure that it is combined with other data. If we compare to nature, instead of trying to prevent extinction of a particular gene by cloning, we should mix the gene with genes of other organisms. This improves whole ecosystem.
Technically, it also improves access to data. If data is available only through API for a project A, then any other project has to implement project A API. If project A pushes to project B, then and other project which already uses project B API benefits from that. We get a network effect.
As data crosses borders between projects we might say that data will lose some of its original properties. Maybe. But does translation between languages always just loose or it sometimes also adds? Adds new culture, new context? In the long term I believe this will enrich commons. We should not be afraid of imperfect copies. This is how progress is made.
So instead of using time and resources on how to make federation between instances of PeerLibrary I am more interested in how to proactively push data to other projects. To push metadata about academic publications. To push annotations of academic publications. To push relations between academic publications. Let's share, proactively share. Because you never know how will data available in some other project spark a new idea and use.
PeerLibrary is an open access project developing a collaborative online community where scholars and researchers can read, discover, and discuss various open access literature all within one site. The project is a response to the question as to what comes after open access.
Although open access publications will be opened to the public for gratis access, licensing terms often still restrict the reuse and redistribution of the texts. Scholars and researchers, however, need access to the discussion and discovery surrounding a paper to enhance understanding. PeerLibrary will be a one-stop site where users will not only have access to the original publications but also access to a collaboratively edited layer of knowledge surrounding the publications. Through this integration of multiple sources of knowledge, PeerLibrary will simultaneously enrich the experience of reading research by making it more interactive and open up the possibility for improving publications through peer feedback.
Furthermore, by encouraging more community interaction and involvement, PeerLibrary hopes to stimulate discussion on how we can build better open access resources and tools for the general public, not just scholars and researchers. This will enable us to better understand the breadth of usage for all communities that the open access movement seeks to empower. Ultimately, by analyzing which resources and tools open access enables, we will be able to supply the open access movement with more compelling and unique reasons for the immediate investment in its development, which we believe will improve scientific research and its results. We believe that PeerLibrary will play a vital role in fulfilling the potential of open access to enrich and energize the scientific community, and we will pursue these goals through three specific steps: expediting access to publications, enabling public recordings of analysis and insights on said publications, and encouraging collaboration and openness in the development of science.
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
✓ Live Streaming✓ Interactive Chat✓ Private Shows✓ HD Quality
Anya is LIVE right now
FREE
Free to watch • No registration required • HD streaming
Hacktivations bring together developers, designers and storytellers to come together and hack for good on software projects that are creating social good through their work. PeerLibrary will be one among 8 projects to hack on this time. Come!
PeerLibrary blog is coming to the Internet corner next to you. PeerLibrary is your future one-stop for all your interaction with open access scholarly literature. Still work in progress. Stay tuned. Subscribe to our mailing list or follow us on Twitter. Check its source code.
PeerLibrary, a project I am currently working on, won the award for Highest Impact at Meteor Hackathon 2013. This is how they describe the project:
Peer Library is like Rap Genius for academia that adds crowdsourced notetaking to academic papers. Users import academic papers in PDF format, view papers in-browser from the library, and make inline comments on selected text in each paper. Users can share those comments and view other people's notes in real time. They also implemented searching for papers by title or journal. Team: Mitar, Gheric Speiginer, Tony Chen.