Unfold Research
Online community for academics to learn and share.
I woke up thinking the following: it would be cool if people could contribute to the UR community without even visiting the website. It would be cool if their workflow was disrupted to the bare minimum, just some kind of "addition" to already existing things that would allow them to contribute so quickly and easily, with minimal hassle.
And there is a way to achieve those things, and they fit into the picture beautifully.
I came up with two ideas:
- browser extension
Lets you contribute with 2-3 clicks, anytime you find something useful that you think might be useful for others. You open up a website, see that it could be useful to some publication, you find publication from the dropdown, add note, et voila!
https://i.ibb.co/JjQ5Jmg/neurom.png
- embedded components
Imagine Stackoverflow having ability to embed upvote/downvode buttons of a specific answer anywhere. It means that you don't have to visit the SO website in order to give your vote. It would probably happen that answer's original poster put those buttons on his website detailing the answer, and whilst getting traffic to his own website, visitors have the ability to contribute to his presence on SO via those embeds.
For academia, this makes perfect sense, since resources are never in one place, so being able to contribute to some central database no matter what external resource you've visited is a great opportunity.
Well, that's it for now. Hopefully, these two ideas don't get stolen, as they are pure gold in regards to academia and huge part of future of Unfold Research.
Decided to create a few mock pages based on sudden "epiphany". I was motivated by recent tweets that I've been finding, in regards to Open Science and easier digest of scientific content, as well as verifying that research is reproducible. After spending ~2 years on https://www.indiehackers.com/product/nodebook, I was very familiar with the needs of academia, but I suddenly saw it all in a new light and what were the main mistakes that I've been making with Nodebook. This time, I am sure I got it right, no doubt.
Comment