| At line 77 added 1 line. |
| + |
| Lines 94-96 were replaced by lines 95-98 |
| - IX. Concept Merge Tool |
| - • Potential users: Ecologists who are conducting meta-analyses. |
| - • Functionality: Merges concepts that are similar so that t ecological information can be pooled – this is actually the main functionality that ecologists need: what do the names mean, and is it admissible to pool the information pertaining to multiple names/concepts. |
| + |
| + !! IX. Concept Merge Tool |
| + * __Potential users:__ Ecologists who are conducting meta-analyses. |
| + * __Functionality:__ Merges concepts that are similar so that ecological information can be pooled – this is actually the main functionality that ecologists need: what do the names mean?, and is it admissible to pool the information pertaining to multiple names/concepts? |
| Removed lines 104-111 |
| - X. Map-to-TCS Tool |
| - • Potential users: Taxonomic concepts providers who understand and wish to document the relations of objects in their preferred database to those represented in the TCS. |
| - • Functionality: Assists in understanding the object relationships (what are concepts?, etc.) according to different database structures. |
| - • Use Cases: None specifically. |
| - • Integration: Not clear, is sufficiently independent at this point. |
| - • Design needs: → Trevor Paterson, MapForce… |
| - • Further details: See above; also this Tool could eventually plug-in to Tool II. |
| - • Priority/development: Is in a sense already underway at Napier, the work started when Jessie and Robert tried to understand how other databases represent concepts; now this Tool would assist in storing and visualization that information. |
| At line 112 added 10 lines. |
| + !! X. Map-to-TCS Tool |
| + * __Potential users:__ Taxonomic concepts providers who understand and wish to document the relations of objects in their preferred database to those represented in the TCS. |
| + * __Functionality:__ Assists in understanding the object relationships ("what are concepts?", etc.) according to different database structures. |
| + * __Use Cases:__ None specifically (but see below). |
| + * __Integration:__ Not clear, is sufficiently independent at this point. |
| + * __Design needs:__ → Trevor Paterson, MapForce… |
| + * __Further details:__ See above; also: this Tool could eventually plug-in to Tool II. |
| + * __Priority/development:__ Is in a sense already underway at Napier, the work started when Jessie and Robert tried to understand how other databases represent concepts; now this Tool would assist in storing and visualizing that information. |
| + |
| + ---- |
| Line 114 was replaced by line 118 |
| - Next steps. |
| + ! Next Steps |
| Lines 116-117 were replaced by lines 120-121 |
| - 1. Post a Wiki version + a Word document, and advertise to SEEK Taxon |
| - 2. Franz, Liu, and Peet will continue scoping Tools II, III and V; starting with Tool III in particular. |
| + * Post a Wiki version + a Word document, and advertise to SEEK Taxon. |
| + * Franz, Liu, and Peet will continue scoping Tools II, III and V; starting with Tool III in particular. |
