thanks a lot for all the enthusiasm, that's what makes it worth it to share and document what I do!
To clarify a few things:
there is absolutely no link between junior researchr and researchr. Junior researchr doesn't "exist", it's an illusion created by clever editing, the things we show aren't possible today (most of them).
Researchr exists (I use it every day). However there is no such thing as a researchr web service, you don't need any accounts, it's just a name for a bunch of different programs on your computer and scripts to tie it together.
And that's the tricky part, as I mention on the wiki page:
Some of you might read this far, and say - this looks really neat, I'd like to install it on my computer and start using it for my research. Unfortunately, given that this isn't one single program, but rather a combination of a bunch of programs, and scripts that integrate with those programs, it's impossible for me to create one simple installer which will let you jump right in and use this setup.
So why I am spending all this time documenting this? In my mind, there are two kinds of “target groups”. The first are tinkerers, who are comfortable with Ruby, the terminal, etc. All of my scripts are available, and I've made some effort to document them, as well as (perhaps more valuably) documenting some of the “neat ways of doing things” that took me a long time to find. I hope this will be useful to you.
Perhaps you want to try to replicate the entire setup - it would be quite a bit of work, but it's certainly possible. Perhaps you just want a certain component (say side-by-side editing in DokuWiki, or automatic import of Kindle annotations)? This should also be quite doable (and if people contact me and tell me that a certain component would be very useful, I might try to separate that out, document it, and make it easier for people to access just that functionality).
But to people who are not able to or willing to spend lot's of time looking over scripts and commands, I hope that this could still be interesting as a demo of what is possible. During a university class, I was part of a group that designed a “mockup” of an academic workflow that we called “junior researchr” (this is where I took the name from). What we showed in that video was not a functional workflow, but something we “simulated”. In this case, the system I am showing you is something that I am using every day for hours, and exactly how it works has been shaped intimately by how I think.
I think we all deserve much more powerful tools for thinking and managing knowledge, and this is my “stab” at it. I am also fascinated by the relationship between how we grapple with ideas individually, and how we can do so in groups (I wrote about this here), and the one thing my system is missing is a social network. I don't want to open my wiki up to editing, but I'd love lot's of others to write about articles on blogs and wikis, and to be able to very easily discover those posts, and share our ideas.
However, given that we are meeting in HK, I could certainly give it a stab to install this on your computer (I am assuming you are using a Mac). That would be the first time, and would be a great exercise for me to see how difficult it is to transfer it to somebody else's environment.
The three programs involved are BibDesk, Skim and DokuWiki (and some of my scripts are tied into Chrome as a webbrowser for DokuWiki). I don't use Papers at all. (It looks very slick, but it's far from as scriptable and powerful as BibDesk).
As for MyAccess, that's really easy: http://reganmian.net/blog/2006/03/31/bookmarklet-for-myaccess-uoft-libraries/ --- I wrote this in 2006, and have used it so much. I really wanted to share it with other UofT students, but never found a good way. I wrote to the library, but I don't think they even bothered to get back to me :( (This doesn't work for all services, but it works for many)
As for tagging, what I would do is use the clipping function to take text from an article page (or anywhere) and insert into a topical page (for example "Knowledge Building"). When it inserts the text, it also adds a link to where the text came from.
You can also link to pages, and on those pages you can automatically display a list of all pages that link to this page, so the KB article could show a list of all articles that link to the KB page. That's a form of "tagging" in a way.