Editing User:Ckeene/Ideas for future versions of eprints (section)

== Long term : fit in with academic workflow ==
Academics make funding bids, do research, etc, then write a draft article, then submit to journal(s), get published. (actually I don't really have a clue what academics do, but hopefully this is a good guess!)

* ''All of these are examples of creating documents and revising documents and sharing documents. This isn't too far from what a repository is. We have thought about helping integrate with the desktop by supporting WebDAV.'' [LES CARR]

At the moment we 'bolt on' to the end of this, but what if we could play a bigger role. 

This may be controversial as in a sense it moves eprints away from being just a repository, and perhaps maybe instead of any extra functionality being put in to eprints, we look at what popular 'research process management' solutions are out there and see how we can work with them (integrate, api's etc). If we had a tool that helps people manage their biids and funding awards, lets them refer to old ones, and see the documents they produced as a result (which - just so happened to make those documents available to the world) then this may well appeal to many academics. Of course at this point eprints stops being what it is and becomes something else, so any moves to accommodate such things would need to be carefully thought out).