Actions

ConferenceCall 2023 02 22 and ConferenceCall 2023 02 15: Difference between pages

Ontolog Forum

(Difference between pages)
 
 
Line 2: Line 2:
|-
|-
! scope="row" | Session
! scope="row" | Session
| [[session::Ubergraph]]
| [[session::OBO Dashboards]]
|-
|-
! scope="row" | Duration
! scope="row" | Duration
Line 8: Line 8:
|-
|-
! scope="row" rowspan="3" | Date/Time
! scope="row" rowspan="3" | Date/Time
| [[has date::22 Feb 2023 17:00 GMT]]
| [[has date::15 Feb 2023 17:00 GMT]]
|-
|-
| 9:00am PST/12:00pm EST
| 9:00am PST/12:00pm EST
Line 22: Line 22:


== Agenda ==
== Agenda ==
* Ubergraph: A SPARQL endpoint with many OBO ontologies loaded and pre-reasoned with simple triples materialized
* OBO Dashboards
* Presenter: Jim Balhoff
* Presenters: Nico Matentzoglu, Anita Caron and [[CharlesHoyt|Charles Hoyt]]
* [https://bit.ly/41wx6LZ Video Recording]
* [https://bit.ly/3XQEGxJ Video Recording]


== Conference Call Information ==
== Conference Call Information ==
* Date: '''Wednesday, 22 Feb 2023'''  
* Date: '''Wednesday, 15 Feb 2023'''  
* Start Time: 9:00am PST / 12:00pm EST / 6:00pm CST / 5:00pm GMT / 1700 UTC  
* Start Time: 9:00am PST / 12:00pm EST / 6:00pm CST / 5:00pm GMT / 1700 UTC  
** ref: [http://www.timeanddate.com/worldclock/fixedtime.html?month=02&day=22&year=2023&hour=12&min=00&sec=0&p1=179 World Clock]  
** ref: [http://www.timeanddate.com/worldclock/fixedtime.html?month=02&day=15&year=2023&hour=12&min=00&sec=0&p1=179 World Clock]  
* Expected Call Duration: 1 hour
* Expected Call Duration: 1 hour
{{:OntologySummit2023/ConferenceCallInformation}}
{{:OntologySummit2023/ConferenceCallInformation}}
Line 37: Line 37:
* [[AlexanderDiehl|Alexander Diehl]]
* [[AlexanderDiehl|Alexander Diehl]]
* [[AlexShkotin|Alex Shkotin]]
* [[AlexShkotin|Alex Shkotin]]
* [[AllenBaron|Allen Baron]]
* [[AnitaCaron|Anita Caron]]
* [[ArwaIbrahim|Arwa Ibrahim]]
* [[ArwaIbrahim|Arwa Ibrahim]]
* [[AsiyahLin|Asiyah Lin]]
* [[AsiyahLin|Asiyah Lin]]
* [[ChrisKindermann|Chris Kindermann]]
* [[CharlieHoyt|Charlie Hoyt]]
* [[ChrisMungall|Chris Mungall]]
* [[ClaudiaSanchezBeatoJohnson|Claudia Sanchez-Beato Johnson]]
* [[ClaudiaSanchezBeatoJohnson|Claudia Sanchez-Beato Johnson]]
* [[CMAlvarez|C.M. Alvarez]]
* [[DamianGoutteGattat|Damian Goutte-Gattat]]
* [[DamianGoutteGattat|Damian Goutte-Gattat]]
* [[DarrenNatale|Darren A. Natale]]
* [[DavidOsumiSutherland|David Osumi-Sutherland]]
* [[FanLi|Fan Li]]
* [[FanLi|Fan Li]]
* [[Fathoni Musyaffa|Fathoni Musyaffa]]
* [[GaryBergCross|Gary Berg-Cross]]
* [[GaryBergCross|Gary Berg-Cross]]
* [[GuangrongQin|Guangrong Qin]]
* [[Giacomo Lanza|Giacomo Lanza]]
* [[HendrickBorgelt|Hendrick Borgelt]]
* [[HenriettHarmse|Henriett Harmse]]
* [[JamesOverton|James Overton]]
* [[JamesOverton|James Overton]]
* [[JanetSinger|Janet Singer]]
* [[JanetSinger|Janet Singer]]
* [[JenniferGiron|Jennifer Girón]]
* [[JieZheng|Jie Zheng]]
* [[JieZheng|Jie Zheng]]
* [[JimBalhoff|Jim Balhoff]]
* [[JimBalhoff|Jim Balhoff]]
* [[JohnJudkins|John Judkins]]
* [[JohnJudkins|John Judkins]]
* [[John Steinbeck|John Steinbeck]]
* [[Josh Lagrimas|Josh Lagrimas]]
* [[KaiBlumberg|Kai Blumberg]]
* [[KatieMullen|Katie Mullen]]
* [[KatieMullen|Katie Mullen]]
* [[KenBaclawski|Ken Baclawski]]
* [[KenBaclawski|Ken Baclawski]]
* [[Leigh Carmody|Leigh Carmody]]
* [[Leigh Carmody|Leigh Carmody]]
* [[MarciaZeng|Marcia Zeng]]
* [[MarciaZeng|Marcia Zeng]]
* [[MarkRessler|Mark Ressler]]
* [[Melissa Clarkson|Melissa Clarkson]]
* [[MichaelDeBellis|Michael DeBellis]]
* [[MikeBennett|Mike Bennett]]
* [[MikeBennett|Mike Bennett]]
* [[NancyWiegand|Nancy Wiegand]]
* [[Nicole Vasilevsky|Nicole Vasilevsky]]
* [[NicoMatentzoglu|Nico Matentzoglu]]
* [[NicoMatentzoglu|Nico Matentzoglu]]
* [[RamondLec|Ramond Lec]]
* [[PhilippeRoccaSerra|Philippe Rocca-Serra]]
* randi
* [[RaviSharma|Ravi Sharma]]
* [[RaviSharma|Ravi Sharma]]
* [[RayStefancsik|Ray Stefancsik]]
* [[RayStefancsik|Ray Stefancsik]]
* [[RhiannonCameron|Rhiannon Cameron]]
* [[RobertRovetto|Robert Rovetto]]
* [[RobertRovetto|Robert Rovetto]]
* [[SabrinaToro|Sabrina Toro]]
* [[SabrinaToro|Sabrina Toro]]
* [[SierraMoxon|Sierra Moxon]]
* [[SamsonTu|Samson Tu]]
* [[StefanoDeGiorgis|Stefano De Giorgis]]
* Sue
* [[SusanBello|Susan Bello]]
* [[SusanBello|Susan Bello]]
* [[TiagoLubiana|Tiago Lubiana]]
* [[UgurBayindir|Ugur Bayindir]]
* [[WasilaDahdul|Wasila Dahdul]]
* [[Umayer Reza|Umayer Reza]]
* [[YaseminBridges|Yasemin Bridges]]


== Discussion ==
== Discussion ==
[12:03] RaviSharma: Hello welcome everyone,
[11:57] RaviSharma: welcome everyone


[12:12] RaviSharma: what is the significance of word Axioms in other ontologies vs just used in other ontologies?
[12:06] James Overton: Here's a link to the slides: https://docs.google.com/presentation/d/1oKxBzSCZGuFlIhw6jAXw00xgEGs7KgmaVR54NEdPprw/edit#slide=id.g20803e73efb_0_85


[12:17] Sue: @Ravi the axioms have formal logic in which the terms from other ontologies are used to define the term in the focus ontology. It is one way to use terms from one ontology in another ontology. Another example of use would be as cross-references.
[12:09] Charlie Hoyt: not just prefixes but also CURIEs and IRIs


[12:17] Mike Bennett: Why equivalent class: Usually one would make the class a subclass both of it's usual (taxonomic) parent and of the restriction. the intersection is implicit
[12:11] RaviSharma: James  and Nico - shared design patterns - are these used from a design repository so when people develop ontologies, they can use the design templates?


[12:19] RaviSharma: Jim you showed both ways, which one has less errors? Say in constructing KG.
[12:14] James Overton: Ravi: Many OBO projects use their own templates and patterns, but we are only beginning to use shared patterns. This is a key part of the COB effort.


[12:20] James Overton: @Mike: We have a standard operation `relax` that converts equivalence axioms to simpler subclass axioms <http://robot.obolibrary.org/relax>. But I think the point stands that querying OWL in SPARQL is hard, and Jim is building toward presenting a more convenient solution.
[12:18] Charlie Hoyt: https://dashboard.obofoundry.org/


[12:23] Tiago Lubiana: Is there a way to differentiate stated/inferred relations in Ubergraph? E.g. one might be interested in retrieving only direct superclasses of a term, but all superclasses in the tree are inferred
[12:18] Charlie Hoyt: actual dashboard: obofoundry


[12:24] James Overton: relation-graph was added to ROBOT 1.9.2 very recently, as part of the <http://robot.obolibrary.org/extract#subset> command.
[12:18] Charlie Hoyt: https://dashboard.obofoundry.org/dashboard/index.html


[12:24] Chris Mungall: @Tiago - these are distinguishable the named graph the triple belongs to
[12:25] RaviSharma: I found a neat cross reference as to which other ontologies use a particular ontology that you are referencing.


[12:28] Alexander Diehl: Is the query language for Ubergraph SPARQL or just SPARQL-like?
[12:25] DOS: Very granular cell ontologies may define classes using reference data rather than textual definitions.  It can therefore be impossible to fulfill the unique text def requirement.  At best one can add a text definition that described the general class => non-uniqueness.  Because of this, the most detailed cell type ontology on the Foundry - FBbt - fails this test.  Would it be possible to modify the test to allow it to be fulfilled by links to reference data?


[12:28] Mike Bennett: @James thanks - makes sense.
[12:26] RaviSharma: How do you determine content accuracy by engaging the experts like doctors or nurses before you determine its readiness for practicing users operational maturity!


[12:29] James Overton: @Alexander: Jim is showing actual SPARQL. He's using a trick to define prefixes for commonly used terms such as `cell` and `has_output`, to make the SPARQL more readable.
[12:27] Charlie Hoyt: i am not familiar with the mondo custom OBO dashboard! This is so cool! For sure we need more strict requirements than what is currently in OBO Foundry
[12:29] James Overton: @Alexander: Jim is showing actual SPARQL. He's using a trick to define prefixes for commonly used terms such as `cell` and `has_output`, to make the SPARQL more readable.


[12:31] RaviSharma: Jim do these include GO relations mapping all gene pairs?
[12:30] James Overton: DOS:  Good point. The automated check for textual definitions is more strict than then principle, which says "most" terms should be defined. <https://obofoundry.org/principles/fp-006-textual-definitions.html>, we can change the automated check, but we need to make a decision about whether to err on the side of strictness or leniency.


[12:32] Chris Mungall: @Ravi - no, this is just the ontology
[12:30] James Overton: The principles were not written with automated checks in mind, and some are harder to automate than others.


[12:33] Asiyah: Is there a list of the 53 ontologies included in the Ubergraph?
[12:33] DOS: Will promotion to the top tier require passing all tests, or will there be some attempt to order based on how many tests are failing?


[12:39] Robert Rovetto: what is the visualization tool used for those graph images?
[12:34] James Overton: My opinion is that better dashboard score should rank higher, but there's no decision yet.


[12:40] Chris Mungall: https://github.com/INCATools/obographviz
[12:35] James Overton: OQUAT: https://cthoyt.github.io/oquat


[12:42] Asiyah Lin - NIAID: Is there a list of 53 ontologies included in the Ubergraph?
[12:35] Nico Matentzoglu: Presentation link: https://docs.google.com/presentation/d/1oKxBzSCZGuFlIhw6jAXw00xgEGs7KgmaVR54NEdPprw/edit#slide=id.g1dcecf06728_0_7


[12:42] Nico Matentzoglu: This query gives you all the phenotypic abnormalities linked to the urine sodium level: https://api.triplydb.com/s/J1QkfjIAw
[12:37] DOS: @James -I'd like to explore discuss how we might extend the principle to allow for a combination of free text def + formalised reference data links to be allowed. Without this, I feel like FBbt is being penalised for being so detailed - where less detailed and so less useful ontology would pass.


[12:43] James Overton: The README has a list of the included ontologies: https://github.com/INCATools/ubergraph
[12:38] Nico Matentzoglu: CL is the cell ontology, CLO is the cell line ontology


[12:43] Sierra Moxon: I’ve used this file to determine which ontologies are in Ubergraph https://github.com/INCATools/ubergraph/blob/master/ontologies.txt
[12:39] Alexander Diehl: Jonathan Bard, one of the originators of the Cell Ontology, in case anyone is curious (JB:JB)


[12:43] Nico Matentzoglu: Or you check Ubergraph: https://api.triplydb.com/s/0TLkJlDcA
[12:39] James Overton: DOS: I agree in general. I work on MHC Restriction Ontology (MRO) which is mostly complexes of proteins, where the logical definition says everything important. We could auto-generate textual definitions, but would that really MRO better? So I would like to see OBO refine the textual definition check.


[12:43] James Overton: Sierra's answer seems like a more complete list. Thanks!
[12:40] RaviSharma: So how did you find resolution of prefix issues?


[12:43] Asiyah Lin - NIAID: Thank you both, James and Sierra! and Nico!
[12:40] James Overton: https://github.com/cthoyt/obo-community-health


[12:44] RaviSharma: Jim have you checked the lost relations namely other than those that execute SPARQL and those that go in the error file?
[12:41] James Overton: ^^ I would like to see OBO refine both the textual definition principle and the automated check.


[12:54] RaviSharma: Nico should we not be concentrating on dealing with harmonizing and aligning in terms of levels of depth to achieve better semantic interoperation? Namely by domain overlap handling?
[12:42] Nicole Vasilevsky: For the OBO Community Health, is this up to date? I pushed to Mondo yesterday and it says the last push was in September


Reply from Gary Berg-Cross: Current automation of alignment and harmonization is limited but useful.  Some needs to be done manually but in that process we may come to understand what semantic depth means and automate a portion of it.
[12:42] RaviSharma: I am surprised that Envo is not being updated since August last year, does that mean that ENVO is stabilized or that development is slow?


[13:00] Asiyah: Is there a way to crowd source people's mappings happened everywhere?
[12:43] James Overton: Nicole: I see "2023-02-15" as the update date for MONDO.


[13:01] James Overton: @Asiyah: Yes, SSSOM is part of Mapping Commons: https://github.com/mapping-commons
[12:43] DOS: I love the Community Health dashboard.


[13:01] Sierra Moxon: I'm curious if the "confidence score" has a restricted range?
[12:43] Nicole Vasilevsky: Oh, I see it was probably an old screenshot! Ignore me


[13:03] Nico: yes, its basically %
[12:44] RaviSharma: Is quality score or effort a metadata?


[13:05] RaviSharma: I asked about a way of controlling the ambiguities as we do while developing software, to which Nico replied that one could filter or selectively map terms from e,g, SnoMed so that two way connections are somewhat possible. The presentations showed to us the improving maturity in ontology integration, KGs and SPARQL use. Thanks to speakers.
[12:44] Gary BC: @Ravi  I think that ENVO was updated 2 days ago.


[13:11] Raymond Lee: Thanks!
[12:45] DOS: Great to be able to point potential users to this so they can tell if an ontology they want to use is active.
 
[12:45] DOS: Also great to see some super-editors getting credit.
 
[12:44] Nico Matentzoglu: Just to make it clear: Charlie’s view on “trust” is his own :P not the OBO foundry view!
 
[12:45] Nico Matentzoglu: (On a personal level I agree with much of it)
 
[12:46] Nico Matentzoglu: Anita you can start sharing
 
[12:46] Allen Baron: How is the OBO community health score calculated?
 
[12:46] Asiyah: Some experts have significant technical barriers to use GitHub. The Geeks here should think of a way to help them!
 
Reply by Nico: I think sending people to special training is key. Organisations use tools like JIRA - GitHub is not too different then these. I would start by not calling it Geeky - I would think that using project management tools is pretty much a must in the modern era, in GitHub is not much different. I would recommend organising training in your organisations to raise awareness!
 
[12:47] Allen Baron: Nice presentation Charlie.
 
[12:48] Nico Matentzoglu: Instruction: https://oboacademy.github.io/obook/howto/deploy-custom-obo-dashboard/
 
Example custom dashboard: https://monarch-initiative.github.io/monarch-ontology-dashboard/dashboard/index.html
 
[12:50] Nico Matentzoglu: https://github.com/OBOFoundry/dashboard-template
 
[12:48] RaviSharma: Gary thanks for reply but I guess it was an old screenshot
 
[12:48] Gary BC: Trust is often discussed in terms of factors like Transparency of scope, goals, users, policies and capabilities as well as Responsibility who is responsible & what are steward standards?
 
[12:48] Charlie Hoyt: Apologies for the mix-up between CL and CLO. I'm a big fan of both resources!
 
[12:49] Alexander Diehl: You are forgiven!
 
[12:50] Nico Matentzoglu: https://github.com/OBOFoundry/dashboard-template
 
[12:51] Charlie Hoyt: > DOS: Also great to see some super-editors getting credit.
 
It's true that super-editors are the total backbone of OBO, but I also consider that these people are the ones whose time is most thin. It's not often you can get a Chris Mungall reply on GitHub
 
[12:52] Charlie Hoyt: @allen the community score code is implemented here: https://github.com/cthoyt/obo-community-health/blob/a2cf266cc6d0c432d719158cb658a79d9fb8a4de/build.py#L210-L290, it's not the documented in the nicest way like the scores on the OBO Dashboard. definitely a place for improvement
 
[12:53] Charlie Hoyt: @nico we should externalize the schema that Anita is talking about now since it's used in several places (OBO Foundry repo, obo dashboard, also to some extent OLS)
 
[13:02] Anita Caron: https://anitacaron.github.io/ont-summit2023/
 
[13:02] Charlie Hoyt: Thanks James!
 
[13:03] csbjohnson: Thank you!
 
[13:03] RaviSharma: thanks, it was great deeper dive in OBO efforts.


== Resources ==
== Resources ==
* [https://bit.ly/41wx6LZ Video Recording]
* [https://bit.ly/3XQEGxJ Session Video Recording]
* [https://oboacademy.github.io/obook/tutorial/custom-qc/ Tutorial: How to add custom quality checks with ODK]


== Previous Meetings ==
== Previous Meetings ==
{{#ask: [[Category:OntologySummit2023]] [[Category:Icom_conf_Conference]] [[<<ConferenceCall_2023_02_22]]
{{#ask: [[Category:OntologySummit2023]] [[Category:Icom_conf_Conference]] [[<<ConferenceCall_2023_02_15]]
         |?|?Session|mainlabel=-|order=desc|limit=3}}
         |?|?Session|mainlabel=-|order=desc|limit=3}}
== Next Meetings ==
== Next Meetings ==
{{#ask: [[Category:OntologySummit2023]] [[Category:Icom_conf_Conference]] [[>>ConferenceCall_2023_02_22]]
{{#ask: [[Category:OntologySummit2023]] [[Category:Icom_conf_Conference]] [[>>ConferenceCall_2023_02_15]]
         |?|?Session|mainlabel=-|order=asc|limit=3}}
         |?|?Session|mainlabel=-|order=asc|limit=3}}


Revision as of 16:36, 8 March 2023

Session OBO Dashboards
Duration 1 hour
Date/Time 15 Feb 2023 17:00 GMT
9:00am PST/12:00pm EST
5:00pm GMT/6:00pm CST
Convener Gary Berg-Cross

Ontology Summit 2023 OBO Dashboards

Helping scientific researchers make better use of ontologies

Agenda

Conference Call Information

  • Date: Wednesday, 15 Feb 2023
  • Start Time: 9:00am PST / 12:00pm EST / 6:00pm CST / 5:00pm GMT / 1700 UTC
  • Expected Call Duration: 1 hour
  • Video Conference URL
    • Conference ID: 837 8041 8377
    • Passcode: 323309
  • Chat Room

The unabbreviated URLs are:

Attendees

Discussion

[11:57] RaviSharma: welcome everyone

[12:06] James Overton: Here's a link to the slides: https://docs.google.com/presentation/d/1oKxBzSCZGuFlIhw6jAXw00xgEGs7KgmaVR54NEdPprw/edit#slide=id.g20803e73efb_0_85

[12:09] Charlie Hoyt: not just prefixes but also CURIEs and IRIs

[12:11] RaviSharma: James and Nico - shared design patterns - are these used from a design repository so when people develop ontologies, they can use the design templates?

[12:14] James Overton: Ravi: Many OBO projects use their own templates and patterns, but we are only beginning to use shared patterns. This is a key part of the COB effort.

[12:18] Charlie Hoyt: https://dashboard.obofoundry.org/

[12:18] Charlie Hoyt: actual dashboard: obofoundry

[12:18] Charlie Hoyt: https://dashboard.obofoundry.org/dashboard/index.html

[12:25] RaviSharma: I found a neat cross reference as to which other ontologies use a particular ontology that you are referencing.

[12:25] DOS: Very granular cell ontologies may define classes using reference data rather than textual definitions. It can therefore be impossible to fulfill the unique text def requirement. At best one can add a text definition that described the general class => non-uniqueness. Because of this, the most detailed cell type ontology on the Foundry - FBbt - fails this test. Would it be possible to modify the test to allow it to be fulfilled by links to reference data?

[12:26] RaviSharma: How do you determine content accuracy by engaging the experts like doctors or nurses before you determine its readiness for practicing users operational maturity!

[12:27] Charlie Hoyt: i am not familiar with the mondo custom OBO dashboard! This is so cool! For sure we need more strict requirements than what is currently in OBO Foundry

[12:30] James Overton: DOS: Good point. The automated check for textual definitions is more strict than then principle, which says "most" terms should be defined. <https://obofoundry.org/principles/fp-006-textual-definitions.html>, we can change the automated check, but we need to make a decision about whether to err on the side of strictness or leniency.

[12:30] James Overton: The principles were not written with automated checks in mind, and some are harder to automate than others.

[12:33] DOS: Will promotion to the top tier require passing all tests, or will there be some attempt to order based on how many tests are failing?

[12:34] James Overton: My opinion is that better dashboard score should rank higher, but there's no decision yet.

[12:35] James Overton: OQUAT: https://cthoyt.github.io/oquat

[12:35] Nico Matentzoglu: Presentation link: https://docs.google.com/presentation/d/1oKxBzSCZGuFlIhw6jAXw00xgEGs7KgmaVR54NEdPprw/edit#slide=id.g1dcecf06728_0_7

[12:37] DOS: @James -I'd like to explore discuss how we might extend the principle to allow for a combination of free text def + formalised reference data links to be allowed. Without this, I feel like FBbt is being penalised for being so detailed - where less detailed and so less useful ontology would pass.

[12:38] Nico Matentzoglu: CL is the cell ontology, CLO is the cell line ontology

[12:39] Alexander Diehl: Jonathan Bard, one of the originators of the Cell Ontology, in case anyone is curious (JB:JB)

[12:39] James Overton: DOS: I agree in general. I work on MHC Restriction Ontology (MRO) which is mostly complexes of proteins, where the logical definition says everything important. We could auto-generate textual definitions, but would that really MRO better? So I would like to see OBO refine the textual definition check.

[12:40] RaviSharma: So how did you find resolution of prefix issues?

[12:40] James Overton: https://github.com/cthoyt/obo-community-health

[12:41] James Overton: ^^ I would like to see OBO refine both the textual definition principle and the automated check.

[12:42] Nicole Vasilevsky: For the OBO Community Health, is this up to date? I pushed to Mondo yesterday and it says the last push was in September

[12:42] RaviSharma: I am surprised that Envo is not being updated since August last year, does that mean that ENVO is stabilized or that development is slow?

[12:43] James Overton: Nicole: I see "2023-02-15" as the update date for MONDO.

[12:43] DOS: I love the Community Health dashboard.

[12:43] Nicole Vasilevsky: Oh, I see it was probably an old screenshot! Ignore me

[12:44] RaviSharma: Is quality score or effort a metadata?

[12:44] Gary BC: @Ravi I think that ENVO was updated 2 days ago.

[12:45] DOS: Great to be able to point potential users to this so they can tell if an ontology they want to use is active.

[12:45] DOS: Also great to see some super-editors getting credit.

[12:44] Nico Matentzoglu: Just to make it clear: Charlie’s view on “trust” is his own :P not the OBO foundry view!

[12:45] Nico Matentzoglu: (On a personal level I agree with much of it)

[12:46] Nico Matentzoglu: Anita you can start sharing

[12:46] Allen Baron: How is the OBO community health score calculated?

[12:46] Asiyah: Some experts have significant technical barriers to use GitHub. The Geeks here should think of a way to help them!

Reply by Nico: I think sending people to special training is key. Organisations use tools like JIRA - GitHub is not too different then these. I would start by not calling it Geeky - I would think that using project management tools is pretty much a must in the modern era, in GitHub is not much different. I would recommend organising training in your organisations to raise awareness!

[12:47] Allen Baron: Nice presentation Charlie.

[12:48] Nico Matentzoglu: Instruction: https://oboacademy.github.io/obook/howto/deploy-custom-obo-dashboard/

Example custom dashboard: https://monarch-initiative.github.io/monarch-ontology-dashboard/dashboard/index.html

[12:50] Nico Matentzoglu: https://github.com/OBOFoundry/dashboard-template

[12:48] RaviSharma: Gary thanks for reply but I guess it was an old screenshot

[12:48] Gary BC: Trust is often discussed in terms of factors like Transparency of scope, goals, users, policies and capabilities as well as Responsibility who is responsible & what are steward standards?

[12:48] Charlie Hoyt: Apologies for the mix-up between CL and CLO. I'm a big fan of both resources!

[12:49] Alexander Diehl: You are forgiven!

[12:50] Nico Matentzoglu: https://github.com/OBOFoundry/dashboard-template

[12:51] Charlie Hoyt: > DOS: Also great to see some super-editors getting credit.

It's true that super-editors are the total backbone of OBO, but I also consider that these people are the ones whose time is most thin. It's not often you can get a Chris Mungall reply on GitHub

[12:52] Charlie Hoyt: @allen the community score code is implemented here: https://github.com/cthoyt/obo-community-health/blob/a2cf266cc6d0c432d719158cb658a79d9fb8a4de/build.py#L210-L290, it's not the documented in the nicest way like the scores on the OBO Dashboard. definitely a place for improvement

[12:53] Charlie Hoyt: @nico we should externalize the schema that Anita is talking about now since it's used in several places (OBO Foundry repo, obo dashboard, also to some extent OLS)

[13:02] Anita Caron: https://anitacaron.github.io/ont-summit2023/

[13:02] Charlie Hoyt: Thanks James!

[13:03] csbjohnson: Thank you!

[13:03] RaviSharma: thanks, it was great deeper dive in OBO efforts.

Resources

Previous Meetings

 Session
ConferenceCall 2023 02 08ODK
ConferenceCall 2023 02 01ROBOT
ConferenceCall 2023 01 25COB
... further results

Next Meetings

 Session
ConferenceCall 2023 02 22Ubergraph
ConferenceCall 2023 03 01Panel
ConferenceCall 2023 03 08Modules and Patterns
... further results
Retrieved from "https://ontologforum.com/index.php?title=ConferenceCall_2023_02_22&oldid=4385"