Comment by chrismungall

Back to stories Open in a window
Comment

Comment by chrismungall

I am part of OBO (and GO, which has also been mentioned here a few times). It's nice to see the discussion here, lots of good comments, including the critical ones!

I'm going to address a few themes that have emerged, hopefully this is informative and can generate useful discussion.

Yes, the OBO site is not really very biologist friendly (or really anyone-friendly). It is more geared towards ontology developers, biocurators, and the kind of people who might build tools biologists would use. I would recommend portals such as the OLS (https://www.ebi.ac.uk/ols) for biologists -- but even this site tends to be used by bioinformatics-savvy folks. Domain scientists and users often use ontologies indirectly. For example, the Human Phenotype Ontology is used in many clinical settings for entering patient phenotypes, and subsequently in diagnosis (making use of the logical structure of the ontology). The cell ontology is central to many single-cell seq efforts. And of course the GO is ubiquitous in interpretation of experimental data via enrichment analyses.

One thing we have tried hard to do with the OBO site is ensure we have up to date metadata for all registered ontologies -- including GitHub trackers. So if you have comments on any particular ontology then engaging the developers via their issue tracker is strongly encouraged. And OBO itself has a tracker, as well as a mail list anyone can join.

One thing we have not done a great job of is in giving any kind of order to the many ontologies now listed. It can be overwhelming to someone not familiar with the field. Which ontology should I use ?(or avoid?) Which ontologies integrate well together, and which ones have duplication or incompatibilities? We have a number of new developments in the pipeline that should improve the situation here through the development of a new mid-upper level ontology called OBO Core (https://github.com/OBOFoundry/Experimental-OBO-Core/). We're also encouraging all ontology developers to use standard tooling and best practice which will make interoperation easier (https://github.com/INCATools/ontology-development-kit).

A few people were asking for explainers on ontologies and bio-ontologies in particular. We have a few on our resources page, which is linked from the main site: https://github.com/OBOFoundry/OBOFoundry.github.io/blob/mast... (pull requests welcome!)

Finally, the OBO project itself receives only a tiny amount of short term funding, and most of the ontologies that comprise it have little or no direct funding (exceptions being widely used ones such as GO). A lot of work is community effort. Not saying that to deflect any criticism - constructive criticism is good! Just to provide an explanation of which some things are the way they are.

Replies chrismungall · 2020-01-22
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or a story row's Open in new reader window button to compare articles. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page and Open in a window are one-off actions that do not change your saved default. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Pins, hidden stories, filters and layout are kept in this browser only.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.