EDIT: Activityhttps://dev.e-taxonomy.eu/redmine/https://dev.e-taxonomy.eu/redmine/redmine/favicon.ico?14691914852024-03-19T08:47:09ZEDIT Project Management
Redmine Revision e6f4e650 (cdm-dataportal): ref #10472: adapt testhttps://dev.e-taxonomy.eu/redmine/projects/edit/repository/cdm-dataportal/revisions/e6f4e650ccbc647e41b9bfc27430f44025da89fe2024-03-19T08:47:09ZKatja LutherRevision 277d90f9 (cdm-dataportal): ref #10482: add to hotfix branchhttps://dev.e-taxonomy.eu/redmine/projects/edit/repository/cdm-dataportal/revisions/277d90f941ff0e23cc5deb74e36e0fb1848e3fbd2024-03-18T15:38:16ZKatja Lutherbug #10482 (Resolved): Registrations with two or more types of the same type result in errorhttps://dev.e-taxonomy.eu/redmine/issues/10482#change-717202024-03-18T14:51:48ZKatja Luther
<p>Applied in changeset <a class="changeset" title="fix #10482: correct handling of typedesignations" href="https://dev.e-taxonomy.eu/redmine/projects/edit/repository/cdm-dataportal/revisions/1ce81374945b6302c8e83c95c5357fbc9c89881a">cdm-dataportal|1ce81374945b6302c8e83c95c5357fbc9c89881a</a>.</p>
Revision 1ce81374 (cdm-dataportal): fix #10482: correct handling of typedesignationshttps://dev.e-taxonomy.eu/redmine/projects/edit/repository/cdm-dataportal/revisions/1ce81374945b6302c8e83c95c5357fbc9c89881a2024-03-18T14:51:26ZKatja Lutherbug #10482 (Resolved): Registrations with two or more types of the same type result in errorhttps://dev.e-taxonomy.eu/redmine/issues/104822024-03-18T14:48:57ZKatja Luther
<p>The registration page for names with more than one typedesignations of one type resulting in an error. </p>
bug #9317: Handle NameTypeDesignations on name basis not on homotypic group basis in outputshttps://dev.e-taxonomy.eu/redmine/issues/9317#change-717192024-03-18T12:18:10ZAndreas Müller
<p>NoK:</p>
<p>I agree with Eckhard and Robert that because the name type belongs to the entire homotypic group the type citation should therefore follow it as it is currently implemented at all ranks and not split.</p>
<p>I agree with Robert that for convenience at least the combination with the accepted genus name and its basionym but in case of more names in the homotypic group all corresponding homonyms of the name type should be cited in a single para under "Type:"</p>
bug #10481 (New): Vaadin type of the genus: selection truncatedhttps://dev.e-taxonomy.eu/redmine/issues/104812024-03-18T11:00:45ZWolf-Henning Kusber
<p>In the production system the following entries are missing:<br>
original designation<br>
monotypy<br>
automatic (not relevant for genus, but for ranks higher than genus and we decided to show all options for the genus, correct?)</p>
<p>In the selection:<br>
lectotype<br>
subsequent designation<br>
subsequent monotypy<br>
present designation<br>
not applicable</p>
<p>All options are shown in the test Vaadin (see):<br>
Genus: Monotypicgenus Kusber<br>
"Publication" Kusber, W.-H.: Generitype monotypic. – Zeitschrift für Tümpelkunde 11: 22-33</p>
feature request #10479: [Discuss] Format hybrids with space between × and name parthttps://dev.e-taxonomy.eu/redmine/issues/10479#change-717182024-03-18T08:53:34ZAndreas Müller
<p>NoK:</p>
<p>As correctly mentioned by Rafaël Govaerts (cited by Walter below), the Code actually does permit a flexible use of space between the multiplication sign and the epithet, see Rec. H.3A <a href="https://www.iapt-taxon.org/nomen/pages/main/art_h3.html">https://www.iapt-taxon.org/nomen/pages/main/art_h3.html</a>.</p>
<p>Although I also like the current way hybrids are displayed in the EDIT Portals, exports of data into other databases are in my view an important argument to have a solution avoiding ambiguities. </p>
<p>As the amount of space is flexible, using a fraction of a space between the multiplication sign and the epithet (but a full space in formulae) would be an option. If I understand it correctly, unicode provides different widths of space (see e.g. <a href="https://www.compart.com/en/unicode/category/Zs">https://www.compart.com/en/unicode/category/Zs</a>).</p>
Revision 899a343a (cdm-dataportal): ref #10472: also remove relsec from search resulthttps://dev.e-taxonomy.eu/redmine/projects/edit/repository/cdm-dataportal/revisions/899a343a79836bf8573a1693ec9d2b920d139a7d2024-03-15T13:22:58ZKatja LutherRevision dbe27f55 (cdm-dataportal): ref #10472: adapt test for last commithttps://dev.e-taxonomy.eu/redmine/projects/edit/repository/cdm-dataportal/revisions/dbe27f55643a8936e6b69709ab09daa091e8aa782024-03-15T13:04:26ZKatja LutherRevision 2d2ff8c5 (cdm-dataportal): ref #10472: show only name without sec and nom ref for acc of...https://dev.e-taxonomy.eu/redmine/projects/edit/repository/cdm-dataportal/revisions/2d2ff8c53f3a5051d5581516cac870e2029467e92024-03-15T12:50:15ZKatja Lutherbug #10480 (Resolved): Problems with name details view when ranks are limitedhttps://dev.e-taxonomy.eu/redmine/issues/10480#change-717162024-03-15T11:47:43ZKatja Luther
<p>This should be fixed, please review.</p>
bug #10480 (Resolved): Problems with name details view when ranks are limitedhttps://dev.e-taxonomy.eu/redmine/issues/104802024-03-15T11:45:48ZKatja Luther
<p>There are problems with the details view if the rank selection is reduced in the local preferences. This is fixed by loading the rank list during the connection to the data source.</p>
feature request #9596: Open issues for TypeDesignationWorkingSethttps://dev.e-taxonomy.eu/redmine/issues/9596#change-717072024-03-15T11:06:21ZAndreas Müller
<p>AM:</p>
<p>ich habe nochmal geschaut und grundsätzlich gibt es bereits Tagged Text für die Type Specimen.</p>
<p>Z.B. <a href="https://test.e-taxonomy.eu/cdmserver/caryo_spp/portal/taxon/254abe96-3cb7-4b24-a682-2a4968045431/page.json?recipe=EuroPlusMed&featureTree=0bf9769c-dc21-4c7d-8200-e5d00b9e8b31&part=mapUriParams&part=tree&doSynonyms=1&doMedia=1&doTaxonNodes=1&doTaxonRelations=1">https://test.e-taxonomy.eu/cdmserver/caryo_spp/portal/taxon/254abe96-3cb7-4b24-a682-2a4968045431/page.json?recipe=EuroPlusMed&featureTree=0bf9769c-dc21-4c7d-8200-e5d00b9e8b31&part=mapUriParams&part=tree&doSynonyms=1&doMedia=1&doTaxonNodes=1&doTaxonRelations=1</a> und dort unter homotypicSynonyms->taggedTypes</p>
<p>Ich habe da für den ersten Typus auch mal eine Referenz hinzugefügt (fide) und zusätzlich einen Lectotype daraus gemacht. Die fide-Referenz kommt bereits so raus wie erwartet. Das könntest du also direkt umsetzen. Die Lectotype-Referenz (designated by) ist irgendwie kaputt. Der Tag fehlt. Aber das sollte sich leicht fixen lassen.</p>
<p>Etwas schwieriger wird es mit den Links für die Specimen. Derzeit spiele ich rum, ob ich dafür eine spezielle Unterklasse „TypedEntityReferenceWithLink“ erzeuge. Wenn der Link gesetzt ist, würde dieser dann genommen, ansonsten der Link zum CDM Specimen (uuid), wobei der im TaggedText auch noch nicht stimmt.</p>
<p>Irgendwie ist das aber nicht so schön, und ich überlege, ob wir hier nicht gleich mit einer besseren Neuimplementierung von TaggedText arbeiten sollten, da der Bereich ja noch wenig genutzt wird und das hier möglich wäre. Auch die TaggedText types (z.B. „label“, „specimenOrObservation“, „typeDesgination“) sollten wir noch ändern. Die sind schlecht gewählt. „Label“ ist eher „typeStatus“, „specimenOrObservation“ -> „fieldUnit“ und „typeDesignation“ eher „specimen“.</p>
<p>Für letzteres bräuchten wir evtl. noch Untertags, um Collection und Accessionnumber zu unterscheiden, sowie die „destroyed“ Information. Für diese wird bislang auch noch nicht die Quelle mit ausgegeben.</p>
feature request #7771: Format Misapplication search results as MAN, not as accepted taxahttps://dev.e-taxonomy.eu/redmine/issues/7771#change-717062024-03-15T10:42:56ZAndreas Müller
<p>Example: </p>
<p><a href="https://test.e-taxonomy.eu/dataportal/preview/cichorieae/cdm_dataportal/search/results/taxon?ws=portal%2Ftaxon%2FfindDto&query=Hieracium+gomben*&form_build_id=form-YlMcNzz6JEmzUBuJvxOkC0DDZZ2IIJ7IGW_6acxTmwQ&form_id=cdm_dataportal_search_taxon_form&search%5BdoTaxaByCommonNames%5D=1&search%5BdoMisappliedNames%5D=1&search%5BdoSynonyms%5D=1&search%5BdoTaxa%5D=1&search%5BpageSize%5D=25&search%5BpageIndex%5D=0">https://test.e-taxonomy.eu/dataportal/preview/cichorieae/cdm_dataportal/search/results/taxon?ws=portal%2Ftaxon%2FfindDto&query=Hieracium+gomben*&form_build_id=form-YlMcNzz6JEmzUBuJvxOkC0DDZZ2IIJ7IGW_6acxTmwQ&form_id=cdm_dataportal_search_taxon_form&search%5BdoTaxaByCommonNames%5D=1&search%5BdoMisappliedNames%5D=1&search%5BdoSynonyms%5D=1&search%5BdoTaxa%5D=1&search%5BpageSize%5D=25&search%5BpageIndex%5D=0</a></p>
<p>Open issue:</p>
<ul>
<li>remove err. sec. from result</li>
<li>allow configuration if sec. of accepted taxon should be shown (does not make sense in a single classification environment)</li>
<li>check if ",non xxx" is shown or make it configurable to show</li>
<li>show "sensu" (as in TaxEditor search) or make it configurable to show it</li>
<li>discuss, how to handle names with multiple sensu information on the same taxon page (e.g. Xxxx yyy sensu Aaaa 2009, sensu Bbbb 2010, sensu Cccc 2011). Should these be multiple entries in the search or a single one</li>
</ul>