searches of MeSH trees need to have parent nodes added as context information for users

GoogleCodeExporter commented 9 years ago

MeSH "trees" are  not trees, they're graphs, in the sense that multiple
nodes may exist with the same descriptive text (eg: 'blood', 'blood
cells'), but with different positions in the tree, and with different MeSH Ids.

In the UI, this manifests as duplicate names in various places. the current
solution is to add parent node info as a method of disambiguation.

so, instead of:

* Blood
* Blood

the user should see:

* Blood < Hemic and Immune Systems < Anatomy
* Blood < Body Fluids < Fluids and Secretions < Anatomy

Original issue reported on code.google.com by glycosl...@googlemail.com on 5 Jun 2009 at 10:53

GoogleCodeExporter commented 9 years ago

Original comment by glycosl...@googlemail.com on 5 Jun 2009 at 11:32

Added labels: Aspect-Science, Aspect-UI, Core-BiologicalContext
Removed labels: Component-UI

GoogleCodeExporter commented 9 years ago

Original comment by glycosl...@googlemail.com on 5 Jun 2009 at 12:07

Added labels: Aspect-Usability, Module-BiologicalContext
Removed labels: Aspect-Science, Aspect-UI, Core-BiologicalContext

GoogleCodeExporter commented 9 years ago

Issue 2 has been merged into this issue.

Original comment by glycosl...@googlemail.com on 5 Jun 2009 at 12:33

GoogleCodeExporter commented 9 years ago

Fixed in rev 1387

Original comment by hir...@gmail.com on 2 Jul 2009 at 10:56

Changed state: Fixed

brleeflang / eurocarb

searches of MeSH trees need to have parent nodes added as context information for users #8