🌟 RDM Club Meetings 1 and 2 - recap We are pleased to announce that we have a new regular community event specifically for Research Data Managers and other data professionals who support users of eLabFTW! The eLabFTW RDM club was created to enable RDMs from all over the world to share strategies for supporting users of eLabFTW at their institutions. This club will start off with monthly informal meetings, and may eventually include working groups and real life meet-ups (!

🌟 OpenCloning introduction In this session, the author of OpenCloning, a cloning tool for molecular biologists, presents the integration within eLabFTW and basic functions of the software. Then Nico presents the latest changes in the new version and discusses upcoming features. There is a Q&A session afterwards. Watch recording

Introduction eLabFTW 5.2 has been released! This new version brings many new features, enhancements and a few bugfixes. This blog post highlights some of these changes, but the complete list of changes is available on the release page. A note about “stable” releases eLabFTW is a living project — “stable” would imply it’s no longer evolving. Version 5.2.0 is production-ready, but minor bugs will surface once it’s in wide use, and patches will follow.

🌟 Sixth eLabFTW Community Meeting In this session, we learned about strategies for teaching with eLabFTW and implementing the software at research institutions. Nikki Parks (RWTH Aachen University) - “Establishing eLabFTW as a Central University Service” Isabell Schmitz (Goethe University Frankfurt) - “Transforming Lab Education: Teaching with eLabFTW” Watch recording

🌟 Fifth eLabFTW Community Meeting In this session, we learned about the integration of eLabFTW with other tools. Dr. Alexander Schlemmer (IndiScale): “Data Integration from RO-Crate and the ELN-File format using the LinkAhead Crawler” Open session where users can ask questions, discuss upcoming features, and talk about their experiences with eLabFTW. Watch recording

🌟 Illuminating Efficiency: Reflections on the Fourth eLabFTW Community Meeting In the continuous journey of our collective exploration, the Fourth eLabFTW Community Meeting convened on November 19, 2024. This gathering became a beacon, shedding light on innovative pathways to enhance laboratory efficiency through eLabFTW. 🎤 Voices of Innovation Two distinguished speakers graced our virtual podium, each sharing insights into optimizing laboratory workflows: Dr. Michael Krieger (The Friedrich-Alexander-University of Erlangen-Nuremberg): Explored the integration of eLabFTW into their physics lab course, introducing the pyelabdata package—a tool designed to streamline data management and analysis.

🌐 Harmonizing Connections: Reflections on the Third eLabFTW Community Meeting In the unfolding narrative of our collective journey, the Third eLabFTW Community Meeting convened on September 17, 2024. This gathering became a symphony of ideas, each note resonating with the theme of integration and collaborative innovation. 🎶 Voices of Integration Three maestros shared their compositions, illuminating pathways to harmonize eLabFTW with diverse instruments: Alexander Haller (University of Heidelberg): Introduced elAPI, an API client designed to seamlessly bridge eLabFTW with other services, enhancing the fluidity of data interactions (https://github.

Introduction eLabFTW 5.1 has been released! This new version brings many new features, enhancements and a few bugfixes. This blog post highlights some of these changes, but the complete list of changes is available on the release page. Important change A breaking change has been introduced in APIv2: /team_tags has moved to teams/{id}/tags. If you have scripts using /team_tags, replace it with teams/current/tags to maintain the same behaviour. Video A video has been produced, summarizing some of the features:

Have you heard about security.txt? It’s a proposed standard where websites can point to their security policy, list security contacts, publish their GPG key, and other important information useful for anyone (but mostly security researchers), in a text file placed at a known location (or should I say a “well-known” location 🤪). The website: https://securitytxt.org/ The RFC: RFC9116 You can see ours here: https://www.deltablot.com/.well-known/security.txt It is similar to robots.txt, humans.

Why we sometimes drop features? It is quite rare, but sometimes things available in one version of eLabFTW are no longer available in the next version. There could be several reasons for this: the feature is no longer open source: this is what happened with the image editing tools of the text editor the feature depends on a library or service that is no longer active/maintained the feature has been superseded by a superior implementation What I wish to discuss in this post is the last point: redundancy and its associated maintenance cost.