EDIT

Do we need a configuration method to define the "Description (aggregated)" feature tree? Otherwise it seems to be impossible to order the descriptions correctly

Andreas Müller wrote:

Do we need a configuration method to define the "Description (aggregated)" feature tree? Otherwise it seems to be impossible to order the descriptions correctly

Can you please explain this a bit more? Is there a Feature tree to oder list of descriptions in the taxon page or do you refer to the elements in the aggregated description? In the latter case it would rather be a requirement for issue #8595

Andreas Kohlbecker wrote:

Andreas Müller wrote:

Do we need a configuration method to define the "Description (aggregated)" feature tree? Otherwise it seems to be impossible to order the descriptions correctly

Can you please explain this a bit more? Is there a Feature tree to oder list of descriptions in the taxon page or do you refer to the elements in the aggregated description? In the latter case it would rather be a requirement for issue #8595

Aggregated description are created using DescritiveDataSets. These do have a FeatureTree ("descriptiveSystem") which describes the order of the features (hierarchical and between sibblings). The currently randomly concatenated structured descriptive data should be ordered according to this tree.
As this is not the same tree as the one defined for the general page we need a possiblity to define it explicitly in dataportal configuration. Alternatively we could use the link from the description to the DescriptiveDataSet to the "descriptiveSystem" to define the tree to use. But I am not sure if this is a good idea, also because for the generic usecase we may even not have a descriptive data set for structured descriptive data but may still want to define an order how to display.
Also there might be the requirement to use a different tree for display then for editing/aggregating the data.

Andreas Müller wrote:

Andreas Kohlbecker wrote:

Can you please explain this a bit more? Is there a Feature tree to oder list of descriptions in the taxon page or do you refer to the elements in the aggregated description? In the latter case it would rather be a requirement for issue #8595

It is a requirement to order the elements. But for this it is requirement for this ticket as well as for #8595. In both cases the data needs to be ordered (and we need to discuss if ordering should take place server side or portal side)

Wait, you are going in the wrong direction. We are not talking about FeatureTrees here. Just about the order of TOC items resp. the order of "blocks" on the taxon page.

Andreas K.: You mentioned that it is possible to assign weights to these blocks. With this it should be possible to show the block "Descriptions (aggregated)" always after "Description".

Added a separate ticket for the ordering of description elements -> #8657

Patrick Plitzner wrote:

Wait, you are going in the wrong direction. We are not talking about FeatureTrees here. Just about the order of TOC items resp. the order of "blocks" on the taxon page.

Yes and no. My comment 3 was not an answer on comment 2 but an additional requirement that needs to be handled urgently. Currently the elements are not ordered and this needs to be fixed urgently. Or is there another ticket for this. If yes please create relation.

But the tree that I mentioned can be used for both the block here and for the "description detail page" (#8595)

Patrick Plitzner wrote:

Andreas K.: You mentioned that it is possible to assign weights to these blocks. With this it should be possible to show the block "Descriptions (aggregated)" always after "Description".

Yes, I will care for this task ... new ticket #8765