EDIT Project Management: Issueshttps://dev.e-taxonomy.eu/redmine/https://dev.e-taxonomy.eu/redmine/redmine/favicon.ico?14691914852023-12-19T13:47:45ZEDIT Project Management
Redmine EDIT - discussion #10445 (Closed): [Master] Upgrade architecturehttps://dev.e-taxonomy.eu/redmine/issues/104452023-12-19T13:47:45ZAndreas Müller
<p>The EDIT platform architekture needs to be generally upgraded. This ticket is for reporting and linking ideas.</p>
<ul>
<li><p>Composable Web Architecture / Microservices / Hexagonale Architektur</p>
<ul>
<li><a href="https://www.bigcommerce.com/articles/ecommerce-website-development/composable-architecture/">https://www.bigcommerce.com/articles/ecommerce-website-development/composable-architecture/</a></li>
<li><a href="https://www.heise.de/hintergrund/Buchbesprechung-Get-Your-Hands-Dirty-on-Clean-Architecture-9289270.html">https://www.heise.de/hintergrund/Buchbesprechung-Get-Your-Hands-Dirty-on-Clean-Architecture-9289270.html</a></li>
<li><a href="https://www.happycoders.eu/de/software-craftsmanship/hexagonale-architektur/">https://www.happycoders.eu/de/software-craftsmanship/hexagonale-architektur/</a>
<ul>
<li><a href="https://www.happycoders.eu/de/software-craftsmanship/hexagonale-architektur-java/">https://www.happycoders.eu/de/software-craftsmanship/hexagonale-architektur-java/</a></li>
<li><a href="https://github.com/SvenWoltmann/hexagonal-architecture-java">https://github.com/SvenWoltmann/hexagonal-architecture-java</a></li>
</ul></li>
<li><a href="https://blog.getambassador.io/microservice-orchestration-best-practices-f32314dd6a12">https://blog.getambassador.io/microservice-orchestration-best-practices-f32314dd6a12</a></li>
<li><a href="https://medium.com/javarevisited/top-10-microservice-design-patterns-for-experienced-developers-f4f5f782810e">https://medium.com/javarevisited/top-10-microservice-design-patterns-for-experienced-developers-f4f5f782810e</a></li>
<li><a href="https://stackoverflow.com/questions/29117570/orchestrating-microservices">https://stackoverflow.com/questions/29117570/orchestrating-microservices</a></li>
</ul></li>
<li><p>techniques on job descriptions</p></li>
<li><p>reactive:</p>
<ul>
<li><a href="https://vertx.io/introduction-to-vertx-and-reactive/">https://vertx.io/introduction-to-vertx-and-reactive/</a></li>
</ul></li>
<li><p>Cloud native: <a href="https://www.enterpriseintegrationpatterns.com/patterns/messaging/PublishSubscribeChannel.html">https://www.enterpriseintegrationpatterns.com/patterns/messaging/PublishSubscribeChannel.html</a></p></li>
</ul>
<p>Code quality:</p>
<ul>
<li><a href="https://www.sonarsource.com/">https://www.sonarsource.com/</a></li>
<li><a href="https://www.jarchitect.com/">https://www.jarchitect.com/</a></li>
</ul>
<p>Architecture patterns:</p>
<ul>
<li>s. auch Lesezeichen in FF</li>
</ul>
EDIT - feature request #10385 (Closed): Add transliteration field to common nameshttps://dev.e-taxonomy.eu/redmine/issues/103852023-08-29T09:27:50ZAndreas Müller
<p>needed e.g. for Georgian common names. Also included in col-dp (update import afterwards!).</p>
EDIT - feature request #10318 (Closed): Add modifier vocabularies from Endara et alhttps://dev.e-taxonomy.eu/redmine/issues/103182023-05-09T13:24:26ZAndreas Müller
<p>see <a href="https://bdj.pensoft.net/articles.php?id=29232&journal_name=bdj">https://bdj.pensoft.net/articles.php?id=29232&journal_name=bdj</a></p>
<p>NoK:</p>
<p>wie neulich schon erwähnt, sind die State Modifiers wg. Projektende unter den Tisch gefallen und ich hatte sie irgendwie auch aus den Augen verloren.</p>
<p>Wir stießen damals sogar auf eine fix&fertige, genau für unsere Verhältnisse brauchbare Ontologie (paper attached, owl auf <a href="https://github.com/biosemantics/ontologies">https://github.com/biosemantics/ontologies</a>).</p>
<p>Wenn wir uns für den Weg entscheiden sollten, modifizierte states dynamisch zu erzeugen, dann könnten wir diese Ontologie (bzw. eine der beiden Versionen) dazu verwenden. Aber auch im anderen Fall wäre sie als Standard zur Bildung modifizierter States außerordentlich nützlich, d.h. <br>
wir sollten sie auf jeden Fall in irgendeiner geeigneten Form integrieren.</p>
EDIT - feature request #10310 (Closed): Add IUCN status as featurehttps://dev.e-taxonomy.eu/redmine/issues/103102023-04-27T10:11:33ZAndreas Müller
<p>It may allow Distribution and CategoricalData</p>
EDIT - feature request #10133 (Closed): Improve ontology state vocabularieshttps://dev.e-taxonomy.eu/redmine/issues/101332022-08-30T10:07:06ZAndreas Müller
<p>Some state vocabularies in the additivity ontology are not really states or have a hybrid character state/structure. Therefore we may want to handle them differently or move them to another term type.</p>
<p>Open issues:</p>
<ul>
<li><del>implement</del> <a class="issue tracker-5 status-5 priority-12 priority-high14 closed" title="feature request: Hybrid structure-state terms (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/10196">#10196</a></li>
<li><del>deduplicate vocabulary (State)structure (as many terms are also available as Structures)</del> , it is currently used for characters "stem shape" (id = 12176) and "stem architecture" (12190) <a href="#note-16">#note-16</a></li>
<li><del>define Centaurea used states</del> => see attachment</li>
<li>adapt descriptions for "structures in adjectival form" and "substances"</li>
<li>update labels for moved vocabularies</li>
<li><del>move "structures" to Structure (can't be done in bupleurum as being used as State there)</del></li>
<li><del>order state vocabularies</del> (<a href="#note-18">#note-18</a>) => not necessary anymore, use orderRelevant = false</li>
<li><del>solve entire plant-habit and -ecological adaptiations (possible solution, both become properties and children become states, but be aware of growth form states vocabulary already existing)</del></li>
<li><del>discussion on structural modifiers as the concept does not work for inner structure tree nodes</del> => decision to not use structural modifiers, instead use separate structure for each modified structure </li>
<li><del>check sources and URIs for all terms (see also <a class="issue tracker-5 status-5 priority-11 priority-default closed" title="feature request: Change term URI of TDWG Term to identifier in additivity ontology (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/8461">#8461</a>)</del></li>
<li><p><del>add state modifier vocabularies from Endara et al</del> => <a class="issue tracker-5 status-5 priority-13 priority-high13 closed" title="feature request: Add modifier vocabularies from Endara et al (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/10318">#10318</a></p></li>
<li><p>delete accuminate (replaced by acuminate), in shape 1.0</p></li>
</ul>
<p>Note: only strcutures, properties and states already in use and states with explicit description or media attached should become part of the importable ontology; Constantina will create a list of used states in Centaurea</p>
EDIT - task #8559 (Worksforme): Revision of the technical concept for the demositeshttps://dev.e-taxonomy.eu/redmine/issues/85592019-09-19T16:31:23ZAndreas Kohlbecker
<p>from <a class="wiki-page new" href="https://dev.e-taxonomy.eu/redmine/projects/edit/wiki/Meeting_2019-09-02">Meeting_2019-09-02</a></p>
<ul>
<li><p>"AK entwickelt Konzept für die Demo-Sites und damit den technischen Hintergrund von Workshops und Training events sowie das Selbststudium."*</p></li>
<li><p>Docker?</p></li>
<li><p>reuse workshop server setup scripts</p></li>
</ul>
EDIT - task #6591 (Closed): Use name used in source for original spellinghttps://dev.e-taxonomy.eu/redmine/issues/65912017-04-25T16:53:25ZAndreas Müller
<p>See <a class="issue tracker-6 status-7 priority-11 priority-default closed" title="task: Rethink original spelling strategy (Duplicate)" href="https://dev.e-taxonomy.eu/redmine/issues/3967">#3967</a> for further information </p>
EDIT - bug #5284 (Duplicate): [UML] Replace Scope by DefinedTerm in PolytomousKey UMLhttps://dev.e-taxonomy.eu/redmine/issues/52842015-09-21T18:36:57ZAndreas Müller
<p>Replace Scope by DefinedTerm in PolytomousKey UML</p>
EDIT - bug #5149 (Closed): Remove UNIQUE index on Sequence_Reference.citations_id columnhttps://dev.e-taxonomy.eu/redmine/issues/51492015-08-17T09:39:38ZPatrick Plitzner
<p>Summary was: "some Sequence_Reference tables have UNIQUE index on citations_id column"</p>
<p>I already deleted this on cdm_campanulaceae on the test server and I think also on production.</p>
<p>I also adapted the h2 scripts used in the JUnit tests.</p>
<p><code>citations_id</code> </p>
<p>DBs that are freshly created by the taxeditor do not have this index.</p>
EDIT - feature request #3972 (Closed): Strictly validate username to not null and not emptyhttps://dev.e-taxonomy.eu/redmine/issues/39722014-01-15T20:50:00ZAndreas Müller
<p>see also #3826</p>
EDIT - feature request #3958 (Closed): Handle CDMPreference tablehttps://dev.e-taxonomy.eu/redmine/issues/39582014-01-14T21:42:47ZAndreas Müller
<p>It is implemented in model but not yet used and not filled with any data. Methods in Service layer are also missing.</p>
<p>Keep in UML milestone as we may need a data updater (e.g. <a class="issue tracker-4 status-5 priority-13 priority-high13 closed" title="bug: Update Nomenclatural code for datasources (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/3658">#3658</a>). Move otherwise.</p>
<p>Decisions for the syntax of the different fields:</p>
<p>subject:</p>
<ul>
<li><p>/ (Database wide)</p></li>
<li><p>/TaxonNode<img src="for a classification or subtree" alt="#c1#33#44#35#55" /></p></li>
<li><p>/editor (??) for purely TaxEditor related preferences (e.g. show ID in supplemental data view)</p></li>
<li><p>TBC</p></li>
</ul>
<p>predicate: No required structure, but package like structure with dot separators makes sence</p>
<ul>
<li><p>aaaa.bbb.ccc.MATCH_MODE</p></li>
<li><p>aaaa.ee.ff.abc</p></li>
<li><p>allows starts with search to return lists of values</p></li>
<li><p>Case insensitive (?)</p></li>
<li><p>each predicate might be defined by as a constant of an enum</p></li>
</ul>
<p>object: up to the predicate to implement</p>
<p>Difficulties may occur when trying to match filters (subjects). An object that requires a preference (e.g. a TaxonName requires a list of available ranks) may match to multiple filters which map to different values (e.g. because the name is used in multiple classifications)</p>
<p>for details see: #3555, see also open issues there</p>
<p>related #5004, #3773, <a class="issue tracker-5 status-5 priority-10 priority-lowest closed child" title="feature request: Implement CdmPreference reading for database preferences (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/5969">#5969</a></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 #2975 (Closed): Add noDataStatus to descriptive data (QuantitativeData and...https://dev.e-taxonomy.eu/redmine/issues/29752012-07-18T15:18:19ZAndreas Müller
<p>... to allow Xper² unknown data. But first check how this is implemented in SDD.</p>
<p>Duplicate for #2974 to have it in UML milestone too.</p>
EDIT - feature request #2949 (Duplicate): Simplify TaxonName classeshttps://dev.e-taxonomy.eu/redmine/issues/29492012-07-06T09:51:34ZAndreas Müller
<p>Currently we do have 7 TaxonNameBase related classes. However only ViralName really differs much from all other classes.</p>
<p>Having different classes instead of pure type information from a type enum such as in Reference creates a lot of overhead for programming, therefore we should unify at least all 5 NonViralName classes.</p>
<p>However, the largest overhead is created by the differentation of TaxonNameBase and NonViralName as TNB is referenced e.g. by TaxonBase whereas for most operations on names we need NVN. This is also a recurring source of bugs such as Class Cast Exceptions.</p>
<p>As ViralNames are very rarely used, it is suggested to integrate them also within 1 (!) TaxonName class and treat incorrect handling via validation. </p>
<p>Also changing name types without changing uuid/id is easier this way.</p>
<p>Allow interfaces for correct programming such as for Reference interfaces.</p>
<p>NomenclaturalCode may become the type class and be persisted (see also #2615)</p>
<p><a href="http://cybertaxonomy.eu/cdm-uml/v31/">http://cybertaxonomy.eu/cdm-uml/v31/</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>