From the 25th to 27th of September 2024, the Leibnitz Centre for Archaeology (LEIZA) & Mainz University of Applied Sciences are hosting the second NFDI4Objects Community meeting. There will be a diverse program with workshops focused on students and young researchers as well as teachers and other interested parties on the topic of research data management of object-related data. Furthermore, the NFDI4Objects will present their annual report, host poster sessions, and ignite talks, and organise collaboration and community workshops. In one of the poster sessions, we (DKZ.2R) will be presenting our poster titled: “The Rhine-Ruhr Center for Scientific Data Literacy (DKZ.2R) bridging the gaps to NDFI4Objects” The full program (in German) can be found on the NFDI4Objects Website. As the DKZ.2R is only funded for a duration of three years, the various NDFI consortia play a major part in finding ways to establishing our offers and making them last. As part of our networking strategy we are also constantly exchanging ideas and looking for synergies between project to use our ressources as efficiently as possible.

Related Posts

Comments on Collaboration - My Experience with the DKZ.2R Rent-an-Expert Program

Comments on Collaboration - My Experience with the DKZ.2R Rent-an-Expert Program

Comments on Collaboration - My Experience with the DKZ.2R Rent-an-Expert Program

At the beginning of this year (2025), I received an email regarding the DKZ.2R “Rent an expert” program. I was very interested in this initiative and therefore applied for support from the scientific consulting team at the Rhine-Ruhr Center for Scientific Data Literacy (DKZ.2R) for assistance with my data analysis.

I obtained my master’s degree in Plant Nutrition from the China Agricultural University and pursued my PhD study at the University of Hohenheim. I am currently a postdoctoral researcher in the Institute of Crop Science and Resource Conservation, Crop Functional Genomics, at the University of Bonn.
My research expertise includes plant culturing, molecule cloning, biochemical analysis and limited data analysis experience on large-scale NGS datasets.
Since the beginning of April 2025, two DKZ.2R consultants were assigned to me: Tarek Iraki, who is proficient in programming languages such as Python, and Lennard Maßmann, who specializes in working with R. Together, we collaboratively worked on my Postdoctoral project, which focuses on the molecular and genomic dissection of lateral root development in maize.

Read More
How To: Good Scientific Practice

How To: Good Scientific Practice

“Scientific integrity forms the basis for trustworthy research”, so it says in the Guidelines for Safeguarding Good Research Practice of the DFG, the German Research Foundation. As a major funder of research in Germany the DFG, as well as many other funders of research in Germany and the European Union, requires researchers to follow a certain set of rules conducting their research. These rules are called “good scientific practice” and have to be followed by researchers to be viable for funding. According to the guidelines researchers are required to “document all information relevant to the production of a research result as clearly as is required by and is appropriate for the relevant subject area to allow the result to be reviewed and assessed”. But good scientific practice is not done by documenting your research. It also includes i.a. protecting the personality rights of your subjects and handling research data in an appropriate manner by e.g. “back(-ing) up research data and results made publicly available, as well as the central materials on which they are based and the research software used, by adequate means according to the standards of the relevant subject area, and retain them for an appropriate period of time.” This is where Research Data Management (RDM) comes in. Of course RDM is much more than just creating a backup of your data on a USB-Stick and handing it over to anyone asking for it. “Good scientific practice” in RDM follows the FAIR principles:

Read More
Documentation From User Experience

Documentation From User Experience

This post is a condensed version of a talk at our Data Compentcy College

If you regularly use scientific software written by others, or tried to replicate interesting research that relies on software, you have probably also invested weeks of work to solve a software problem or even given up on a software because of missing documentation. Finding a project that might be the solution to your problem and then failing to run the code is frustrating. Being unable to run a project you have built yourself years ago is even worse. Having experienced all those setbacks myself in the past I want to use this post to channel that frustration to fuel solutions for better documentation for our current and future projects.

Read More