Project

General

Profile

Taxonomic Editor » History » Version 83

Niels Hoffmann, 07/13/2010 05:23 PM

1 82 Niels Hoffmann
[|{{>toc}}
2 1
3 82 Niels Hoffmann
]
4 1
5
6
7 5 Markus Döring
# Taxonomic Editor
8 1
9 77 Niels Hoffmann
The Taxonomic Editor is the desktop application used to edit data stored in a [[CommunityStore]]. It edits data in either 
10 1
11
1. a remote source, or 
12 77 Niels Hoffmann
13 80 Niels Hoffmann
1. a local data source embedded in the application.
14 1
15
16 80 Niels Hoffmann
![](EDITTaxonomicEditor_Version2.2.1.jpg)
17 1
18 80 Niels Hoffmann
----
19 1
20 80 Niels Hoffmann
21
22
## Download
23
24
25 81 Niels Hoffmann
| Current stable release | http://wp5.e-taxonomy.eu/download/taxeditor/stable/ |
26
| All versions | http://wp5.e-taxonomy.eu/download/taxeditor/ |
27 80 Niels Hoffmann
28 81 Niels Hoffmann
Installation instructions may be found at the product website: http://wp5.e-taxonomy.eu/cdm-setups/?q=node/3
29 80 Niels Hoffmann
30
31
32
----
33 35 Pepe Ciardelli
34
35 61 Pepe Ciardelli
## Overview
36 17 Pepe Ciardelli
37 66 Pepe Ciardelli
The goal of the Taxonomic Editor is to provide a next-generation tool that moves beyond the form-based data entry of web-based tools like the [Berlin Model Web Editor](http://www.bgbm.org/biodivinf/docs/bgbm-model/software.htm.)
38 1
39
40 61 Pepe Ciardelli
The core workflow is: 
41 1
42 61 Pepe Ciardelli
1. the user enters data in a freetext area (the middle area in the above screenshot); 
43 1
44 61 Pepe Ciardelli
1. the data is parsed on-the-fly, i.e. as it is entered;
45 1
46 61 Pepe Ciardelli
1. the user reviews whether the data has been parsed correctly in the structured data area on the right.
47 1
48
49 61 Pepe Ciardelli
Thus, the Editor offers the familiarity and user-friendliness of word processing programs, while keeping the CDM data structure visible at all times.
50 1
51 44 Pepe Ciardelli
52 61 Pepe Ciardelli
A second defining feature of the Editor is that the user will be allowed to enter erroneous data. Rather than enforcing data integrity upon input, the user will be warned when any rules have been broken, using the red and yellow squiggly underlines used by word processing software to show grammatical and spelling errors. When the mouse hovers over data that has been marked as flawed, the error will be explained, along with possible corrections.
53 44 Pepe Ciardelli
54
55 61 Pepe Ciardelli
Good interface design keeps to a minimum the number of new movements or gestures a user must learn in order to use a new piece of software; these should then be applied in as many different contexts as possible, so that the software feels intuitive. Thus, in every part of the Editor, the left mouse button will be used to drag and drop data elements, for example, to drag a name from the search results list onto a synonym list; and the right mouse button will open up a context menu containing a list of possible commands that can be performed on the data element the mouse is pointing at.
56 1
57
58 61 Pepe Ciardelli
Finally, note that the Editor is taxon-centric. Taxa are chosen from the left pane - from the taxonomic tree, recently viewed taxa, search, or favorites - and opened in the main editor area. At the bottom of each taxon editor area are tabs for individual taxon data categories, i.e. "Name", "Features", "Concepts", "Geography", etc.
59 1
60
61 64 Pepe Ciardelli
For a more in-depth discussion, please see the current draft of the [Editor Design Document](http://dev.e-taxonomy.eu/trac/attachment/wiki/TaxonomicEditor/EDIT%20Taxonomic%20Editor%20Design%200.2.pdf.)
62 1
63
64
65 61 Pepe Ciardelli
## Technology
66 1
67 61 Pepe Ciardelli
The Editor will be built using the [Eclipse Rich Client Platform](http://www.eclipse.org/eclipse/platform-ui/) (RCP). This is a collection of Java libraries used to build the Eclipse Java development environment, essentially a word processing tool for Java developers. In essence, we will take the code used to program Eclipse and adapt it to the Editor. The RCP libraries include basic application functionality such as window management and operating system integration, as well as word processing features like autocomplete and syntax and error highlighting.
68 44 Pepe Ciardelli
69 61 Pepe Ciardelli
70
71
## Use Cases / Requirements
72
73
A list of Taxonomic Editor functionality, based on the Berlin Model Web Editor, can be found under [[EditorRequirements]].
74
75
76 63 Pepe Ciardelli
Use cases for development of additional Editor modules can be found under [[PlatformUseCases]].
77 65 Pepe Ciardelli
78
79
A [[ConceptWorkshop]] was held in Berlin February 21-22, 2008 to discuss the design of the Editor, with a focus on the management of taxonomic concepts. The results of the workshop can be found [here](http://dev.e-taxonomy.eu/trac/attachment/wiki/ConceptWorkshop/2008_02_21-Berlin-ConceptWorkshop_Final.pdf.)
80 70 Andreas Müller
81
82
83
## Bug & Enhancement Reports
84
85 72 Andreas Müller
_registered users only_
86
87 70 Andreas Müller
88 73 Andreas Müller
To report bugs and submit enhancement requests please add a new ticket by using the following links for  
89
90 74 Andreas Müller
* [bugs](http://dev.e-taxonomy.eu/trac/newticket?component=taxeditor&milestone=TaxEditor+Release+2.0)
91 73 Andreas Müller
92
* [enhancements](http://dev.e-taxonomy.eu/trac/newticket?component=taxeditor&milestone=TaxEditor+Release+1.0)
93
94 83 Niels Hoffmann
You may use the prefilled ticket properties except for the priority property.
95
96
97
When filing bugs please answer these questions:
98
99
~~~
100
What steps will reproduce the problem?
101
1. 
102
2. 
103
3. 
104
105
What is the expected output? What do you see instead?
106
107
108
What version of the product are you using? On what operating system?
109
110
111
Please provide any additional information below.
112
~~~
113 70 Andreas Müller
114 71 Andreas Müller
115
Reported bugs you find at
116
117
* http://dev.e-taxonomy.eu/trac/report/30 (bugs) 
118
119
* http://dev.e-taxonomy.eu/trac/report/32 (enhancements)