EDIT

To make it more flexible we should add a vocabulary with the terms, otherwise we have to add the terms in a static way and adding a new occurence status type would need to adapt the implementation.

Andreas Müller wrote in #note-11:

Katja Luther wrote in #note-9:

To make it more flexible we should add a vocabulary with the terms, otherwise we have to add the terms in a static way and adding a new occurence status type would need to adapt the implementation.

There is already a vocabulary. See OccurrenceStatusType.csv.

But more relevant than the vocabulary is the termType, which is OST ("OccurrenceStatusType").

Or I fully misunderstand your comment.

Sorry this was a mistake...
A first implementation is available now.

please review.

Generally this works. Only the location in the UI should be improved. Currently it is too much hidden.

For DerivedUnit DetailsView I suggest to put it at the end of the "General" section. Same for the DerivedUnitFacade DetailsView/Dialogue.

Also it would be nice to have a summary label beside the label "Status" which concatenates all status if there are any. However, this is a nice to have and probably a general issue for all lists or expandable sections, so it does not need be solved in this ticket if difficult.

Andreas Müller wrote in #note-15:

Generally this works. Only the location in the UI should be improved. Currently it is too much hidden.

For DerivedUnit DetailsView I suggest to put it at the end of the "General" section. Same for the DerivedUnitFacade DetailsView/Dialogue.

Now, the status is between pref. stable uri and publish flag. for all details views/dialogues.

Also it would be nice to have a summary label beside the label "Status" which concatenates all status if there are any. However, this is a nice to have and probably a general issue for all lists or expandable sections, so it does not need be solved in this ticket if difficult.

This is implemented as well.

The selection is now at a better place, so we can close this ticket.

There are only very few nice to haves that might go into a follow up ticket if not being no-brainers

• The space above should be less and the space below should be more (the collapsed line should be in the middle between "Pref. Stable URI" and "Publish"
• the summary is not automatically updated, but only after reloading the details view
• we may discuss if the "+" beside the summary is still needed with the summary being their; I guess it is not necessary but not sure

Issues 2 and 3 are of general interest for al such lists and collapsed sections. Maybe we can create a new ticket saying that such summaries should be implemented everywhere and the "+" should be replaced, and we give the specimen status as example how it should look like and be implemented.

Removed the '+'

Works as expected now.