elimination of identical biological context entries

[GoogleCodeExporter]

Describe your suggestion:
The biological context as such is a good and important idea, but the way
the correlation between glycan structures and biol. cont. is currently
implemented needs to be rethought. At the moment it seems that a new
biological context is created for each glycan structure that is entered,
regardless if an identical biological context already exists or not. This
causes two problems: On the one hand the list of biological contexts for a
certain glycan can become very long (see
http://www.ebi.ac.uk/eurocarb/show_glycan.action?glycanSequenceId=149 - it
takes rather long to load the page and depending on browser and OS the page
is not even displayed correctly any more) and finding a certain biol. cont.
in the list is difficult, and on the other hand the details view of the
biol. cont. holds only one glycan structure each. So it is also difficult
to find all structures that are found within one specific biological
context; and for someone who is not familar with this issue it might look
like there is only one structure found in a certain context, although there
might be many other structures in identical contexts present in the database.
Therefore, identical biological contexts entries should be merged.

For which pages (URLs/addresses) and/or features are you making this
suggestion?
All features/pages that make use of biological context.

How would this suggestion help you?
It would make the database more user-friendly.

Original issue reported on code.google.com by thomas.l...@googlemail.com on 3 Sep 2009 at 9:49

[GoogleCodeExporter]

I have one possible solution to this problem now working.  We will need to 
discuss
this though; as I think the biological context relationships need changing a 
little
bit more than I already have.

David

Original comment by Damerel...@googlemail.com on 19 Nov 2009 at 7:18

[GoogleCodeExporter]

There's now a "complete" fix for this issue within the repository as well as 
script 
within revision 1817 which should be able to update the schema within a live 
database 
which contains data within it.

Original comment by Damerel...@googlemail.com on 3 Dec 2009 at 3:18

• Changed state: Accepted
• Added labels: Type-Bug, Priority-Critical
• Removed labels: Type-Enhancement, Priority-Medium