feature request #6413
Updated by Andreas Müller about 5 years ago
Coming from the name editor it is currently only possible to add a new type designation in order to create a type specimen. If the user wants to create an isotype i.e. a duplicate of the recently added type specimen it is not possible to create a "real" duplicate that shares the same FieldUnit. For this the user has to switch to the specimen editor. How could the interface look like to directly create an isotype (or any related type) coming from the name editor? * the specimen wizard could be shown with all the FieldUnit data already entered (because the new DerivedUnit is already a child of the existing FieldUnit * a reduced wizard where the user can only select the collection is shown * ... WGB: Auch hier wäre natürlich eine Möglichkeit, mehrere Specimen gleichzeitig zu Isotypen zu erklären, ausgesprochen nützlich – alle Specimens einer Field Unit sind ja normalerweise Typen. ... Hier wäre eine Kontextmenüfunktion *Add – Specimen duplicates* sehr komfortabel, in die man eine Liste von Herbarabkürzungen eintragen kann, die dann entsprechend zu Specimen gemacht werden (ggf. unter Erzeugung einer neuen Collection) (#6665) Possible solution in the details view of name editor: 1. First we could add a new button/extend the functionality of the +-button to create a new type designation 1. The button will open a dialog where you can select the field unit on which the new specimen duplicate is based. If there is only one field unit then this step can be skipped and the only field unit is selected 1. Another dialog opens where you can specify the accession number, collection and what kind of type it is(holo, lecto, etc.) 1. As a first implementation step, it is only possible to create on specimen duplicate 1. As a second step it should be possible to enter a list of accesion numbers, collections and types to create multiple duplicates **Note** Note on algae data: generally the common parent for duplicates must not be field units but also can be derivatives like cultures. However, for most cases the relationship between field unit and final specimen is most important so in a first step it is enough to use the field unit as the common parent. If a user wants to model this more exactly he/she should go to specimen tree editor afterwards. **Note** on available status: Usually we do have status pairs, a holotype has isotypes, a neotype has isoneotypes, a lectotype has isolectotypes, etc. as possible duplicates. We should consider this when offering default status or a list of sorted status where the most probable status is shown on top