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

OEMetaBuilder: Add links to the metadata schema #1824

Open
1 task
amanda-wein opened this issue Sep 9, 2024 · 0 comments
Open
1 task

OEMetaBuilder: Add links to the metadata schema #1824

amanda-wein opened this issue Sep 9, 2024 · 0 comments
Labels
enhancement NFDI Issues related to NFDI

Comments

@amanda-wein
Copy link

Description of the issue

Currently when using the OEMetaBuilder, if a term is unclear or more guidance is needed to fill out a field, the best solution is to go directly to the OEMetadata schema, which has more detailed term definitions as well as examples of what the content of a field should look like.

There are also instances where the field instructions direct the user to visit a different website for information. Specifically, in the "Licenses" section, under "Instruction" the informational text says "A short description of rights and restrictions. The use of tl;drLegal is recommended." No indication is given here that tl;drLegal is a different website that the user should visit to get more info; the metadata schema does provide a link to the tl;drLegal website, but the OEMetaBuilder form does not.

Ideas of solution

Add links in the OEMetaBuilder so that a user can click on a field name to pull up the field's definition in the metadata schema. Also, add a link to tl;drLegal directly in the form.

Workflow checklist

@a-steinert a-steinert added the NFDI Issues related to NFDI label Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement NFDI Issues related to NFDI
Projects
None yet
Development

No branches or pull requests

2 participants