![\"Coscine](\"https:\/\/blog.rwth-aachen.de\/forschungsdaten\/files\/2023\/02\/Coscine-FAIRly-in-love-1.png\")
<\/a>Source: Own illustration<\/p><\/div><\/p>\n
If you haven’t fallen in love with Coscine<\/a> yet, you will have fallen under the spell of the research data management platform by February 14, 2023 at the latest – fittingly on the day of love. In this follow-up-report we have summarized the event for you and why Coscine makes your heart race. The event Coscine – FAIRly in Love with Research Data event <\/em>took place as part of the Love Data Week.<\/p>\n <\/p>\n All those who do not yet know what Coscine is and who is behind it, pay attention:<\/p>\n Coscine is an open source platform that enables researchers to run their research data management (RDM) at the highest level and according to good scientific practice. The platform was developed at the IT Center of RWTH Aachen University and is currently offered across universities.<\/p>\n But why fall in love with a RDM platform? Have we convinced you? \ud83d\ude09<\/p>\n Coscine manages to be in a very special harmony with the FAIR principles. So what makes Coscine FAIR?<\/p>\n With the help of the login<\/strong> via SSO and ORCID, institutional boundaries for access to the respective project are removed. The individual accounts allow authentication of the owner or all contributors to the dataset as well as user-specific rights such as Owner, Member or Guest. This makes research data accessible<\/strong> and reusable<\/strong>.<\/p>\n Metadata<\/strong> is captured at the project, resource, and file levels and automatically linked to the research data. Optionally, the metadata can be made publicly accessible within Coscine. They are also searchable via ElasticSearch. Technical mapping and validation is done using the W3C standards RDF and SHACL. Additionally, a connection to the NFDI4Ing metadata hub via “FAIR Digital Object” interfaces is planned. All these aspects contribute to making research data findable<\/strong>, interoperable<\/strong> and reusable<\/strong>.<\/p>\n The application profile generator<\/strong> from the AIMS<\/strong><\/a> (Applying Interoperable Metadata Standards) project allows profiles to be created with individual and discipline-specific metadata, eliminating the need for technical knowledge of RDF and SHACL. This makes research data findable<\/strong> and interoperable<\/strong>.<\/p>\n Through various resource types<\/strong>, the storage of research data is made possible. Among others, there is access to the RDS via web browser or S3 client. There, a retention and archiving period of ten years from the end of the project is guaranteed. With the help of Linked Data, externally stored research data and, thanks to GitLab resources, project-related repositories can be linked. The result is that the research data can be reused<\/strong> as much as possible.<\/p>\n By means of handle-based ePIC Persistent Identifiers (PID)<\/strong>, the storage locations of the research data become unique and permanently identifiable as well as referenceable on a global level. Furthermore, fragment identifiers for individual files are enabled by extended handle URLs. This makes the research data findable<\/strong> and accessible<\/strong>.<\/p>\n For RDS resources<\/strong>, depending on the resource type, interaction is possible via browser, S3 protocol or REST API. The REST interface makes data and metadata independently findable and accessible. The ease of entering data and metadata into the system facilitates subsequent use. In addition, the interface enables workflows to be automated. Thus, research data is made findable<\/strong> and accessible<\/strong><\/span>.<\/p>\n Source: Own illustration<\/p><\/div>\n Long-term archiving is beyond the scope of Coscine. Researchers must therefore transfer their data and metadata to an appropriate archive or repository for availability beyond ten years after the end of the project.<\/p>\n In addition, the richness of the description in the research metadata (e.g., the choice of application profile, workflows) as well as the specification of a license is in the hands of the researchers.<\/p>\n Since Coscine allows a high degree of flexibility in the creation of application profiles, researchers must ensure that they reference appropriate domain-specific controlled vocabularies and ontologies when creating individual application profiles, and thus use (meta-)data corresponding to domain-relevant community standards.<\/p>\n The protocol is open, free, and universally implementable.<\/p>\n For metadata, work is underway to implement a FAIR Data Point as a standardized interface.<\/p>\n Metadata should be accessible even if the data is no longer available. Therefore, a permanent placeholder with metadata of deleted resources will be implemented in the future.<\/p>\n For (meta)data to contain qualified references to other (meta)data, these can only be added manually so far. Therefore, a project has been requested to add a predefined option to link (meta)data records.<\/p>\n In addition, a technical versioning of (meta)data is currently being implemented.<\/p>\n The lively participation in the workshop with around 40 participants from all over Germany enabled an interesting discussion and many insights into the functions of Coscine. Interested parties were guided live through the platform during the workshop and were able to ask their questions at the end. We have listed the most interesting questions including the answers for you once again.<\/p>\n 1st question: Answer: 2nd Question<\/strong>: Answer<\/strong>: 3rd question<\/strong>: Answer<\/strong>: 4th question<\/strong>: Answer<\/strong>: 5th Question<\/strong>: Answer<\/strong>: 6th Question<\/strong>: Answer<\/strong>: 7th question<\/strong>: Answer<\/strong>: We would like to thank all participants for their interest in Coscine and the resulting successful exchange with each other. See you next time!<\/p>\n You don’t want to miss any more news about Coscine? Then subscribe to our mailing list<\/a> and visit us on our website<\/a>.<\/p>\n Do you have any questions or feedback? Then send a message to the IT-ServiceDesk<\/a>. We are looking forward to your message!<\/p>\n ______<\/p>\n Responsible for the content of this article are Ilona Lang<\/a> and Arlinda Ujkani<\/a>.<\/p>","protected":false},"excerpt":{"rendered":" This entry is only available in Deutsch. Wer sich bisher noch nicht in Coscine verliebt hat, wurde sp\u00e4testens am 14. Februar 2023 \u2013 passend zum Tag der Liebe \u2013 in […]<\/p>\n","protected":false},"author":3308,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"c2c_always_allow_admin_comments":false,"footnotes":""},"categories":[1,3,108,109,107,102],"tags":[157,288,148,65,133,26,529,40,138,487,29],"class_list":["post-4861","post","type-post","status-publish","format-standard","hentry","category-allgemein","category-rwth","category-berichte","category-fdm-team-unterwegs","category-informationen-beratung","category-services","tag-aims","tag-austausch","tag-coscine","tag-fair","tag-fair-prinzipien","tag-gitlab","tag-love-data-week","tag-metadaten","tag-pid","tag-rds","tag-workshop"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/blog.rwth-aachen.de\/forschungsdaten\/en\/wp-json\/wp\/v2\/posts\/4861","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.rwth-aachen.de\/forschungsdaten\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.rwth-aachen.de\/forschungsdaten\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.rwth-aachen.de\/forschungsdaten\/en\/wp-json\/wp\/v2\/users\/3308"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.rwth-aachen.de\/forschungsdaten\/en\/wp-json\/wp\/v2\/comments?post=4861"}],"version-history":[{"count":14,"href":"https:\/\/blog.rwth-aachen.de\/forschungsdaten\/en\/wp-json\/wp\/v2\/posts\/4861\/revisions"}],"predecessor-version":[{"id":4879,"href":"https:\/\/blog.rwth-aachen.de\/forschungsdaten\/en\/wp-json\/wp\/v2\/posts\/4861\/revisions\/4879"}],"wp:attachment":[{"href":"https:\/\/blog.rwth-aachen.de\/forschungsdaten\/en\/wp-json\/wp\/v2\/media?parent=4861"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.rwth-aachen.de\/forschungsdaten\/en\/wp-json\/wp\/v2\/categories?post=4861"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.rwth-aachen.de\/forschungsdaten\/en\/wp-json\/wp\/v2\/tags?post=4861"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Getting to know each other – Speed Dating<\/span><\/h3>\n
\nIt’s quite simple! Thanks to the project structure, Coscine allows easy data management as well as access for all project members, who have access to their project data and code. In addition, research data can be automatically linked to metadata, and individual and project-specific application profiles, known as application profiles, can be created. These application profiles in turn contain individual metadata combinations from various metadata schemas and terms. Integrated IT services such as the Research Data Storage (RDS) and GitLab are offered as resources for the data sources. In the future, the integration of Nextcloud as well as Sciebo will also be targeted. When using the RDS as a storage resource, research data can be archived for 10 years after the end of the project. Last but not least, all FAIR principles are supported by Coscine.<\/p>\nFAIRly in Love<\/span><\/h3>\n
<\/a>Discover why your research data still needs your love<\/span><\/h3>\n
Future FAIR improvements<\/span><\/h3>\n
Workshops benefit from the exchange with each other<\/span><\/h3>\n
\n<\/strong>Is Coscine used across all faculties\/areas at RWTH Aachen University? Are there any departments that cannot use Coscine?<\/p>\n
\n<\/strong>Yes, Coscine is already in use at RWTH Aachen University regardless of department and is a generic FDM platform (i.e., without a subject-specific focus). Since RWTH has a large focus on engineering, mainly associated faculties are represented in Coscine so far. Initially, Coscine only queries generic metadata fields on project and resource level, the subject-specific application profiles on file level can be selected by researchers themselves. Thus, each discipline can individualize Coscine for itself.<\/p>\n
\nDo you obtain the ePIC PIDs from GWDG or do you have your own infrastructure at RWTH?<\/p>\n
\nThe ePIC-PIDs are obtained from the GWDG<\/a>. The GWDG provides us with two servers for this purpose, one for test PIDs and one for the productive PIDs.<\/p>\n
\nIf Coscine is not intended for long-term archiving, then the PIDs are not really persistent, are they?<\/p>\n
\nThe PIDs that are output by Coscine persistently reference the digital object behind them, which is always a resource in Coscine. However, the data, which in turn is stored in the resource, can change. This is the only way PIDs can be issued for “warm” data – by referring only to the storage environment of the data (for RDS, this refers to the respective S3 bucket). Once the 10 years of archiving have elapsed after the end of the project, the data is deleted. The PID will continue to point to the location (e.g., the deleted S3 bucket). Therefore, a permanent placeholder with metadata for deleted resources will be implemented at this location in the future.<\/p>\n
\nTo what extent is the use of Coscine (already) mandatory or is it only recommended so far?<\/p>\n
\nThe use of Coscine is not mandatory and will continue to be offered and recommended on a voluntary basis in the future. What makes it attractive for researchers to use it is mainly the access to free storage on the RDS and the compliance with FDM guidelines according to application requirements.<\/p>\n
\nHow long did their pilot phase run?<\/p>\n
\nCoscine’s pilot phase started in March 2020, and we aim to have Coscine in regular operation in the second quarter of 2023.<\/p>\n
\nWhat is the size of the team of developers working on Coscine?<\/p>\n
\nCoscine has about ten employees with different specialties and employment contracts – a total of about six full-time positions. The developers are employed through various third-party funded projects.<\/p>\n
\nWhere do new application profiles created with the AIMS application profile generator end up?<\/p>\n
\nNew application profiles are deposited in the associated and open Coscine-GitLab repository.<\/p>\nConclusion<\/span><\/h3>\n
Learn more<\/span><\/h3>\n