Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal for DSW integration #803

Merged
merged 16 commits into from
Jan 28, 2022
Merged

Conversation

bedroesb
Copy link
Member

@bedroesb bedroesb commented Jan 14, 2022

Similar to the training, the metadata ca
Screenshot from 2022-01-14 15-03-59
n be used to list questions in the data stewardship wizard:

Using this snippet in the metdata:

---
dsw:
  - name: File Naming conventions
    uuid: bc5e3dbf-2923-4025-a49a-f204b01d4018
  - name: How will you do file naming and file organization?
    uuid: 8e886b55-3287-48e7-b353-daf6ab40f7d8
  - name: Are you using a filesystem with files and folders?
    uuid: a12aa967-28a5-4a9b-8df8-f7c533205ea4
---

LIVE PREVIEW

@floradanna
Copy link
Collaborator

@rwwh please, let us know what you think of this suggestion.

@rwwh
Copy link
Contributor

rwwh commented Jan 14, 2022

This looks good, I am just asking myself whether this is close enough to the relevant position in the page in case there are multiple sections (like with Human Data). Would it be considered in such cases to position an additional link close to the relevant location on the page? I guess the fact that we're using links to sections in the RDMkit pages directly from DS Wizard indicates that sub-page accuracy is needed in some cases.

@bedroesb
Copy link
Member Author

I assume also have this problem for FAIRCOOKBOOK... https://rdmkit.elixir-europe.org/data_transfer.html#more-information
Different sections having their own toollist,more information section, ... is asking for trouble though with the current jekyll implementation

@rwwh
Copy link
Contributor

rwwh commented Jan 14, 2022

I see two other ways, both with their own drawbacks. Maybe someone can think of another trick.

  1. Split sections on different topics into different pages.
  2. Insert textual references to these context-dependent resources, exactly in the right place.

Wild thought: Could the reference be given a # context and from that make the template recognize the header under which it should be inserted?

@bedroesb
Copy link
Member Author

Today in the editorial meeting we decided to add the links at the more information section automatically as a first step. In the meantime Martin will have a look how we could bring more information things below sections/within the text.

@bedroesb
Copy link
Member Author

thank you @MarekSuchanek for your code snippet in parsing the knowledge model!

_config.yml Outdated
@@ -10,7 +10,7 @@ description: "Find the answers to your Research Data Management questions in Lif
gtag: G-RXQ55EFTTH
# Google analytics tag

dsw_deep_link_prefix: https://researchers.ds-wizard.org/knowledge-models/dsw:root:latest/preview?questionUuid=
dsw_deep_link_prefix: https://converge.ds-wizard.org/knowledge-models/dsw:root-rdmkit:2.3.7/preview?questionUuid=
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MarekSuchanek this can propably also be https://converge.ds-wizard.org/knowledge-models/dsw:root-rdmkit:latest/preview?questionUuid= ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it can... with the automatic update of links, the latest seems to be the optimal way of linking.

@bedroesb
Copy link
Member Author

@rwwh Maybe we/you open an issue about sections on pages and its corresponding information. + subpages? I think this pull request is ready to be merged.

@bedroesb bedroesb merged commit 3b5b71d into elixir-europe:master Jan 28, 2022
@bedroesb bedroesb deleted the DSW-integration branch August 21, 2023 08:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants