-
Notifications
You must be signed in to change notification settings - Fork 16
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Deploying to gh-pages from @ f6d2994 🚀
- Loading branch information
Showing
5 changed files
with
118 additions
and
18 deletions.
There are no files selected for viewing
80 changes: 80 additions & 0 deletions
80
...-on-the-development-and-implementation-of-basic-services-and-dataplants-contribution.html
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,80 @@ | ||
| <html class="has-navbar-fixed-top" style="scroll-behavior: smooth;"> | ||
| <head> | ||
| <meta charSet="utf-8"/> | ||
| <meta name="viewport" content="width=device-width, initial-scale=1"/> | ||
| <link rel="icon" type="image/png" sizes="32x32" href="/images/favicon.png"/> | ||
| <title> | ||
| nfdi4plants - News | ||
| </title> | ||
| <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css"/> | ||
| <link rel="stylesheet" type="text/css" href="/style/style.css"/> | ||
| <link rel="stylesheet" type="text/css" href="https://cdn.jsdelivr.net/npm/@creativebulma/[email protected]/dist/css/bulma-collapsible.min.css"/> | ||
| <script defer="true" src="https://kit.fontawesome.com/0d3e0ea7a6.js" crossOrigin="anonymous"></script> | ||
| <script type="module" src="/js/bundle.js"></script> | ||
| <style> | ||
|
|
||
| body { | ||
| margin: 0px; | ||
| } | ||
|
|
||
| thead tr th, strong { | ||
| color: var(--accent-text-color) !important | ||
| } | ||
|
|
||
| a { | ||
| color: var(--link-color, #4FB3D9) !important; | ||
| } | ||
|
|
||
| a:hover { | ||
| color: var(--link-hover-color, #3A3A3A) !important; | ||
| } | ||
|
|
||
| thead { | ||
| font-size: 1.2rem; | ||
| } | ||
|
|
||
| nfdi-toc, nfdi-body { | ||
| --outside-background-color: rgb(240, 243, 246); | ||
| --header-color: rgb(10, 12, 16) | ||
| --element-text-color: #0E1116; | ||
| --element-background-color: #fff; | ||
| --accent-text-color: rgb(31, 194, 167); | ||
| --link-color: #4FB3D9; | ||
| --link-hover-color: #8ad3ee; | ||
| } | ||
|
|
||
| </style> | ||
| </head> | ||
| <nfdi-navbar></nfdi-navbar> | ||
| <body> | ||
| <section class="hero is-medium is-dark has-bg-lightblue"> | ||
| <div class="hero-body"> | ||
| <div class="container has-text-centered"> | ||
| <h1 class="title"> | ||
|
|
||
| </h1> | ||
| </div> | ||
| </div> | ||
| </section> | ||
| <section class="section"> | ||
| <div class="container p-4"> | ||
| <h1 class="title is-1"> | ||
| NFDI wide Workshop on the development and implementation of basic services (Base4NFDI) and DataPLANT's contribution | ||
| </h1> | ||
| <h2 class="subtitle is-2"> | ||
| 16 Feb 2024 | ||
| </h2> | ||
| <div class="content"> | ||
| <p>DataPLANT took part in an online workshop on the development and implementation of basic services coordinated by the NFDI. The objectives of the workshop held by Base4NFDI the 16th February online was to define the future development of basic services and to agree upon how consortia could or should commit to adopting a (potential) core service during the integration phase. With first service reaching phase three it needs to be clarified how the commitment should look like. For this a discussion on the coordination and decision making process was held as well as concrete ideas on how to ensure commitment to collaborating on core services generated. The considerations were refined in the breakout sessions.</p> | ||
| <p>A potential plan is to incorporate this into the mandatory requirements for the "integration phase" of the core service application. During the inaugural year, developments can still be observed. For the further steps consortia should: Signal the adoption within each consortium, optimally backed by a public statement with a specific project plan or roadmap. Here step-by-step Communities of Practice should be build, which consist of a team of consortium members supporting usage within the consortium, actively using it themselves, and reaching a critical mass. To reach a widespread impact in consortia, core services should be made available to the entire community and the commitment to the core service should have a critical mass in consortia, meaning that e.g. infrastructure facilities/data centers/researchers (if it is an end-user component).</p> | ||
| <p>DataPLANT itself plans to contribute to base services: Firstly, We are already in exchange with the IAM working group to investigate in a NFDI wide AAI solution. Secondly, we plan to expand established concepts and services in DataPLANT to the wider NFDI. For this, we had already launched an open "call for participation" at last year's CoRDI with a <a href="https://zenodo.org/records/10021181">poster</a> to encourage a general service for versioning and sharing code and data (based on GitLab). The feedback was consistently very good and interest from various institutions (and consortia) was definitely there. DataPLANT uses GitLab heavily as a starting point for the FDM workflows (centered around the ARC) and as a data repository. We are offering it as a package for an <a href="https://github.com/nfdi4plants/DataHUB">on-premise installation</a> and are in contact with various institutions on further roll-outs.</p> | ||
| <p><strong>Links</strong><br /> | ||
| <a href="https://zenodo.org/records/10021181">Poster - GitLab as a tool for Research Data Management</a><br /> | ||
| <a href="https://github.com/nfdi4plants/DataHUB">DataHUB – On-premise Installation</a></p> | ||
|
|
||
| </div> | ||
| </div> | ||
| </section> | ||
| </body> | ||
| <nfdi-footer></nfdi-footer> | ||
| </html> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.