VibrantIndexInterface » History » Version 5
Lorna Morris, 05/31/2012 05:51 PM
1 | 1 | Lorna Morris | |
---|---|---|---|
2 | 2 | Lorna Morris | # Skype Meeting, ViBRANT Index Issues, (Anton, Andreas M., Andreas K., Lorna) 31.5.2012 |
3 | 1 | Lorna Morris | |
4 | |||
5 | |||
6 | 4 | Lorna Morris | |
7 | 1 | Lorna Morris | ## How do we display links for Misapplied names in the VIBRANT search index? |
8 | |||
9 | |||
10 | * A distinct name can have more than one status (e.g. Misapplied name, Accepted Taxon) in a single multi-classification |
||
11 | |||
12 | |||
13 | 3 | Lorna Morris | source. Currently the VIBRANT index doesn't indicate which Taxa the name is misapplied for. Thus status should be applied to |
14 | 1 | Lorna Morris | |
15 | |||
16 | 3 | Lorna Morris | a Taxon Relationship rather than the Taxon itself. |
17 | 1 | Lorna Morris | |
18 | |||
19 | * Longer-term solution: Discuss re-modelling the CDM. Misapplied name is the status of a Taxon Relationship not a Taxon. |
||
20 | |||
21 | |||
22 | Misapplied names are currently handled the same as Accepted Taxa in the CDM. They should be handled differently. Chagning the |
||
23 | |||
24 | |||
25 | model will impact the taxonomic Editor and other software. Updating the model may be useful for the Redlist project. |
||
26 | |||
27 | |||
28 | * Shorter-term-solution: Change the interface to direct the user to the available information. If we have a Taxon without a |
||
29 | |||
30 | |||
31 | classification id then we could report the source as 'Misapplied name'. However there could be serveral reasons why the Taxon |
||
32 | |||
33 | |||
34 | is not attached to a classification so 'Other status' may be more appropriate. Another solution is to show concept |
||
35 | |||
36 | |||
37 | relationships in the interface, therefore even is we keep status 'Accepted' for Misapplied names it makes the status clearer |
||
38 | |||
39 | |||
40 | (see below). |
||
41 | |||
42 | |||
43 | |||
44 | 5 | Lorna Morris | |
45 | 1 | Lorna Morris | ## Should we show Concept Relationships in the user interface? |
46 | 5 | Lorna Morris | |
47 | 1 | Lorna Morris | |
48 | |||
49 | * IOPI shows Concept Relationships (Misapplied Names are shown as Accepted for a given Concept). |
||
50 | |||
51 | |||
52 | * The service method we use to extract the data from the CDM returns all Taxon relationships for a given Taxon, therefore we |
||
53 | |||
54 | |||
55 | could display this information in the user interface. |
||
56 | |||
57 | |||
58 | Solution: Display multiple URLs (e.g. to the "Accepted Taxa" of a Misapplied Name) for cases where the Taxon has multiple |
||
59 | |||
60 | |||
61 | Concept relationships. |
||
62 | |||
63 | |||
64 | |||
65 | ## What is meant by Source and what should we display in the Interface |
||
66 | |||
67 | |||
68 | * Currently the VIBRANT index interface shows the sec reference as source. We agree that the sec reference should always be |
||
69 | |||
70 | |||
71 | displayed (and labeled such). A Taxon concept can have multiple sources. Currently in the CDM a Taxon name can have set of |
||
72 | |||
73 | |||
74 | sources. For the index we want to display the last source in our interface but distinguishing the last source in the CDM is |
||
75 | |||
76 | |||
77 | currently not possible. |
||
78 | |||
79 | |||
80 | * Short-term solution: The import gives a title for the source e.g. Euro+Med (for the current data remove all sources but the |
||
81 | |||
82 | |||
83 | last and show it) |
||
84 | |||
85 | |||
86 | * Longer-term solution: Re-model the CDM. Change the set of sources to a sequence of sources. The problem is that we don't |
||
87 | |||
88 | |||
89 | always have this information. And further complexity can arise when 2 sources are merged. A simplier solution is to just add |
||
90 | |||
91 | |||
92 | a flag 'last source' when we don't know the sequence. |
||
93 | |||
94 | |||
95 | |||
96 | |||
97 | ## What should we display in the the link to each source |
||
98 | |||
99 | |||
100 | * Andreas K suggests we map URL's to human readable strings. URL's don't always have a human readable component so we cna't |
||
101 | |||
102 | |||
103 | always parse this, but sources do ahve a title so we can display this for the link. In most cases there is only one source. |
||
104 | |||
105 | |||
106 | In cases where there are multiple sources we should show a list of links to sources (labelled as either 'Source history' or |
||
107 | |||
108 | |||
109 | 'Contributing Sources'). |
||
110 | |||
111 | |||
112 | * Longer-term solution: Re-model the CDM. Currently the URL is added to the Taxon. We should add the URL to the Source. |
||
113 | |||
114 | |||
115 | |||
116 | |||
117 | ## What should we display for Status |
||
118 | |||
119 | |||
120 | * Currently we are using Taxon, Synonym for the status (the class name from the CDM). Should Taxon be chnaged to 'Accepted |
||
121 | |||
122 | |||
123 | Taxon'. We've decided to use "Accepted" as in PESI. In the cases where the name is Accepted and Misapplied in a single |
||
124 | |||
125 | |||
126 | source, we will also provide this information as described above. |