[seqfan] Re: 23 sequences (+ warning)

Charles Greathouse charles.greathouse at case.edu
Sun Feb 10 22:05:04 CET 2013


There are two scenarios here with multiple edits before a sequence is
approved.
1. Person A begins to edit a sequence.
2. Person A submits the edit.
3. Person B begins to edit a sequence.
4. Person B submits the edit.
5. An EiC approves the sequence.
This one doesn't cause problems -- person B sees person A's edits, even
though they haven't been approved.

The second scenario:
1. Person A begins to edit a sequence.
2. Person B begins to edit a sequence.
3. Person A submits the edit.
4. Person B submits the edit.
5. An EiC approves the sequence.

This one could be a problem, since both people were working off the same
copy of the sequence but changed it differently. But fortunately Russ did a
good job handling these kinds of conflicts. If different sections were
edited, both changes go through normally -- neither person even needs to be
aware of the other. If they edit the same sections, the second person
editing gets an edit conflict notice that shows what the other person
changed in the meantime. The second person can then integrate the changes
as they see fit (both versions are presented).


Charles Greathouse
Analyst/Programmer
Case Western Reserve University


On Sun, Feb 10, 2013 at 12:12 PM, L. Edson Jeffery <lejeffery2 at gmail.com>wrote:

> I always check the history before editing. However, multiple users can be
> editing the same sequence at the same time: maybe the system could keep
> track of this and give some warning.
>
> Ed Jeffery
>
> >please give notice of any seq's you are taking on to avoid double edits
> >As long as edits are not 'officialised' by an 'editor-in-Chief', the
> >non-ascii signs will still be there for someone else to re-edit!
>
> _______________________________________________
>
> Seqfan Mailing list - http://list.seqfan.eu/
>


More information about the SeqFan mailing list