Skip to content

Commit 9cdb66e

Browse files
authored
Merge pull request #76 from datasharingframework/v1.7.1
Added Content for DSF v1.7.1
2 parents 319088e + 62dd579 commit 9cdb66e

33 files changed

+2666
-4
lines changed
Binary file not shown.
Binary file not shown.

docs/src/.vuepress/theme.ts

Lines changed: 89 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ export default hopeTheme({
4343
prefix: "/stable/",
4444
children: [
4545
{
46-
text: "Guideline v1.7.0 (stable)",
46+
text: "Guideline v1.7.1 (stable)",
4747
icon: "info",
4848
children: ["index", "maintain/install", "maintain/upgrade-from-0", "maintain/allowList-mgm", "maintain/install-plugins", "develop/create", "contribute/"],
4949
}
@@ -66,7 +66,7 @@ export default hopeTheme({
6666
text: "Versions",
6767
icon: "note",
6868
// children:["/v1/"],
69-
children: [{ text: "v1.7.0 (stable)", link: "/stable/" }, { text: "v1.6.0", link: "/v1.6.0/" }, { text: "v1.5.2", link: "/v1.5.2/" }, { text: "v1.5.1", link: "/v1.5.1/" }, { text: "v1.5.0", link: "/v1.5.0/" }, { text: "v1.4.0", link: "/v1.4.0/" }, { text: "v1.3.2", link: "/v1.3.2/" }, { text: "v1.3.1", link: "/v1.3.1/" }, { text: "v1.3.0", link: "/v1.3.0/" }, { text: "v1.2.0", link: "/v1.2.0/" }, { text: "v1.1.0", link: "/v1.1.0/" }, { text: "v1.0.0", link: "/v1.0.0/" }, { text: "v0.9.3 (archived)", link: "/oldstable/"}],
69+
children: [{ text: "v1.7.1 (stable)", link: "/stable/" }, { text: "v1.7.0", link: "/v1.7.0/" }, { text: "v1.6.0", link: "/v1.6.0/" }, { text: "v1.5.2", link: "/v1.5.2/" }, { text: "v1.5.1", link: "/v1.5.1/" }, { text: "v1.5.0", link: "/v1.5.0/" }, { text: "v1.4.0", link: "/v1.4.0/" }, { text: "v1.3.2", link: "/v1.3.2/" }, { text: "v1.3.1", link: "/v1.3.1/" }, { text: "v1.3.0", link: "/v1.3.0/" }, { text: "v1.2.0", link: "/v1.2.0/" }, { text: "v1.1.0", link: "/v1.1.0/" }, { text: "v1.0.0", link: "/v1.0.0/" }, { text: "v0.9.3 (archived)", link: "/oldstable/"}],
7070
},
7171
{
7272
text: "",
@@ -217,7 +217,7 @@ export default hopeTheme({
217217
]
218218
},
219219
],
220-
"/v1.7.0/": [
220+
"/v1.7.1/": [
221221
{
222222
text: "Home",
223223
icon: "home",
@@ -300,6 +300,92 @@ export default hopeTheme({
300300
children: ["create", "upgrade-from-0" ],
301301
},
302302
],
303+
"/v1.7.0/": [
304+
{
305+
text: "Home",
306+
icon: "home",
307+
link: "/",
308+
},
309+
{
310+
text: "Current version",
311+
icon: "update",
312+
link: "/stable/",
313+
}, {
314+
text: "Maintain a DSF instance",
315+
icon: "tool",
316+
prefix: "maintain/",
317+
link: "maintain/",
318+
children: ["install", "upgrade-from-1", "upgrade-from-0", "allowList-mgm", "root-certificates", "passwords-secrets", {
319+
text: "FHIR Reverse Proxy",
320+
icon: "module",
321+
prefix: "fhir-reverse-proxy/",
322+
link: "fhir-reverse-proxy/",
323+
children: [{
324+
icon: "config",
325+
text: "Configuration",
326+
link: "configuration"
327+
}]
328+
}, {
329+
text: "FHIR Server",
330+
icon: "module",
331+
prefix: "fhir/",
332+
link: "fhir/",
333+
children: [{
334+
icon: "config",
335+
text: "Configuration",
336+
link: "configuration"
337+
}, {
338+
icon: "config",
339+
text: "Access Control",
340+
link: "access-control"
341+
}, {
342+
icon: "config",
343+
text: "OpenID Connect",
344+
link: "oidc"
345+
}]
346+
}, {
347+
text: "BPE Reverse Proxy",
348+
icon: "module",
349+
prefix: "bpe-reverse-proxy/",
350+
link: "bpe-reverse-proxy/",
351+
children: [{
352+
icon: "config",
353+
text: "Configuration",
354+
link: "configuration"
355+
}]
356+
}, {
357+
text: "BPE Server",
358+
icon: "module",
359+
prefix: "bpe/",
360+
link: "bpe/",
361+
children: [{
362+
icon: "config",
363+
text: "Configuration",
364+
link: "configuration"
365+
}, {
366+
icon: "config",
367+
text: "Access Control",
368+
link: "access-control"
369+
}, {
370+
icon: "config",
371+
text: "OpenID Connect",
372+
link: "oidc"
373+
}]
374+
},
375+
{
376+
text: "Install Plugins",
377+
icon: "plugin",
378+
link: "install-plugins"
379+
}],
380+
},
381+
{
382+
text: "Develop process plugins",
383+
icon: "plugin",
384+
prefix: "develop/",
385+
link: "develop/",
386+
children: ["create", "upgrade-from-0" ],
387+
},
388+
],
303389
"/v1.6.0/": [
304390
{
305391
text: "Home",

docs/src/stable

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
v1.7.0
1+
v1.7.1

docs/src/v1.7.1/contribute/code.md

Lines changed: 97 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,97 @@
1+
---
2+
title: Contribute code
3+
icon: info
4+
---
5+
6+
Your code can make a difference for the Data Sharing Framework (DSF). We invite all users to share their code, tests, scripts and improvement ideas. Contributions of any size enhance the DSF and support the data sharing framework community.
7+
8+
### Benefits of Contributing:
9+
- Foster community growth and diversification.
10+
- Sharpen your coding skills.
11+
- Gain recognition in the DSF community.
12+
- Directly impact the future of data sharing in medicine.
13+
14+
Start now by visiting our contribution pages. Every line of code helps us build a stronger and more versatile DSF.
15+
16+
## General
17+
18+
### Code style
19+
20+
You can import our code style for your specific IDE:
21+
22+
* [Eclipse](https://github.com/datasharingframework/dsf/blob/main/src/main/resources/eclipse-formatter-config.xml). Open your preferences, click on `Java`, `Code style`, `Formatter`, `Import` and select the downloaded file.
23+
* [IntelliJ](https://github.com/datasharingframework/dsf/blob/main/src/main/resources/intellij-formatter-config.xml). Open your settings, click on `Editor`, `Code style`, `Java`, the settings icon, `import scheme`, `IntelliJ` and select the downloaded file.
24+
25+
Pull requests will only be approved if the code is formatted according to the code style configurations above. To format the code with maven before pushing to GitHub, use `mvn compile -Pformat-and-sort`.
26+
27+
### Branching strategy
28+
29+
[Git Flow](https://www.atlassian.com/de/git/tutorials/comparing-workflows/gitflow-workflow) is used as this project's branching strategy. Therefore, you will find the following structure:
30+
31+
* main
32+
* develop
33+
* issue
34+
* hotfix
35+
* release
36+
37+
Notice that only the first two elements listed are actual branches. The other elements are containers to hold all branches belonging to that category.
38+
39+
40+
#### Branch naming
41+
42+
The following ruleset is applied to name branches:
43+
44+
* `issue/<issue-number>_<issue-name>`
45+
* `hotfix/<version>`
46+
* `release/<version>`
47+
48+
## Setting up the project
49+
50+
This chapter lists all important requirements to get the project buildable and running properly.
51+
52+
### Java
53+
54+
This project uses Java JDK 17, so make sure you have it installed on your system.
55+
56+
### Docker
57+
58+
[Docker](https://www.docker.com/) is used in this project to test database functionality and to run more complex test-setups.
59+
60+
### Maven
61+
62+
The project relies on [Maven](https://maven.apache.org/) as its management tool.
63+
*Important:* When building the project you might encounter the following error:
64+
*Could not determine gpg version* [GPG](https://gnupg.org/) is used to sign artifacts for public release. Since this does not concern contributors, you may skip this step in the maven build process with `-Dgpg.skip`.
65+
66+
67+
## Workflow
68+
69+
1. Create an issue or comment on an issue that you want to contribute some feature
70+
2. Fork the repository, create a branch and mention it in the issue
71+
3. If you desire feedback, create a pull request or comment on it in the issue. Feel free to @ any member with write permissions if you feel like your request has not been registered yet. They will review your changes and/or change requests
72+
4. If your changes are production-ready, create a [pull request](https://github.com/datasharingframework/dsf/pulls).
73+
74+
### Pull request process
75+
76+
We follow Martin Fowler's method for managing pull requests. This approach categorizes pull requests based on the level of trust and experience of the contributor, as well as the impact of the changes. Here's how we apply it:
77+
78+
1. **Ship**: For our most trusted contributors with a proven track record. These members can merge their pull requests without prior review, typically for minor or highly confident changes.
79+
80+
2. **Show**: This level is for trusted contributors who need some oversight, as well as for experienced developers who want to demonstrate how certain changes should be made in the future. They create pull requests and show their work to the team.
81+
82+
3. **Ask**: New or less experienced contributors, as well as those submitting more complex changes, fall into this category. They are required to ask for feedback and approval before their changes can be merged, ensuring thorough review and quality control.
83+
84+
85+
This method helps us maintain a balance between code quality and efficient development, recognizing the varying levels of expertise among our contributors.
86+
87+
For more information on Fowler's approach, visit [Martin Fowler's article on Pull Requests](https://martinfowler.com/articles/ship-show-ask.html).
88+
89+
90+
## Data Security in DSF Development
91+
92+
The DSF (Data Sharing Framework) and its process plugins are frequently used to transmit sensitive personal data. To prevent the release of personal data during development, please adhere to the following guidelines:
93+
94+
- **No development with real personal data:** Always use anonymized or synthetic data for development purposes.
95+
- **No personal data in repositories:** Ensure no personal data is present in local and remote repositories intended for publication, not even temporarily.
96+
- **Review all log files:** Before using log files in issues, examples, etc., thoroughly review them to ensure no personal and sensitive data is included.
97+
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
title: Contribute documentation
3+
icon: info
4+
---
5+
6+
**Join us in enhancing our documentation!**
7+
8+
We believe in the power of community collaboration to make our documentation clearer, more comprehensive, and more user-friendly. There are several ways you can contribute, and we welcome greatly your input!
9+
10+
11+
1. **Contact us with feedback**: If you find any of our documentation unclear or if you think there's a topic not covered yet, please don't hesitate to reach out to us. Your perspective as a reader is invaluable in helping us to identify areas for improvement.
12+
2. **Create an issue**: You noticed something that needs fixing or you have a suggestion? Head over to our GitHub repository at [Data Sharing Framework Documentation](https://github.com/datasharingframework/datasharingframework.github.io/issues) and please create an issue. This way, our team and other contributors can track and address documentation changes systematically.
13+
3. **Contribute directly with a pull request**: If you're feeling proactive and want to make direct changes, you're more than welcome to submit a pull request. Visit our GitHub repository at [Data Sharing Framework Documentation](https://github.com/datasharingframework/datasharingframework.github.io) and feel free to propose your changes. Whether it's a typo fix, a new section, or enhanced explanations, every contribution counts.
14+
15+
We're excited to see your suggestions and are grateful for every contribution that helps us improve. Let's build better documentation together!

docs/src/v1.7.1/contribute/readme.md

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
title: Contribute
3+
icon: info
4+
---
5+
6+
We are thrilled that you consider contributing to our projects. Your contributions, big or small, are greatly valued and play a significant role in the success and improvement of our work. Whether you're a seasoned developer or just starting out, there's a place for you here to make a meaningful impact.
7+
8+
### **Ways you can contribute:**
9+
10+
11+
1. **Helping other users**:
12+
* **MII Zulip**: If you are part of the German Medical Informatics Initiative, [join the MII Zulip community](https://mii.zulipchat.com/#narrow/stream/392426-Data-Sharing-Framework-.28DSF.29) to assist others, share your knowledge, and learn from fellow contributors.
13+
* **GitHub Discussions**: Engage with our community in [GitHub Discussions](https://github.com/datasharingframework/dsf/discussions) by answering questions, providing feedback, and sharing your insights.
14+
2. **Testing releases**:
15+
* **Stay ahead**: Help us testing the latest releases. Your feedback on functionality, bugs, and user experience is invaluable.
16+
* **Report findings**: Share your testing results to help us refine and enhance our releases.
17+
3. **Reviewing changes**:
18+
* **Peer review**: Contribute by reviewing pull requests. Your insights can help ensure the quality and integrity of code changes.
19+
* **Constructive feedback**: Offer constructive feedback and suggestions to help improve and refine proposed changes.
20+
4. **Documentation changes**:
21+
* **Improve documentation**: Help us improving and updating our documentation. Clear and accurate documentation is crucial for user understanding and success. Please checkout our [Getting started guide for documentation contributions](./documentation) to DSF.
22+
* **Suggest improvements**: If you notice gaps or areas for enhancement in our documentation, we welcome [your suggestions and contributions](https://github.com/datasharingframework/datasharingframework.github.io).
23+
5. **Contributing bug reports**:
24+
* **Report bugs**: If you find a bug, please report it via [an issue on GitHub](https://github.com/datasharingframework/dsf/issues). Detailed bug reports are incredibly helpful.
25+
* **Reproduction steps**: Include steps to reproduce the bug and any relevant logs according to our bug report issue template.
26+
6. **Contributing feature requests**:
27+
* **Suggest features**: You have an idea for a new feature? We'd love to hear it! Open an issue to describe your proposed feature and its potential benefits according to our feature request template.
28+
* **Collaborate on implementation**: If you're able to, contribute to the development of your proposed feature or bug fix. Collaboration can lead to more innovative and effective solutions. Please checkout our [Getting started guide for code contributions](./code) to DSF.
29+
7. **Contributing process plugins**:
30+
* **Develop process plugins for the DSF**: If you have ideas for a process plugin, we encourage you to develop and contribute them. Our [Getting started guide for process plugin development](https://dsf.dev/stable/develop/) will be a useful reference.
31+
* **Share your work**: Your plugins could be a valuable addition to the ecosystem and benefit other users.
32+
33+
Before you start contributing, we recommend reading our getting started guidelines for detailed information on our processes and standards. This ensures a smooth and productive experience for everyone involved.
34+
35+
**Your contributions in any form, are what drives the continuous growth and improvement of this project. Thank you for being a part of our community and for your willingness to contribute!**

docs/src/v1.7.1/develop/README.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
title: Develop Process Plugins
3+
icon: plugin
4+
---
5+
## Overview
6+
- [Create a new process plugin](create)
7+
- [Upgrade processes from 0.9.x](upgrade-from-0)

docs/src/v1.7.1/develop/create.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
title: Create a new process plugin
3+
icon: code
4+
---
5+
6+
Visit the [how the DSF can help you](../../for-you/) page to get started.
7+
8+
9+
::: tip Work in progress
10+
We are currently in the process of updating the written documentation on how to create a DSF process plugin. In the meantime we recommend to study the oldstable version of the [process plugin tutorial](/oldstable/tutorial/). Additionally, we recommend to take a look at the upgraded DSF processes here:
11+
- The [hello world plugin](https://github.com/datasharingframework/dsf-process-hello-world)
12+
- The [ping pong plugin](https://github.com/datasharingframework/dsf-process-ping-pong)
13+
- The [update allowlist plugin](https://github.com/datasharingframework/dsf-process-allow-list)
14+
:::
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
title: Upgrade processes from 0.9.x
3+
icon: update
4+
---
5+
::: tip Work in progress
6+
We are currently in the process of updating the written documentation on how to upgrade a DSF process plugin to DSF 1.0.0. In the meantime we recommend to take a look at the provided sample plugin and the upgraded DSF plugins:
7+
- The [hello world plugin](https://github.com/datasharingframework/dsf-process-hello-world)
8+
- The [ping pong plugin](https://github.com/datasharingframework/dsf-process-ping-pong)
9+
- The [update allowlist plugin](https://github.com/datasharingframework/dsf-process-allow-list)
10+
:::

0 commit comments

Comments
 (0)