Explore use of CEDAR, either complete Workbench, or at least template standards

[cmungall]

We should explore the use of CEDAR:

https://metadatacenter.org/

CEDAR allows for the easy creation of metadata templates, and automatically builds UIs that have functionality such as type checking and ontology autocomplete based on designated ontology branches.

Even if you opt not to use the UI, the CEDAR group has defined standard ways of specifying a template and fields within a template that may be of use to us here.

There is a paper describing the CEDAR Workbench here:
https://link.springer.com/chapter/10.1007/978-3-319-68204-4_10

For the more technical members of this group, I found the following documents describing the CEDAR data model and JSON-LD structures helpful:

• https://github.com/metadatacenter/cedar-docs/wiki/CEDAR-Template,-Element,-and-Field-Instances
• https://more.metadatacenter.org/tools-training/outreach/cedar-template-model

[wdduncan]

Just a thought: I wonder if it is possible to integrate the templates with biolinkml?

[cmungall]

do you want to make a new ticket on how biolinkml might be used? thx!

…

On Wed, Dec 11, 2019 at 8:57 AM Bill Duncan ***@***.***> wrote: Just a thought: I wonder if it is possible to integrate the templates with biolinkml? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6?email_source=notifications&email_token=AAAMMOOX3DX3NRXF5VG3EVLQYDWTDA5CNFSM4JZF2WM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGTGKVA#issuecomment-564553044>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAMMOOZUTHBJUF5LW2L6PLQYDWTDANCNFSM4JZF2WMQ> .

[wdduncan]

Will do :) On Wed, Dec 11, 2019 at 10:52 AM Chris Mungall <notifications@github.com> wrote:

…

do you want to make a new ticket on how biolinkml might be used? thx! On Wed, Dec 11, 2019 at 8:57 AM Bill Duncan ***@***.***> wrote: > Just a thought: I wonder if it is possible to integrate the templates with > biolinkml? > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > < #6?email_source=notifications&email_token=AAAMMOOX3DX3NRXF5VG3EVLQYDWTDA5CNFSM4JZF2WM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGTGKVA#issuecomment-564553044 >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AAAMMOOZUTHBJUF5LW2L6PLQYDWTDANCNFSM4JZF2WMQ > > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#6?email_source=notifications&email_token=AAYJ7TWFD7YEE273VMFVEYDQYEEE7A5CNFSM4JZF2WM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGTTUKA#issuecomment-564607528>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYJ7TUFRK56HMAVZXTIGE3QYEEE7ANCNFSM4JZF2WMQ> .

[lschriml]

Use of template, CEDAR, or otherwise sound good for the NMDC efforts.
The GSC doesn't produce templates for users.
The INSDC has templates in place.

Are you looking at CEDAR for devising the JSON implementation ?

Cheers,
Lynn

[cmungall]

Thanks for the info!

Yes, I have been looking at the CEDAR datamodel/JSON-LD schema with a view to using this for the mixs-ng structured representation of templates

[only1chunts]

A while back I did have a play in the CEDAR workbench, and created this draft version of a MIGS checklist:
https://tinyurl.com/vc95ym6
The JSON version of it can be seen right at the bottom of the page, expand the advance view option