Menu
▾
▴
Re: [Obi-devel] [Obi-coord] Curator note vs editor note
|
From: James M. <ma...@eb...> - 2009-11-24 20:35:06
|
Agreed, and God knows I don't want to get caught up in meta-trouble, but I
just want to make it easy for everyone to disambiguate instantly. Mainly
me in fact - I'll forget in a month and put it in the wrong property. My
proposal is user note and editor note (synonym curator note).
James
> +1 Chris,
>
> Jie
>
> Chris Stoeckert wrote:
>> Hi James,
>> I certainly agree with the two types of notes and believe there is a
>> consensus for them: something internal to hide; something useful in
>> the way of a comment to include in the release. I don't feel strongly
>> about what we call them.
>>
>> Cheers,
>> Chris
>>
>> On Nov 24, 2009, at 3:14 PM, James Malone wrote:
>>
>>
>>> Hi Chris,
>>>
>>> I was also thinking about this after the call. Even after reading the
>>> definitions it still doesn't make sense to me. It suggests that the
>>> curator is not the editor and vice versa. If I edit the term I am
>>> curating
>>> it/editing it and if I leave a note for another editor/curator I can
>>> leave
>>> it in a editor/curator note. They are one and the same as far as I
>>> see. I
>>> think what we need is a single property for us, call it editor note or
>>> whatever, and a note that is for the users if that is the
>>> intention. The
>>> below definition of editor note as far as I can tell, is exactly the
>>> same
>>> as curator note in meaning, other than the fact it gets hidden which
>>> means
>>> ontologically they are the same (since IAO insists on turning
>>> annotation
>>> properties into classes). I would like to keep this even simpler:
>>>
>>> Editor note (or whatever): an internal note for other editors
>>> (curators)
>>> to be hidden from public.
>>>
>>> User note: a useful not which may comment on definition for example
>>> to aid
>>> users and is included in release.
>>>
>>> What do you think Chris (et al)?
>>>
>>> Cheers,
>>>
>>> James
>>>
>>>
>>>
>>>
>>>
>>>> At yesterday's developer call, the issue of curator notes versus
>>>> editor notes came up. There are internal notes that we don't want the
>>>> outside world to see (like "Alan says there will be problmes, e.g.
>>>> with selection by survival" with OBI_600009 'exposure of material to
>>>> environment') but other notes that would be helpful to readers of the
>>>> ontology (" It could also be added that the reverse transcriptase is
>>>> bearer of a GO:0003964 RNA-directed DNA polymerase activity, which is
>>>> realized in this process."with OBI_0600028 artificially induced
>>>> reverse transcription).
>>>>
>>>> At http://obi-ontology.org/page/OBI_Minimal_metadata:
>>>> It says:
>>>> editor note: An administrative note intended for the editor. It will
>>>> not be included in the publication version of the ontology, so it
>>>> should contain nothing necessary for end users to understand the
>>>> ontology. Editor notes should include the date of edit.
>>>> Cardinality: Each class can have one, or many editor notes
>>>> Implementation: datatype annotation property
>>>>
>>>> Base on todays discussion, I propose the following change:
>>>> curator note: An administrative note intended for the curator of the
>>>> ontology. It will not be included in the publication version of the
>>>> ontology, so it should contain nothing necessary for end users to
>>>> understand the ontology. Curator notes should include the date of
>>>> edit
>>>> (YYYY/MM/DD) and the author.
>>>> Cardinality: Each class can have one, or many curator notes
>>>> Implementation: datatype annotation property
>>>>
>>>> editor note: A note containing points under consideration for further
>>>> term development that will be included in the publication version of
>>>> the ontology. It should contain nothing embarrassing and something
>>>> potentially useful for end users to understand the ontology. Editor
>>>> notes should include the date of edit (YYYY/MM/DD) and the author.
>>>> Cardinality: Each class can have one, or many editor notes
>>>> Implementation: annotation property
>>>>
>>>> Any objections?
>>>> Thanks,
>>>> Chris
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>>>> 30-Day
>>>> trial. Simplify your report design, integration and deployment -
>>>> and focus
>>>> on
>>>> what you do best, core application coding. Discover what's new with
>>>> Crystal Reports now. http://p.sf.net/sfu/bobj-july
>>>> _______________________________________________
>>>> Obi-coord mailing list
>>>> Obi...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/obi-coord
>>>>
>>>>
>>> --
>>> EMBL Outstation - Hinxton,
>>> European Bioinformatics Institute,
>>> Wellcome Trust Genome Campus,
>>> Hinxton,
>>> Cambridge, CB10 1SD,
>>> United Kingdom
>>> Fax: + 44 (0) 1223 492 468
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> 30-Day
>> trial. Simplify your report design, integration and deployment - and
>> focus on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now. http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Obi-devel mailing list
>> Obi...@li...
>> https://lists.sourceforge.net/lists/listinfo/obi-devel
>>
>
--
EMBL Outstation - Hinxton,
European Bioinformatics Institute,
Wellcome Trust Genome Campus,
Hinxton,
Cambridge, CB10 1SD,
United Kingdom
Fax: + 44 (0) 1223 492 468
|
