You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: