Project

General

Profile

task #8275

[DISCUSS] Relationship between invalid designations and invalid names / nom. inval.

Added by Andreas Müller 6 days ago. Updated 6 days ago.

Status:
New
Priority:
New
Category:
cdm
Start date:
05/14/2019
Due date:
% Done:

0%

Severity:
normal
Tags:

Description

Is this the same?

In BM dataportal version of E+M it looks like ALL nom. inval. are shown as inval. desig.:

So it looks like it is the same. Therefore this primarily seems to be ad data portal ticket as it is about how to publish the data.

However, we may also discuss, why we do not use the invalid designation taxon relationship here instead of an ordinary synonym relationship for a "nom. inval." name.

Open questions:

picture761-2.png View (7.95 KB) Andreas Müller, 05/14/2019 11:36 AM


Related issues

Related to Edit - task #8055: Correct formatting for invalid designations New 02/01/2019
Related to Edit - feature request #7666: Remaining issues for "Formatter and DTO for taxon relationships (e.g. misapplied names)" In Progress 08/20/2018

History

#1 Updated by Andreas Müller 6 days ago

  • Description updated (diff)
  • Target version changed from Euro+Med Migration to Euro+Med Portal Release

#2 Updated by Andreas Müller 6 days ago

  • Related to task #8055: Correct formatting for invalid designations added

#3 Updated by Andreas Müller 6 days ago

  • Related to feature request #7666: Remaining issues for "Formatter and DTO for taxon relationships (e.g. misapplied names)" added

#4 Updated by Andreas Müller 6 days ago

ERS (2018-03-28):

Dear all,

to facilitate the discussion about the status "invalid designation", I am continuing in English and put Nick in cc.

The background for this is article 6.3 Melbourne Code: "In this code, unless otherwise indicated, the word "name" means a name that has been validly published [...]".

Consequently, there is no such thing (status) as a nom. inval., because if it is not validly published, it is by definition not a name, but an invalid designation (des. inval.).

In fact, the abbreviation so commonly found in the literature "nom. inval." is not even included in the glossary, nor in the subject index of the Melbourne code (neither is "invalid designation", nor "des. inval.").

In Euro+Med Plantbase, the editors took the code very literally, eventually arriving at the point that such an invalid designation is not even a synonym (which has to be a good name). It is common practice to indicate this, in synonym lists, with a dash before the "name", instead of the "=" which precedes a validly published synonym. However, in most publications, the abbreviation "nom. inval." is commonly used. @Nick, do you have a recommendation how to deal with invalid designations in databases and publications, from a nomenclatural point of view?

In the following example,
http://ww2.bgbm.org/EuroPlusMed/PTaxonDetail.asp?NameId=121643&PTRefFk=7000000
Euro+Med
differentiates between
Basionym; Homotypic synyonyms; heterotypic synonyms; invalid designations and misapplied names.

@Anton, do you know how the status "invalid designation" is assigned in the Berlin Model Portal?

Answer to:

AM: ... Bevor ich es vergesse, möchte ich einen Fall hier aber schon mal erwähnen, und zwar http://ww2.bgbm.org/EuroPlusMed/PTaxonDetail.asp?NameId=7709633&PTRefFk=7100000 , also der erste Fall bei den Synonymen (Bromus ramosus subsp. bikfayensis).
Dieses wird als INVALID DESIGNATION ausgegeben, allerdings habe ich keine Ahnung, woher diese Information stammt. Im BM Editor finde ich sie in keinem Feld. Ist das eine Zusammengesetze Information? Auch wurde nicht der Relationstyp „is invalid designation for“ verwendet. Hat jemand eine Ahnung woher das kommt?
Das wäre wichtig zu wissen, um ggf. ähnliche Fälle auch korrekt behandeln zu können.

#5 Updated by Andreas Müller 6 days ago

We do not have any invalid designation relationships in E+M (BM):

SELECT *
FROM RelPTaxon rel
WHERE   RelQualifierFk IN (8)
ORDER BY RelQualifierFk;

#6 Updated by Andreas Müller 6 days ago

  • Description updated (diff)

#7 Updated by Andreas Müller 6 days ago

  • Description updated (diff)

#8 Updated by Andreas Müller 6 days ago

All invalid names (term ids may need to be adapted)

SELECT ns.type_id, ns.citation_id, n.nameCache, n.titleCache, n.id
FROM NomenclaturalStatus ns INNER JOIN TaxonName_NomenclaturalStatus MN ON MN.status_id = ns.id
 INNER JOIN  TaxonName n ON n.id = MN.TaxonName_id
WHERE ns.type_id IN (867, 871, 877, 876, 873, 875) AND nameCache LIKE 'Tara%cup%'
ORDER BY ns.type_id

And the vocabulary (id to be adapted):

SELECT *
FROM DefinedTermBase dtb 
WHERE dtb.titleCache LIKE '%%'
AND dtb.DTYPE = 'NomenclaturalStatusType' AND dtb.vocabulary_id = 19;

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)