Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[bioontology-support] feature request: Start term

Alan Ruttenberg alanruttenberg at gmail.com
Tue Feb 3 17:53:46 PST 2009


2009/2/3 Natasha Noy <noy at stanford.edu>:
> Hi Alan,
>
> Yes, I completely agree that having it land on the obsolete class is bad.
>
> I think having that "main class" as part of the metadata that the ontology author specifies would make a lot of sense.
>
> For a short-term solution though, how about we just look through all the roots and if we find one with "obsolete" or "deprecated" in its name, we move it to the bottom?

We could also add an annotation property to the entity in question:
bioportal_hint: main_class
probably same amount of code needed and gives better control.
-Alan


>
> Natasha
>
>
> On Feb 3, 2009, at 12:37 AM, Alan Ruttenberg wrote:
>
>> On Mon, Feb 2, 2009 at 7:46 PM, Natasha Noy <noy at stanford.edu> wrote:
>>>
>>> Hi Alan,
>>>
>>> You can also currently specify, for example:
>>> http://bioportal.bioontology.org/visualize/39317/IAO_0000018'
>>>
>>> So, you can send a user there.
>>>
>>> Is that what you had in mind?
>>
>> No. I was concerned with what happens when someone clicks the
>> "explore" link from the OBI detail page
>> http://bioportal.bioontology.org/ontologies/39317
>>
>>>
>>>>> For OBI, for instance, I might like to specify that I want the class
>>>>> Material Entity opened up in the hierarchical view, and the class
>>>>> agarose gel to be visible in the display view.
>>>
>>> Well, the hierarchical and the details view are synchronized. Are you
>>> suggesting they shouldn't be?
>>
>> No. Just that both things be visible - some opening up of the
>> hierarchical view and some particular detail view within that.
>>
>> Regards,
>> Alan
>>
>>>
>>> Natasha
>>>
>
>



More information about the bioontology-support mailing list