'Living research projects'

Living, "Kaizen", "permanent Beta" work

Should research projects be improved and updated 'in the same place', rather than with 'extension papers'?

Advantages of 'permanent Beta' projects

  1. 1.
    Small changes and fixes: The current system makes it difficult to make minor updates – even obvious corrections – to published papers. This makes these papers less useful and less readable. If you find an error in your own published work, there is also little incentive to note it and ask for a correction, even if this were possible.
    • In contrast, a 'living project' could be corrected and updated in situ. If future and continued evaluations matter, they will have an incentive to do so.
  2. 2.
    Lack of incentives for updates and extensions: If academic researchers see major ways to improve and build on their past work, these can be hard to get publish and get credit for. The academic system rewards novelty and innovation, and top journals are reluctant to publish 'the second paper' on a topic. As this would count as 'a second publication' (for tenure etc.), authors may be accused of double-dipping, and journals and editors may punish them for this.
    • In contrast, a 'living project' can be improved and extended in situ. The author can submit this 'improved project' to (e.g.) the Unjournal for an updated evaluation.
  3. 3.
    Clutter and confusion in the literature: Because of the above, researchers often try to spin an improvement to a previous paper as very new and different. They do sometimes publish a range of papers getting at similar things, and using simila methods, in different papers/journals. This makes it hard for other researchers and readers to understand which paper they should read.
    • In contrast, a 'living project' can keep these in one place. The author can lay out different chapters and sections in the ways that make the full work most useful.
But there may also be downsides to 'all extensions and updates in a single place'. Some discussion follows. (And note that the Unjournal enables this but does not require it.)


SK: why [do] you think it's significantly better than the current replication+extension approach?
DR: I can see the arguments on both sides here. I definitely support replications and sometimes it may make sense for the author to “start a new paper” rather than make this an improvement if the old one. I also think that the project should be time stamped, evaluated and archived at particular stages of its development.
But I lean to thinking that in many to most cases a single project with multiple updates will make the literature clearer and easier to navigate than the current proliferation of “multiple very similar papers by the same author in different journals”. It also seems a better use of researcher time, rather than having to constantly restate and repackage the same things
PS (?): Are these are things like 'living' google docs that keep getting updated? If so I'd consider using workarounds to replicate their benefits on the forum for a test run (e.g., people add a version to paper title or content or post a new version for each major revision). More generally, I'd prefer the next publication norm for papers to be about making new 'versions' of prior publications (e.g, a 'living review' paper on x is published and reviewed each year) than creating live documents (e.g., a dynamic review on x is published on a website and repeatedly reviewed at frequent and uncertain intervals when the authors add to it). I see huge value in living documents. However, I feel that they wouldn't be as efficient/easy to supervise/review as 'paper versions'.
They might also not be ideal for citing as they would be an ever changing resource. I can imagine the whole academic system struggling to understand and adapt to such a radical innovation given how focused it is on static documents. With all of this considered, I'd like 'dynamic/living work' to be incentivised with funding and managed with informal feedback and comments rather than being formally reviewed (at least for now). I'd see living review work as sitting alongside and informing 'reviewed' papers rather than supplanting them. As an example, you might have a website that provides a 'living document' for lay people about how to promote charity effectively and then publish annual papers to summarise the state of the art for an academic/sophisticated audience.
I don’t think living documents need to pose a problem as long as they are discretely versioned and each version is accessible. Some academic fields are/were focused on books more than papers, and these were versioned by edition. Preprinting is also a form of versioning and combining the citations between the published paper and its preprint/s seems to be gaining acceptance (well, google scholar may force this by letting you combine them) - I don’t recall ever seeing a preprint citation indication a specific version (on preprint servers that support this) but its seems possible.
I think the issue with the current citing practice for live documents like webpages is that even if a ‘version’ is indicated (e.g. access date) past versions aren’t often very accessible.
I mainly agree with @gavintaylor, but I appreciate that 'changing everything at the same time' is not always the best strategy.
The main idea is that each version is given a specific time stamp, and that is the object that is reviewed and cited. This is more or less already the case when we cite working papers/drafts/mimeos/preprints.
Gavin, on the latter 'past version accesibility' issue, This could/should be a part of what we ensure with specific rules and tech support, perhaps.
Copy link
On this page
Living, "Kaizen", "permanent Beta" work
Advantages of 'permanent Beta' projects