EDIT: Issueshttps://dev.e-taxonomy.eu/redmine/https://dev.e-taxonomy.eu/redmine/redmine/favicon.ico?14691914852018-05-07T16:15:45ZEDIT Project Management
Redmine feature request #7405 (Closed): Rename WorkingSet to DescriptiveDataSethttps://dev.e-taxonomy.eu/redmine/issues/74052018-05-07T16:15:45ZAndreas Müller
<p>WorkingSet is a too general name. DescriptiveSystem or DescriptiveDataSet better suits the semantics of this class.</p>
feature request #7384 (Closed): Order SpecimenTypeDesignationStatus according to new order in voc...https://dev.e-taxonomy.eu/redmine/issues/73842018-04-27T12:42:38ZAndreas Müller
<p>Due to <a class="issue tracker-4 status-5 priority-11 priority-default closed" title="bug: Show types in correct order (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/6526">#6526</a> the order of type designations status has been slightly changed.<br>
The order should be adapted in existing databases.</p>
feature request #7334 (Closed): Make pro parte and partial synonyms real concept relationshipshttps://dev.e-taxonomy.eu/redmine/issues/73342018-03-28T12:19:32ZAndreas Müller
<p>Since <a class="issue tracker-5 status-5 priority-11 priority-default closed parent" title="feature request: Remove synonym relationships (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/5974">#5974</a> pro parte and partial is stored as attribute of a synonym which belongs to exactly 1 accepted taxon.</p>
<p>Pro parte and partial synonyms may link to multiple taxa and they are not real synonyms in terms of that they are equal to the accepted taxon in semantics. Indeed, they are concept relationships and therefore should be handled as such.</p>
<p>We need 2 new taxon relationship types for them. Also we need to migrate existing data by making the synonyms accepted taxa and create the according taxon relationship.</p>
feature request #6943 (Closed): Allow zoological in-Authors in taxon nameshttps://dev.e-taxonomy.eu/redmine/issues/69432017-09-13T08:25:30ZAndreas Müller
<p>The zoological code (<a href="http://www.nhm.ac.uk/hosted-sites/iczn/code/">http://www.nhm.ac.uk/hosted-sites/iczn/code/</a>) allows citation of contributions authors as "A in B".</p>
<p>"Recommendation 51E. Citation of contributors. If a scientific name and the conditions other than publication that make it available [Arts. 10 to 20] are the responsibility not of the author of the work containing them, but of some other person(s), or of less than all of joint authors, the authorship of the name, if cited, should be stated as "B in A", or "B in A & B", or in whatever form is appropriate to facilitate information retrieval (normally the date should also be cited)."</p>
<p>Currently this can only be handled in the AbbrevTitleCache of the author with an extra record for this author that contains both information. Alternatively we could have an extra field for the "in" author for zoological taxon names. Or maybe even 2 such fields for combination author and original author.</p>
<p>Examples for this were first observed in edaphobase.</p>
feature request #6752 (Closed): Add verbatimDatehttps://dev.e-taxonomy.eu/redmine/issues/67522017-06-23T11:51:48ZAndreas Müller
<p>We may need an additional field verbatimDate which is e.g. for references the date when the reference was published according to what is written on front page.</p>
<p>A couple of questions exist:</p>
<ul>
<li>do we need this field for all TimePeriods or only for usage in Reference => decision: references only</li>
<li>what format should it have? String, Date, DateTime, TimePeriod, PartialDate, ... => decision: String</li>
</ul>
<p>If it does not become a field within TimePeriod it may become more difficult to parse and format such dates as you need to implement separate parsers and formatters for this special use case.<br>
But we could use a subclass VerbatimTimePeriod which has an extra field.</p>
<p>If it becomes a String it is not possible to format differently according to the needs of the output (e.g. the new IPNI format [dt. Jan 2013; issued 28 Dec 2012] then is not possible to use in a special publication when at other places we only want to have something like "2013" 2012</p>
<p>Other places where TimePeriod is currently used are: Classification.timeperiod, InstitutionalMembership.period, Person.lifespan, EvenBase.timeperiod (including subclasses Amplification, DerivationEvent, DeterminationEvent, GatheringEvent, MaterialOrMethodEvent [Cloning, PreservationMethod], SingleRead), DescriptionElementBase.timeperiod, NamedArea.validPeriod, </p>
<p>See also <a class="issue tracker-4 status-5 priority-10 priority-lowest closed" title="bug: Remaining cdm light issues (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/6627#note-10">#6627#note-10</a></p>
<p>Open issues:</p>
<ul>
<li>Parsing and Formatting (<a class="issue tracker-5 status-5 priority-10 priority-lowest closed" title="feature request: Improve parsing and formatting for VerbatimTimePeriod (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/7429">#7429</a>)</li>
<li><del>TaxEditor implementation</del> (<a class="issue tracker-5 status-5 priority-11 priority-default closed" title="feature request: Implement verbatim date for references in TaxEditor (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/7421">#7421</a>)</li>
<li><del>Vaadin implementation</del> (<a class="issue tracker-6 status-5 priority-10 priority-lowest closed" title="task: Implement VerbatimTimeField for cdm-vaadin and use this in the ReferencePopupEditor (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/7425">#7425</a>)</li>
</ul>
feature request #6720 (Closed): Make individualCount a stringhttps://dev.e-taxonomy.eu/redmine/issues/67202017-06-12T14:44:16ZAndreas Müller
<p>Currently it is integer, but usually one needs something like 3M,4W</p>
feature request #6588 (Closed): Add URL and URL comment to OriginalSource / ExternalLinkhttps://dev.e-taxonomy.eu/redmine/issues/65882017-04-24T17:24:53ZAndreas Müller
<p>An original source may sometimes want to link to an external link where the reference (the page in the reference) is available, e.g. a link to BHL.<br>
We may want to have a URI field for this.</p>
<p>Maybe we also nee multiple URIs for multiple links or maybe even a wrapped URI class which includes further information such as a comment (e.g. why has this link be used or what exactly can be seen here) or a link type. With only one URI we could handle this in parallel to the URI field, otherwise a separate class is to be preferred.</p>
<p>see also comments in <a class="issue tracker-4 status-7 priority-10 priority-lowest closed" title="bug: Add URL for TypeDesignation (Duplicate)" href="https://dev.e-taxonomy.eu/redmine/issues/6434">#6434</a> and <a class="issue tracker-5 status-7 priority-11 priority-default closed" title="feature request: [DISCUSS] Comment field for "Protolog" (Duplicate)" href="https://dev.e-taxonomy.eu/redmine/issues/6435">#6435</a> and <a class="issue tracker-5 status-5 priority-10 priority-lowest closed" title="feature request: Handle protologue as original source with URI link (Closed)" href="https://dev.e-taxonomy.eu/redmine/issues/6589">#6589</a></p>
<p>Decision: Handle as separate class ExternalLink</p>
<p>Open: </p>
<ul>
<li>should we handle files via Media or via ExternalLink, general they do have characteristic of Media like (Author, versions, ...) but currently it is not easy to interchange between these both. Maybe ExternalLink could have an extra field Media that links to a full media object, so ExternalLink becomes a Wrapper for simple URIs and complex Media </li>
</ul>
feature request #2335 (Closed): Make WorkingSet IdentifiableEntityhttps://dev.e-taxonomy.eu/redmine/issues/23352011-04-14T21:09:23ZAndreas Müller
<p>For Xper we need Extensions for additional data associated to a working set. Also Media is needed.</p>
<p>As being the container for all descriptive data and for a multi-access key it also seems to make sense to have it identifiable. </p>
<p>see also #2336</p>