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

Rephrase question set for DFG v5 catalog due to vagueness #203

Closed
sa-wetter opened this issue Aug 27, 2023 · 1 comment · Fixed by #236
Closed

Rephrase question set for DFG v5 catalog due to vagueness #203

sa-wetter opened this issue Aug 27, 2023 · 1 comment · Fixed by #236
Assignees
Milestone

Comments

@sa-wetter
Copy link
Member

Hi,

I'd like to make two suggestions for existing 'question sets' in the DFG v5 catalog.

In the section "long-term data accessibility", the question set simply reads "when available" which is also visible in the drop down overview of the catalog. How about changing the question set to "Data availability"? This would get rid of the vagueness if a person is filling out the section who has not reached that question but can see the preview on the right hand side of the screen. (see attached screenshot)
when_available

Similarly, the German "wann nutzbar" is equally vague. Here, "(zeitliche) Verfügbarkeit" could be better suited for section "Dauerhafte Zugänglichkeit".
wann_nutzbar

Let me know what you think.

Best,
Sarah

@Zack-83
Copy link
Member

Zack-83 commented Oct 13, 2023

@sa-wetter Hier ist die Liste der Dateien, wo der Titel auftaucht:
https://github.com/search?q=repo%3Ardmorganiser%2Frdmo-catalog+%22When+available%22&type=code

Ich würde auch @torsten-rathmann als Erstautor involvieren.

Du kannst direkt aus der Issue einen neuen Branch anlegen (und folglich eine Merge Request)

image

@Zack-83 Zack-83 added this to the Release 1.4.0 milestone Oct 26, 2023
@Zack-83 Zack-83 linked a pull request Nov 1, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants