Source: Own Illustration
When transitioning from one phase of the research process to the next, researchers often encounter media gaps. For example, when they have finalized their data management plan (DMP) in RDMO and want to create a corresponding Coscine project for data storage and management. Until now, the project metadata had to be transferred manually for this purpose. Through an incubator with DMP4NFDI, RDMO has now learned to communicate with Coscine and transfer the metadata directly. This blog post explains exactly how this works and what requirements must be met.
Interface Between Coscine and RDMO Enables Import Instead of Duplicate Data Entry
Importing a DMP from RDMO is the first feature available exclusively in the new Coscine user interface. By using a JSON file, you can transfer project metadata from one system to another, thereby reducing the effort involved in duplicate data entry and minimizing associated sources of error. In addition, information about the RDMO project is automatically stored in Coscine, paving the way for potential future developments to further integrate the two tools. A step-by-step guide and further details on this feature can be found in the Coscine documentation.
The following video also shows you how to use the incubator in Coscine.
[Das Video wird nach dem Klick von Youtube geladen und abgespielt, dazu baut der Browser eine direkte Verbindung zu den YouTube-Servern auf. Es gilt die Datenschutzerklärung von Google.]
Prerequisites for Importing from RDMO: Collaboration with Research Support Staff Recommended
In order for Coscine to read and process the JSON file exported from RDMO, RDMO plugins must first be installed. Additionally, the correct attributes must be present in the RDMO catalog so that the project metadata is automatically entered into the correct fields in Coscine during import. To implement this mapping between the two tools, we recommend collaborating with, for example, data stewards and the administrators of your RDMO instance. For more information on the requirements for the RDMO import, see the Coscine documentation.
Agile Development: Why the Feature Looks Different Than Planned
The feature was developed as part of an incubator in collaboration with the NFDI core service DMP4NFDI. At the start of the incubator, a blog post was published outlining the plan at that time. The Coscine team works in an agile manner – so changes to the plan are part of everyday work. The decision to opt for JSON import instead of token-based import was primarily driven by the goal of making the feature as stable and widely usable as possible. For example, the import could be extended to other DMP tools in the future. The mapping of RDMO attributes to Coscine fields can also be easily adjusted as needed. As a result of the work in the incubator, the focus is currently on NFDI catalogs.
Learn More
Do you have questions or comments about the incubator? The Coscine team welcomes your feedback via email.
Would you like to stay informed about the latest news from Coscine? Then visit the Coscine website and subscribe to the Coscine newsletter to stay up to date once a month.
Responsible for the content of this article are Michèle Robrecht and Arlinda Ujkani.
Leave a Reply
You must be logged in to post a comment.