feature request #8304
feature request #8108: Name page shows complete name information
Name page redirects to according taxon depending on query parameter
As requested in #8108 the redirection behavior of the name page to the related taxon (if there is only one) should be configurable.
The behavior should not be unique for the whole dataportal but individually different for the contexts in which a name is used in the portal.
Therefore the best solution would be to make it configurable via a query parameter or by drupal path argument.
The behavior also needs to be configurable per portal installation individually per context. The render templates already allow to fine tune the display of names and taxa, to enable links to the name and nomref. From this point of view it seems to make sense to use the render templates also for the configuration of the autoredirect feature of the name page. rejected in favor of having this implemented more quick an simplistic, see comment 4
fix #8304 redirect from name to taxon page depending on drupal path argument, with test
#1 Updated by Andreas Kohlbecker about 2 months ago
- Status changed from New to Resolved
- % Done changed from 0 to 50
Applied in changeset cdm-dataportal|2f65af049f9784cd0b0de8096df842491c590b31.
#3 Updated by Andreas Kohlbecker 23 days ago
ich bemerke gerade eine Veränderung in der Anzeige von Homonymbeziehungen:
Wenn ich in http://cichorieae.e-taxonomy.net/portal/cdm_dataportal/taxon/0d33931c-b89b-47ba-aecd-93a11778f765/synonymy?highlite=f69929b6-942c-4f53-b1f4-25db9345b580&acceptedFor=f69929b6-942c-4f53-b1f4-25db9345b580#f69929b6-942c-4f53-b1f4-25db9345b580 auf das ältere Homonym H. foliosa Vill. 1876 gehen, lande ich nicht wie früher in der Synonymy der Taxonseite zu der das ältere Homonym gehört, sondern auf eine nutzlosen Zwischenseite http://cichorieae.e-taxonomy.net/portal/cdm_dataportal/name/a111f1a1-304f-4e38-9ea7-ca4086a6d23e/f69929b6-942c-4f53-b1f4-25db9345b580/null/
Lässt sich das wieder abstellen??
By the way: Fußnotenverweise werden z.Z. verdoppelt dargestellt, so auf http://cichorieae.e-taxonomy.net/portal/cdm_dataportal/taxon/e2b2af79-21bc-4a49-98d8-3b716ca26e9b/synonymy?highlite=c661ae18-da75-48c1-bd0d-8955ad2e4b8b&acceptedFor=c661ae18-da75-48c1-bd0d-8955ad2e4b8b#c661ae18-da75-48c1-bd0d-8955ad2e4b8b, sihe unter A. uniflorus car. crepidifolius ....
#4 Updated by Andreas Kohlbecker 23 days ago
The suggestion made in the issue description to use the name render templates to fine tune the behavior of the autoredirect feature per portal and context would require quite some time to be implemented. The render templates are evaluated in the
render_name_or_taxon() method the autoredirect feature however is implemented in the
cdm_dataportal_name_view() method which is a completely different place. The extension of the render templates would also be a bit costly in terms of time. Therefore I will only implement a global switch in the settings by which the autoredirect feature can be enabled always.
#7 Updated by Andreas Müller 1 day ago
- Status changed from Resolved to Feedback
- Assignee changed from Andreas Müller to Andreas Kohlbecker
I do not fully understand this solution. I thought it should be configurable for each location that has a link to a name (e.g. name in source, name in synonymy, determined under, ...
The current implementation allows to configure only 1 (and always the same) behavior it does not allow to distinguish where the call comes from as far as I can see.
#8 Updated by Andreas Kohlbecker about 18 hours ago
- Assignee changed from Andreas Kohlbecker to Andreas Müller
This is a misunderstanding. During the standup yesterday I was talking about a global switch which overrides the default behavior. The explanation why I decided for this solution is found in comment 14
Also other implementations witch are not making use of the render templates would be costly in terms of time. I think we should not invest this time as long there is no definite user request for this.