You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
[](https://github.com/elixir-europe/rdmkit/actions/workflows/tool_list_conversion.yml)[](https://github.com/elixir-europe/rdmkit/actions?query=workflow%3A%22Jekyll+site+CI%22)[](https://doi.org/10.5281/zenodo.5110061)[](https://github.com/ELIXIR-Belgium/elixir-toolkit-theme)
1
+
[](https://github.com/elixir-europe/rdmkit/actions/workflows/tool-list-validation.yml)[](https://github.com/elixir-europe/rdmkit/actions?query=workflow%3A%22Jekyll+site+CI%22)[](https://doi.org/10.5281/zenodo.5110061)[](https://github.com/ELIXIR-Belgium/elixir-toolkit-theme)
Copy file name to clipboardExpand all lines: _data/tool_and_resource_list.yml
+7-4Lines changed: 7 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -1335,7 +1335,7 @@
1335
1335
name: Minimum Information about Plant Phenotyping Experiment (MIAPPE)
1336
1336
registry:
1337
1337
fairsharing: nd9ce9
1338
-
tess: MIAPPE
1338
+
tess: Minimum Information about Plant Phenotyping Experiment
1339
1339
url: https://www.miappe.org/
1340
1340
- description: Cloud storage and file sharing service from Microsoft
1341
1341
id: microsoft-azure
@@ -1497,11 +1497,12 @@
1497
1497
fairsharing: re1278
1498
1498
tess: OmicsDI
1499
1499
url: https://www.omicsdi.org
1500
-
- description: OMOP is a common data model for the harmonisation for of observational health data.
1500
+
- description: OMOP is a common data model for the harmonisation of observational health data.
1501
1501
id: omop-cdm
1502
-
name: OMOP-CDM
1502
+
name: The Observational Medical Outcomes Partnership Common Data Model (OMOPCDM)
1503
1503
registry:
1504
1504
tess: OMOP-CDM
1505
+
fairsharing: qk984b
1505
1506
url: https://ohdsi.github.io/CommonDataModel/
1506
1507
- description: OntoMaton facilitates ontology search and tagging functionalities within Google Spreadsheets.
1507
1508
id: onotomaton
@@ -3488,8 +3489,10 @@
3488
3489
biotools: agrischemas
3489
3490
url: https://github.com/Rothamsted/agri-schemas
3490
3491
- description: A data model for the collection of cancer-related clinical information and genomics metadata.
3491
-
name: The Minimal Dataset for Cancer of the 1+Million Genomes Initiative (1+MG-MDC)
3492
3492
id: 1pmg-mdc
3493
+
name: The Minimal Dataset for Cancer of the 1+Million Genomes Initiative (1+MG-MDC)
3494
+
registry:
3495
+
fairsharing: 0d9069
3493
3496
url: https://zenodo.org/records/10784601
3494
3497
- description: The PSI-MS Controlled Vocabulary consists of a large collection of structured terms covering description and use of Mass Spectrometry instrumentation as well as Protein Identification and Quantitation software.
Copy file name to clipboardExpand all lines: pages/about/events.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,10 @@ github:
4
4
file_path: _data/events.yml
5
5
---
6
6
7
+
Explore upcoming and past events connected to RDMkit, from webinars and workshops to conference sessions and community gatherings focused on research data management.
8
+
7
9
{% include events.html event_type="upcoming_event" title=true %}
8
10
9
11
10
12
{% include events.html event_type="past_event" title=true %}
Copy file name to clipboardExpand all lines: pages/about/news.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,8 @@ github:
4
4
file_path: _data/news.yml
5
5
---
6
6
7
+
Keep up with the latest developments around RDMkit, including new content, community highlights, collaborations, and other updates relevant to research data management in the life sciences.
8
+
7
9
[<iclass="fa fa-rss me-2"></i>Subscribe to the RSS feed]({{ '/feed.xml' | relative_url }}){: class="btn btn-light rounded-pill"}
Copy file name to clipboardExpand all lines: pages/about/outreach.md
+50-4Lines changed: 50 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,29 @@ We are, since the beginning, actively spreading the word about RDMkit making sur
6
6
7
7
## Presentations
8
8
9
+
### RDMkit at ISMB/ECCB 2025
10
+
11
+
**2025-07-24**
12
+
13
+
RDMkit was presented as part of the eScience Lab ISMB/ECCB 2025 presentations, with a poster titled "Research Data Management Toolkit for Life Scientists". The poster materials can be found on [Zenodo](https://zenodo.org/records/15830546).
14
+
15
+
### Hands-On RDM with ELIXIR groups: Crafting short and long-term strategies
16
+
17
+
**2024-06-10**
18
+
19
+
These slides, presented at ELIXIR All Hands 2024, include RDMkit as part of the wider ELIXIR research data management ecosystem. The slides can be found on [F1000Research](https://f1000research.com/slides/14-27).
20
+
21
+
### RDMkit: A key resource for FAIR data management
22
+
23
+
**2024-06-11**
24
+
25
+
RDMkit was presented as a poster at ELIXIR All Hands 2024. The poster can be found on [F1000Research](https://f1000research.com/posters/13-727).
26
+
27
+
### RDMkit: The Research Data Management Toolkit for Life Sciences
28
+
29
+
**2023-09-12**
30
+
31
+
This presentation was given at the 1st Conference on Research Data Infrastructure (CoRDI 2023). The slides can be found on [Zenodo](https://zenodo.org/records/8354863).
9
32
10
33
### RDMkit poster at ELIXIR All Hands 2023
11
34
@@ -20,11 +43,35 @@ The poster can be found on [F1000Research](https://f1000research.com/posters/12-
20
43
21
44
RDMkit was introduced to the [DSIG](https://www.dtls.nl/about/community/interest-groups/data-stewards-interest-group/) at one of their monthly meetings, together with introduction on IDTkit and FAIRCookBook. [Presentation slides on RDMkit (PDF)](https://drive.google.com/file/d/12aHIH0rRU6ogOOacZr3K6PrzXylYgHIo/view).
22
45
23
-
### ELIXIR FAIR & Research Data Management know-how ecosystem - All hands 2022
46
+
### Research Data Management Toolkit (RDMkit): guidelines for plant phenotyping data management and sharing
47
+
48
+
**2022-09-26**
24
49
25
-
**2022-06-10**
50
+
This poster highlighted RDMkit in the context of plant phenotyping data management and sharing, and was presented at the 7th International Plant Phenotyping Symposium (IPPS2022). The poster can be found on [Zenodo](https://zenodo.org/records/7148792).
26
51
27
-
RDMkit was presented at all hands. The presentation can be found on [F1000Research](https://f1000research.com/slides/11-737).
52
+
### RDMkit - The research data management toolkit for life sciences
53
+
54
+
**2022-06-08**
55
+
56
+
RDMkit was presented as a poster at ELIXIR All Hands 2022. The poster can be found on [F1000Research](https://f1000research.com/posters/11-736).
57
+
58
+
### The ecosystem together - walkthrough from two perspectives: a User and a Contributor
59
+
60
+
**2022-06-09**
61
+
62
+
This ELIXIR All Hands 2022 presentation placed RDMkit in the wider FAIR and research data management ecosystem together with FAIRsharing, the FAIR Cookbook, DSW, WorkflowHub, and TeSS. The slides can be found on [F1000Research](https://f1000research.com/slides/11-636).
63
+
64
+
### RDMkit walkthrough
65
+
66
+
**2022-06-07**
67
+
68
+
RDMkit was presented at ELIXIR All Hands 2022 through a walkthrough of the toolkit. The slides can be found on [F1000Research](https://f1000research.com/slides/11-737).
69
+
70
+
### Registries walkthrough
71
+
72
+
**2022-06-09**
73
+
74
+
This ELIXIR All Hands 2022 talk focused on the registries connected to the broader RDMkit ecosystem, including FAIRsharing, TeSS, bio.tools, and WorkflowHub. The slides can be found on [F1000Research](https://f1000research.com/slides/11-940).
28
75
29
76
### Q-EBRA WORKSHOP: Your next grant application - methodological approach
30
77
@@ -105,4 +152,3 @@ OS Fair 2021 aims to bring together and empower open science communities and ser
Copy file name to clipboardExpand all lines: pages/contribute/preview_changes.md
+35-6Lines changed: 35 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,12 +5,12 @@ summary: Use your own fork to preview changes on the website.
5
5
6
6
## Introduction
7
7
8
-
This guide is mainly targeted at editors who have more rights than other contributors. Other contributors who want to preview their changes on their fork can skip towards the GitHub pages section right away.
8
+
Any contributor can preview changes from their own fork. The first part of this guide is mainly relevant for people who can edit the main repository directly and want to make sure their work happens on their fork instead. If you already work on your own fork, you can skip directly to [Preview your changes using GitHub Actions](#preview-your-changes-using-github-actions) or [Preview your changes using GitHub Codespaces](#preview-your-changes-using-github-codespaces).
9
9
10
10
11
11
## Make changes on your fork
12
12
13
-
As an editor with editing rights, changes made by clicking on the pencil icon will be committed to a branch on the main website itself. This is not a problem in normal circumstances, but when one wants to preview changes on one's own fork, this is not wanted.
13
+
If you have write access to the main repository, changes made by clicking on the pencil icon can be committed to a branch on the main website itself. That is often fine, but it is not what you want if you prefer to preview changes from your own fork.
14
14
15
15
### 1. Make sure you have forked the main branch
16
16
@@ -44,13 +44,42 @@ This step is important. Make sure to commit to a new feature branch which you na
44
44
45
45
## Preview your changes using GitHub Actions
46
46
47
-
- Go to Settings > Pages and enable GitHub Actions as a source
48
-
- Go to Environments > github-pages and remove the rule under Deployment branches if you want to deploy other branches than master via Workflow Dispatch (manually triggered action)
49
-
- Enable GitHub Actions (and use Workflow Dispatch)
47
+
To preview a branch on your fork, you need to trigger the repository's existing GitHub Pages workflow manually.
48
+
49
+
1. Go to `Settings > Pages` in your fork and make sure the site is published from **GitHub Actions**.
50
+
2. If you want to deploy a feature branch instead of the default branch, go to `Settings > Environments > github-pages` and remove the restriction under **Deployment branches**.
51
+
3. Go to the `Actions` tab of your fork and open the `Jekyll site CI` workflow.
52
+
4. Click **Run workflow**. This is the GitHub interface for the `workflow_dispatch` trigger that is already defined in the workflow file; you do not need to enable anything extra for it.
53
+
5. Select the branch with your changes and start the workflow run.
54
+
6. Open the completed workflow run and use the deployment link shown in the workflow graph or the `View deployment` link to open the preview site.
50
55
51
56
{% include image.html file="deploy_using_gh_actions.png" alt="Got to the settings tab in your repo to enable GitHub pages" %}
52
57
53
58
59
+
## Preview your changes using GitHub Codespaces
60
+
61
+
GitHub Codespaces is another way to preview your changes without setting up Ruby or Docker on your own computer.
62
+
63
+
1. Open your fork on GitHub or the and switch to the branch that contains your changes.
64
+
2. Click `Code`, open the `Codespaces` tab, and create a new codespace for that branch.
65
+
3. In the codespace terminal, install the site dependencies:
66
+
67
+
```bash
68
+
bundle install
69
+
```
70
+
71
+
4. Start the local preview server from the repository root:
72
+
73
+
```bash
74
+
bundle exec jekyll serve
75
+
```
76
+
77
+
5. Open the preview by clicking the forwarded port link for port `4000`. If it does not open automatically, go to the `PORTS` tab in the codespace and open port `4000` from there.
78
+
6. Keep the server running while you edit files. The preview will refresh automatically after you save your changes.
79
+
80
+
{% include callout.html type="note" content="GitHub Codespaces availability and included usage depend on your GitHub plan or organisation settings." %}
81
+
82
+
54
83
## Open a Pull Request (PR) with your changes
55
84
56
85
Got to your newly created branch and click 'Contribute'. This will create a PR for the main repository.
@@ -61,6 +90,6 @@ You can always make changes after the creation of this pull request by going to
61
90
62
91
{% include image.html file="files_changed_github.png" alt="Files changed tab on GitHub" %}
63
92
64
-
and clicking on the 3 dots to edit the file again. Changes made this way will become visible in your preview automatically after a few minutes.
93
+
and clicking on the 3 dots to edit the file again. After committing new changes to your branch, run the `Jekyll site CI` workflow again from the `Actions` tab to update the preview.
65
94
66
95
{% include image.html file="3_dots_github.png" alt="File change options on GitHub" %}
0 commit comments