EDIT Project Management: Issueshttps://dev.e-taxonomy.eu/redmine/https://dev.e-taxonomy.eu/redmine/redmine/favicon.ico?14691914852015-07-06T13:51:42ZEDIT Project Management
Redmine EDIT - bug #5063 (Closed): Fix CoL import (split in parts++)https://dev.e-taxonomy.eu/redmine/issues/50632015-07-06T13:51:42ZAndreas Müller
<p>Currently the import is failing to import the hierarchy. Also performance is very bad, so we may want to improve the import by </p>
<ul>
<li><p>splitting it into parts </p></li>
<li><p>remove auditing and other features which may not be needed for the CoL <a class="issue tracker-5 status-5 priority-10 priority-lowest closed child" title="feature request: Allow removing auditing from imports (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/6880">#6880</a></p></li>
<li><p>also see other open issues like #3210</p></li>
</ul>
<p>Splitting into parts may include</p>
<ul>
<li><p>using database based mapping instead of in-memory mapping </p></li>
<li><p>splitting taxon relationship import into synonym relationship, higher taxon rank relationships and lower taxon rank relationships imports</p></li>
</ul>
EDIT - bug #5040 (Closed): Allow transmission engine webservice to define area levelhttps://dev.e-taxonomy.eu/redmine/issues/50402015-06-26T18:01:59ZAndreas Müller
<p>Currently the namedAreaLevel to be used for transmission engine is hardcoded to TDWGLevel3 in DescriptionListController.doAccumulateDistributions.</p>
<p>For E+M this is not valid as we E+M uses its own vocabulary. We need to make areaLevelUuid a webservice parameter.</p>
<p>See also #3979</p>
EDIT - bug #4944 (Closed): "Protected" indication for references needs to be improvedhttps://dev.e-taxonomy.eu/redmine/issues/49442015-05-28T13:05:52ZAndreas Müller
<p>There are some issues with the orange coloring which indicates that a cache is protected in the reference details view.</p>
<ol>
<li><p>Generally the reference type is never orange though it should whenever a cache is protected</p></li>
<li><p>If the reference cache is protected the "Abbrev cache" and the "Abbrev title" should not be orange as these fields are not primarily made invisible by the protection of the title cache (for discussion see also <a class="issue tracker-4 status-5 priority-16 priority-high10 closed child" title="bug: Abbrev title for person should never be orange (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/4915">#4915</a>)</p></li>
<li><p>If both caches are protected and then one cache is toggled to unprotect only 2-3 fields stay orange. This is inconsistent with the state when you have both caches unprotected on switch to one field being protected. The same protection state should always result in the same state of colored fields. This can easily be reached by having one method that computes the coloring and that is always called when any of the protection states are changing or when a new object is loaded (a similar behavior has been observed for names: <a class="issue tracker-4 status-5 priority-10 priority-lowest closed child" title="bug: Protected caches for taxa and names behave inconsistent (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/3737">#3737</a>)</p></li>
<li><p>Related to the above we may think about different colors for the 3 states "titleCache protected", "abbrevCache protected", "both protected"</p></li>
<li><p>We may think about not having the "Reference Abstract" orange as nobody will expect that the abstract will go into the caches </p></li>
</ol>
<p>The following is a split from <a class="issue tracker-5 status-5 priority-10 priority-lowest closed child" title="feature request: Implement editing for abbreviated title (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/3561">#3561</a>: [DISCUSS] If only Reference Cache or only Abbrev Title Cache are protected how should the other fields be coloured? E.g. should the author be coloured organge? YES because cache 1 is protected, NO because cache 2 is not protected. </p>
<p>closely related to <a class="issue tracker-4 status-5 priority-16 priority-high10 closed child" title="bug: Abbrev title for person should never be orange (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/4915">#4915</a></p>
EDIT - bug #4915 (Closed): Abbrev title for person should never be orangehttps://dev.e-taxonomy.eu/redmine/issues/49152015-05-19T15:00:12ZAndreas Müller
<p>the abbreviated title of a person should never become orange as it is not a cache field. However it sometimes becomes orange.</p>
<p>What I did:</p>
<ul>
<li><p>Open Person or Team Bulk editor</p></li>
<li><p>create new Person (right click New-Author) => the new person is shown with protected white title cache and white abbrev. title</p></li>
<li><p>do any change in title cache => the abbrev. title becomes orange !!</p></li>
</ul>
<p>You may go further and unprotect the title cache => everything becomes white and then protect it and again everything incluging abbrev title becomes orange</p>
<p>related to <a class="issue tracker-4 status-5 priority-13 priority-high13 closed child" title="bug: "Protected" indication for references needs to be improved (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/4944">#4944</a>, for general implementation issues see there.</p>
<p>see also #4912</p>
EDIT - bug #4821 (Closed): Changing order of terms not possiblehttps://dev.e-taxonomy.eu/redmine/issues/48212015-04-24T08:46:42ZAndreas Müller
<p>When trying to change the order of an ordered term vocabulary (e.g. Presence Absence Term) by moving an existing term in between 2 other terms the term is added as a child to the above term instead of just changing the order.</p>
EDIT - feature request #4770 (Closed): Allow convert person to teamhttps://dev.e-taxonomy.eu/redmine/issues/47702015-04-01T02:38:59ZAndreas Müller
<p>see also <a class="issue tracker-5 status-5 priority-10 priority-lowest closed" title="feature request: Allow convert team to person (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/4769">#4769</a></p>
<p>bulk editor implementation: <a class="issue tracker-5 status-5 priority-14 priority-high12 closed" title="feature request: adding convert Team to Person and Person to Team to the bulk editor (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/4908">#4908</a></p>
<p>Open issue:</p>
<ul>
<li><del>if the person.titleCache is not protected and also no atomized data exists the team.titleCache is empty but protected</del></li>
</ul>
EDIT - feature request #4769 (Closed): Allow convert team to personhttps://dev.e-taxonomy.eu/redmine/issues/47692015-04-01T02:38:06ZAndreas Müller
<p>see also <a class="issue tracker-5 status-5 priority-10 priority-lowest closed" title="feature request: Allow convert person to team (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/4770">#4770</a></p>
<p>bulk editor implementation: <a class="issue tracker-5 status-5 priority-14 priority-high12 closed" title="feature request: adding convert Team to Person and Person to Team to the bulk editor (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/4908">#4908</a></p>
EDIT - feature request #4706 (Closed): Create IntextReferencehttps://dev.e-taxonomy.eu/redmine/issues/47062015-03-12T12:12:02ZAndreas Müller
<p>We need the possibility to link to other CDM / external objects from within a text (e.g. a description or an annotation). Currently links are only possible for the whole block, which is often not good enough.</p>
<p>We may want to have a hypertext like possibility to link e.g. </p>
<pre> "lore ipsum <TaxonName id=2 uuid=...>Abies alba Mill.</TaxonName> ipsum lore...
</pre>
<p>One problem to solve is that during deduplication / deleting, these links may become unstable. The according link information needs to be updated or deleted. Also we do not get a ForeignKey constraint violation during delete which prevents us from deleting. </p>
<p>We may create a class which stands for an inline reference. It holds foreign keys to all relevant classes referenced classes (Names, References, Specimen, Agents, ...) and it can be referenced from e.g. LanguageString or Annotation. This way we keep the foreign key information.</p>
<p>The class also holds information about where in the text the information is to be found (not necessarily required as this can be found easily by searching the text).</p>
<p>The IntextReference structure could also be used for linking to external sources via URIs.</p>
<p>Open issues:</p>
<ul>
<li><p>Does the class need to be versionable to allow auditing?</p></li>
<li><p>Do we need to add it to JAXB? Data can be reconstructed using the tag information also</p></li>
</ul>
EDIT - feature request #4639 (Closed): Show quantitative data correctly in Data portal (for Cypru...https://dev.e-taxonomy.eu/redmine/issues/46392015-02-06T15:31:03ZAndreas Müller
<p>In general we need to show quantitative data in the data portal somehow like (a)-b-c-e-(f) for extrema, min, max and average. Also count n, standard deviation etc. need to be shown.</p>
<p>However, for now urgently need to implement correct min and max handling for altitudes in the Cyprus portal. Currently these data are not in the feature tree to avoid showing them incorrectly, but most taxa do have altitude data. </p>
<p>"es gibt keine Specimens mit Höhenangaben. Es geht um kumulative Höhenangaben für fast alle zyprischen Arten. ... die Höhenangaben [wurden] in den Editor eingepflegt (Federführung A. Müller). Dazu gab es mit ihm und Dir schon ausführliche E-Mail-Austausche. Die Anzeige im Portal gebricht noch an marginalen Problemen, vor allem dem, wenn Minimum und Maximum gleich sind, also vor allem bei Küstenarten. Bei diesen sollte also nicht 0-0 m angezeigt werden, sondern nur 0 m o. ä.</p>
<p>" Ralf</p>
<p><em>Gewünsche Anzeige</em>:</p>
<p><strong>Altitudinal range</strong> </p>
<p>25–1050 m (_also bitte nicht mit Binde-, sondern mit Bis-Strich.</p>
<p>Maximum und Minimum also mit kumulierter Literaturangabe._)</p>
<p>siehe auch attachment</p>
<p><em>Zu klären</em>:</p>
<ul>
<li><p>Wenn Maximum und Minimum gleich sind, ist es unsinnig 25-25 m zu schreiben. Kann man das so programmieren, dass dann einfach nur „25 m“ angezeigt wird? Ist zwar kein Range mehr, aber damit muss man leben. Ist auch vergleichsweise selten.</p></li>
<li><p>Wenn Maximum und Minimum beide 0 m sind (bei vielen Küstenpflanzen), wäre zu klären, ob man dann nicht „at sea level“ schreiben könnte. 0 m sieht blöd aus und impliziert beim unbedarften Betrachter einen Fehler. Aber wenn das zuviel Arbeit macht, muss eben 0 m da stehen.</p></li>
</ul>
<p><strong>Arten mit Höhenangaben:</strong> </p>
<ul>
<li><p>Salvia verbenaca</p></li>
<li><p>Salvia veneris</p></li>
<li><p>Salvia fruticosa</p></li>
<li><p>Trifolium argutum (sealevel example)</p></li>
<li><p>Trifolium arvense</p></li>
<li><p>Trifolium lappaceum</p></li>
<li><p>Bosea cypria</p></li>
</ul>
<p>see also #4031</p>
EDIT - feature request #3702 (Closed): WaterbodyOrCountry ISO 3166 alpha-3 code should be availab...https://dev.e-taxonomy.eu/redmine/issues/37022013-09-04T15:21:13ZAndreas Müller
<p>Currently the ISO alpha-3 code is only available as abbreviated label of the english representation. We should have an own attribute instead.</p>
<p>Separated <strong>this</strong> ticket from <a class="issue tracker-5 status-1 priority-14 priority-high12" title="feature request: Include ISO-3166 numeric codes to Country (New)" href="https://dev.e-taxonomy.eu/redmine/issues/2302">#2302</a> as <strong>this</strong> became fixed by #3479</p>
EDIT - feature request #3561 (Closed): Implement editing for abbreviated titlehttps://dev.e-taxonomy.eu/redmine/issues/35612013-06-26T16:23:21ZAndreas Müller
<p>Reference class does have 3 new fields: abbrevTitle, abbrevTitleCache and protectedAbbrevTitleCache. This needs to be reflected in the Taxonomic Editor.</p>
<p>Also check that all cache fields update correctly.</p>
<p>see #1551, <a class="issue tracker-5 status-1 priority-11 priority-default child" title="feature request: Implement abbreviated title in Dataportal (New)" href="https://dev.e-taxonomy.eu/redmine/issues/3562">#3562</a>, #3851, <a class="issue tracker-4 status-5 priority-13 priority-high13 closed child" title="bug: "Protected" indication for references needs to be improved (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/4944">#4944</a>, #5960</p>
EDIT - bug #3046 (Closed): Sort order for taxa with status not being nom.inval. is incorrecthttps://dev.e-taxonomy.eu/redmine/issues/30462012-08-10T12:15:45ZAndreas Müller
<p>The current TaxonComparator moves all taxa that do have ANY nom.status. to the end of a list as long as the other taxa do not have a status at all. Only if both taxa do have a status the comparison takes into account if the status is of type nom.inval. or nom.nudum. or of any other type.</p>
<p>According to N.Killian only nom.inval.(incl. nom.nudum) should be handled out of date order.</p>
<p>see also #3043, #3044, #3045, #3338, <a class="issue tracker-5 status-5 priority-12 priority-high14 closed" title="feature request: Move other invalid names to the end (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/5794">#5794</a></p>
EDIT - feature request #2854 (Closed): Implement part of other title for part of articles and par...https://dev.e-taxonomy.eu/redmine/issues/28542012-03-13T14:52:37ZAndreas Müller
<p>duplicate for #2853 to have it in both milestones</p>
EDIT - bug #2578 (Closed): Improve "move synonym"https://dev.e-taxonomy.eu/redmine/issues/25782011-08-31T15:25:07ZAndreas Müller
<p>The current implementation of ITaxonService.moveSynonymToAnotherTaxon is not fully correct yet.</p>
<p>We need to throw an exception if the synonym is part of a homotypical group (size> 1).</p>
<p>Additionally we need a method to move a homotypical group (all synonyms of a homotypical group) to another taxon. </p>
<p>Also check that the synonym to move is not part of the homotypical group of the accepted taxon.</p>
<p>see also #2585</p>
EDIT - feature request #2200 (Closed): Handle multiple authors for names correctly when cachinghttps://dev.e-taxonomy.eu/redmine/issues/22002011-01-17T13:48:30ZAndreas Müller
<p>Mail von Ralf:</p>
<p>(4) Das Thema ist zwar teilweise schon er-/bekannt, aber ich erwähne </p>
<blockquote>
<p>es, weil auch die anderen E-Floren das Problem bekommen werden. Die </p>
<p>"Berliner Schule" kürzt im Fall von mehr als 2 nomenklatorischen Autoren mit & al.</p>
<p>ab. Viele andere machen das nicht; so auch die Zypern-Checkliste. Gibt </p>
<p>man also mehr als 2 Autoren im Editor ein, werden im Portal-Baum die </p>
<p>Autorennamen mit angezeigt (auch in der General-Überschrift). Das ist </p>
<p>wohl zunächst ein Parsing-Problem.</p>
</blockquote>