Add multiple editor (owners) tag to exported gff3/json about apollo

[nathandunn]

Okay, I’ve scheduled it for the next release (the one you will be testing).

Nathan

On Sep 26, 2014, at 8:07 AM, childers [email protected] wrote:

Currently the exported gff3 contains a field for owner, which is the user that created that model.
Our usage tracking would be greatly enhanced if the exported gff3 would also include an 'editor' tag, which consists of a list of all users that modified the model.

—
Reply to this email directly or view it on GitHub.

[monicacecilia]

Hey Chris,
How often do you come about more than one user editing the same model?

~m.

On Fri, Sep 26, 2014 at 4:07 PM, childers [email protected] wrote:

Currently the exported gff3 contains a field for owner, which is the user
that created that model.
Our usage tracking would be greatly enhanced if the exported gff3 would
also include an 'editor' tag, which consists of a list of all users that
modified the model.

—
Reply to this email directly or view it on GitHub
#29.

[childers]

Hey Moni,

Honestly, I think that scenario is pretty rare, since we have well
organized communities that are coordinating their efforts. Since it is not
straightforward to see this without iterating through all the history
databases and aggregating transactions on a per-feature basis, I'm not
certain how frequently this happens. That is one of the key questions I'd
love to have an easier way to answer!

Another potential application of this would be that an OGS could be loaded
as annotations, then we can track how it is improved by the users.

I really like the bulk load feature, but once it tags everything as
belonging to the account used for loading, subsequent editors are not
listed anywhere.

Best,
Chris

On Sat, Sep 27, 2014 at 9:07 AM, Monica Munoz-Torres <
[email protected]> wrote:

Hey Chris,
How often do you come about more than one user editing the same model?

~m.

On Fri, Sep 26, 2014 at 4:07 PM, childers [email protected]
wrote:

Currently the exported gff3 contains a field for owner, which is the
user
that created that model.
Our usage tracking would be greatly enhanced if the exported gff3 would
also include an 'editor' tag, which consists of a list of all users that
modified the model.

—
Reply to this email directly or view it on GitHub
#29.

—
Reply to this email directly or view it on GitHub
#29 (comment).

[monicacecilia]

Ok. Thanks for the response. I'm glad Nathan is planning to include an 'editor' tag for the next release.
cheers,
~m.

[childers]

Have you ever heard of multiple editors per feature before? You get to
talk to annotators for lots of diverse projects, and I wouldn't be
surprised to hear of iterative/cooperative annotation.

Chris

On Mon, Sep 29, 2014 at 8:40 AM, Monica Munoz-Torres <
[email protected]> wrote:

Ok. Thanks for the response. I'm glad Nathan is planning to include an
'editor' tag for the next release.
cheers,
~m.

—
Reply to this email directly or view it on GitHub
#29 (comment).

[monicacecilia]

No, actually, as useful as that can be I have not heard of multiple editors for a single gene model just yet. Even when I am working with H. Robertson I usually start a different gene model to answer his questions.

[nathandunn]

Currently, there is no support for that. Even if the editor is different than the editor, it is information that is stored exclusively in the session. That being said, I think its a good feature and it makes a lot of sense in the context of storing history. I think its something that should not be too hard to record when we refactor. I'll move the milestone to reflect that.