forked from FAIR-by-Design-Methodology/templates
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
83d0166
commit ab6737a
Showing
2 changed files
with
48 additions
and
0 deletions.
There are no files selected for viewing
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,48 @@ | ||
--- | ||
title: "Takeaways" | ||
author: "Skills4EOSC" | ||
tags: | ||
- FAIR-by-Design learning materials | ||
- Recap | ||
- Takeaways | ||
- Co-creation | ||
--- | ||
|
||
# Conclusion | ||
|
||
## Slides | ||
|
||
[Download the slides here](https://github.com/FAIR-by-Design-Methodology/CLARIN-Training/raw/main/resources/2nd%20Session/08%20Wrap-up/wrap-up.pptx){:download} | ||
|
||
## Takeaways | ||
|
||
To create FAIR-by-Design learning materials, consider the following: | ||
|
||
1. **Ensure Findability**: Structure content with clear metadata, tags, and descriptions to make it easily searchable. Use consistent terminology across materials. Get a PID for your materials. | ||
2. **Promote Accessibility**: Design materials to be accessible to all users, including those with disabilities. Use open licenses and ensure content is available in multiple formats (e.g., PDFs, HTML). | ||
3. **Foster Interoperability**: Use standard open formats and frameworks that allow materials to be easily integrated into different systems. Ensure compatibility with various platforms. | ||
4. **Encourage Reusability**: Design modular content that can be repurposed for different contexts. Provide clear documentation and guidelines for reuse, ensuring that others can adapt the materials without losing the original intent. | ||
- this includes plans, assessment details, activities description and facilitation guide | ||
5. **Engage the Community**: Involve users in the development and refinement of materials. Use feedback loops, such as surveys and discussions, to continually improve the resources. | ||
6. **Use Open Tools**: Leverage open-source tools for content creation and dissemination to align with FAIR principles and ensure that materials can be widely shared and adapted. | ||
7. **Document Your Process**: Keep thorough documentation of the creation process, including decisions made regarding content structure, licensing, and technical implementation. This transparency helps others understand and build upon your work. | ||
- provide information in files such as README, CITATION, CODE_OF_CONDUCT, LICENSE, CONTRIBUTORS, RELEASE_NOTES, etc. | ||
8. **Version Control**: Use version control systems like GitHub to manage updates and track changes, ensuring that the most current and relevant materials are always accessible. | ||
|
||
## Let us co-create | ||
|
||
The FAIR-by-Design methodology is a living document, continuously evolving as we refine and enhance it based on new insights and feedback from our community. We’re committed to ensuring that it remains relevant, effective, and aligned with the latest developments in instructional design. | ||
|
||
**We Need Your Input!** | ||
|
||
We deeply value your thoughts and ideas. Your feedback is crucial in shaping the future of the FAIR-by-Design methodology. Let’s collaborate to co-create an even better version of these materials. | ||
|
||
**How You Can Contribute**: | ||
|
||
- **[EC Survey Form](https://ec.europa.eu/eusurvey/runner/FAIR-by-Design_Open_Survey)**: Your voice matters, and the EC Survey form is always open for your input. Share your thoughts anytime. | ||
- **GitHub Issues**: Have an idea for a new feature or notice something that needs fixing? Create a GitHub Issue to bring it to our attention. | ||
- **GitHub Discussions**: Engage with the community by asking questions, sharing comments, or starting a discussion on GitHub. Every perspective helps us grow. | ||
- **Pull Requests**: If you have specific suggestions for improvement, why not take it a step further and submit a pull request? Your contribution can directly shape the next version. | ||
- **[Feedback Form](https://forms.gle/XDkcga4y8zAVJDEn8)**: Tell us what you think about this training by filling out the Feedback form. Your insights will help us improve the experience for everyone. | ||
- **[Post-Mortem Document](../../Feedback/FAIR-by-Design_postmortem.docx){:download}**: Have you applied the methodology in your work? We’d love to hear about your experience. Share your impressions and outcomes in the Post-Mortem document to help us learn from real-world applications. | ||
|
Binary file not shown.