This year has been a year of growth at Engineering Archive. We have seen a return to the annual submission numbers that we saw prior to the transition to the new hosting platform and greater than a 20% increase over last year! Some of the issues we saw last year with excessive spam submissions have been mitigated with the implementation of new software to catch automated submissions. Of course, that doesn’t stop those who make such submissions manually, but this is where our manual screening process comes in.

We continue to appreciate the support of the Engineering Archive Membership Circle. The Membership Circle creates the opportunity for institutions, libraries, and other organizations to support the sustainability of the server through a $500 annual contribution. Many of our supporting libraries are in their 7th year of keeping the server running!

We hope you’ll keep in touch via social media. Find us on the fediverse at our Mastodon account @engrxiv@scicomm.xyz. Note that we are winding down our usage of Twitter and will shortly stop using that platform altogether.

Thank you and HAPPY NEW YEAR!

Since the early days (mid-2016) of Engineering Archive, we have had a presence on Twitter. It was basically the go-to platform for scientific communication and academic discourse. It was actually through Twitter that the initial introductions were made which allowed engrXiv to exist! However, the social media landscape has changed and Twitter today is a shell of what it once was. While good communities may still be found there, the platform itself is a representation of the worst that the online world has to offer.

As a result, Engineering Archive will be sunsetting our presence on Twitter over the coming months. The @engrXiv account at Twitter has been in passive-only mode for the past couple of years, posting only announcements of new preprints through the IFTTT service. However, we have made the decision to cease posting to that platform all-together at the conclusion of our current IFTTT subscription period in May 2025. After that time, the Twitter account for the server will be effectively archived and no long actively announcing new preprints.

Instead, we encourage you to find us on the Fediverse via our Mastodon account, @engrxiv@scicomm.xyz, where we will continue to announce new preprints and other activities relevant to the server. We have decided for now to avoid repeating the mistakes of the past and will not be creating accounts on either Bluesky or Threads. We hope instead that you will join us on the fediverse where you can find our account through Mastodon, Friendica, Lemmy, or any of the other plethora of compatible services. Of course, you can always go old-school and subscribe to our RSS feed! This same RSS feed can be accessed using the Matrix messaging protocol at #engrXiv-new-preprints:matrix.org.

An issue that comes up from time to time with submissions made to the Engineering Archive is what happens if one of the co-authors on a paper finds out later that it was submitted without their knowledge and they don’t approve. There are two ways to approach this issue: 1) professional norms and 2) copyright law.

While it may not be as fun as the underlying engineering work that went into producing a research paper, it’s important for authors to be well-informed about their rights and responsibilities. Having some awareness of copyright law and adhering to best practices, authors can protect their intellectual property and avoid potential disputes with co-authors.

First, it’s generally considered good practice for authors to seek permission from their co-authors before submitting a paper for publication at any venue. Journal publishers typically expect that all authors are aware of and agree to a possible publication of their work (this also influences copyright, discussed further below). As part of the submission process at Engineering Archive, submitting authors are specifically asked if they have obtained permission to post the work from their co-authors. However, this permission is not independently verified by server moderators.

With regards to copyright law*, there are a few considerations. When it comes to a multi-authored work such as a typical research manuscript, each author holds copyright over their specific contributions. This means that if a portion of the work was originally created by a single author, that author has the exclusive right to reproduce, distribute, display, and perform only that specific part of the work. However, it’s not always possible to discern each individual’s contributions to a research paper. If this is the case, then the copyright for the entire work is typically owned by the authors collectively, not individually. Therefore, each author would have the right to reproduce, distribute, display, and perform the entire work, but not just their specific contributions.

As a best practice, authors should consider implementing an authorship agreement in advance of any collaboration. This agreement could address issues such as acceptable future venues for publication (don’t forget to include a preprint server!), authorship order, etc. All authors should agree in advance on these things which may have future implications on the acceptable terms of publication, including the choice of publisher, the license granted to the publisher, and the terms of any agreements regarding royalties or other financial considerations.

Issues related to authorship disputes may be covered in our server’s terms. Most of the time, co-authors should discuss these matters and reach an agreement prior to submitting a work to Engineering Archive. Once the work has been posted to the server, our terms and conditions apply and withdrawal of the work will only be made under conditions of legal obligation.

This is a blog post and not legal advice. It’s always advisable to consult a legal expert or refer to copyright law resources when dealing with copyright matters.