Research Data Management
This is the third and final installment of some reflections on using electronic notebooks (ELNs) as a tool for data curation. The first post looked at ELNs as a low cost alternative to the new Springer Nature research data support service. The second post examined in detail capabilities needed by both ELNs and data repositories to optimize the use of ELNs as data curation tools. In this post I’ll take a practical look at how data librarians can use ELNs to facilitate better curation of datasets bound for repositories.
The second post identified and explained four capabilities needed by ELNs to optimize data structuring and hence provide a good platform for curation:
Working with an ELN with these capabilities will save time and enable data librarians and the researchers they are working with to take full advantage of structure that has been built into the research record during the active research phase.
This of course is goo practice for all sorts of reasons. It’s relevant to optimizing use of ELNs in the following ways. First, it will give you an opportunity to introduce a researcher to the benefits of using an ELN and the particular ELN they will be using, if they are not already familiar with these. Conversely, if the researcher is using an ELN you are not familiar with this will provide an opportunity for the researcher to introduce it to you. Either way, this will also open up an opportunity to discuss the research plan and to think in general ways about how the record of the research can be best structured to facilitate efficient deposit of relevant datasets into a repository.
The data management plan can, at least, be stored in the ELN, and, ideally, will be created in the ELN so that links can be made between the plan and relevant parts of the research record (this is an example of why the ability to link between internal documents and resources is useful). If the ELN supports automatic conversion of Word and Open Office documents into documents in the ELN’s format, a good option is to import the Data Management Plan into the ELN with the converted in the ELN’s format, to facilitate more fine-grained linking between the DMP and relevant parts of the research record. The DMP can conveniently be included as part of the datasets that are desposited in the repository at the end of the research project.
Having an account for the ELN that allows you to view, and, possibly, comment on data produced by the researcher will save both you and them time and make your communication more efficient. You can communicate using the ELN’s messaging system or, if supported by integrations with the ELN, you can communicate about preparation of datasets using chat tools like Slack, Microsoft Teams and Google Hangouts Chat. You will need to discuss and agree with the researcher an arrangement that gives you convenient access yet does not raise fears that their research will be altered, and also provides for convenient communication channels using whatever tools you and they like to use and are supported by your institution.
Whether or not you’re able to engage with the researcher early on in the project, when the time comes to collect and organize datasets for deposit in the repository, you’ll be in a much better position with the data having been collected and organized in the ELN during the active research phase. Assuming the ELN has the external and internal linking capabilities noted above, all relevant data will be accessible from within the ELN, i.e. already collected and structured in a single resource, and selecting which datasets to include for deposit into the repository becomes a much more straightforward process.
The ability to see the pre-existing structure created during the active research phase likely will enable you to more quickly understand what the research is about and hence to be able to comment on what should do into the deposits and how it should be organized. The ELN will also provide convenient tools — e.g. moving documents from one folder to another — for re-organizing datasets if after discussion you and the researcher think that would be useful.
RSpace is an open-source platform that orchestrates research workflows into FAIR data management ecosystems: request a demo or contact us to learn more.
March 24, 2026
RAiD in RSpace: Reporting Research Activities AutomaticallyIntegrations
RSpace version 1.120 introduces native RAiD support, allowing researchers to automatically report research activities to their project's RAiD record. Here's what that means in practice, and why we'd love your feedback.
Read moreMarch 17, 2026
RSpace is more than an ELN — and now our website says so!News
RSpace has grown well beyond its ELN roots — it now integrates sample management, research workflow orchestration, and FAIR-enabling infrastructure like persistent identifiers and metadata standards into one cohesive platform. In early March we relaunched researchspace.com with a new look and structure that reflects this evolution across three tightly integrated facets: Research Orchestrator, ELN, and Sample Management.
Read moreJanuary 19, 2026
From ELN to FAIR Research Infrastructure: Our Vision for RSpaceResearch Data Management
We kicked off 2026 by presenting RSpace's vision for FAIR data workflows to the Competence Network for Open Science in Poland. The talk explored how vertical interoperability enables seamless data and metadata flow across the research lifecycle. You can find the presentation "RSpace - From Electronic Laboratory Notebook to FAIR Research Data Orchestration” here (https://doi.org/10.5281/zenodo.18253482).
Read moreJanuary 9, 2026
2025: A year to remember for RSpace!News
2025 in review - A reflection on community-driven development of RSpace and an outlook to 2026.
Read more