FederationMissingNotice in Collection component not fitting and redundant

[christophfriedrich]

The Collection component already has the FederationMissingNotice implemented, but I don't think it's fitting here because of the wording ("the following list"). While that could be fixed, maybe we don't need the FederationMissingNotice at all, as the "offline" badge in the FederationNotice already conveys the necessary information:

I suggest to remove the FederationMissingNotice here and will do so if nobody says something else in the next day or two.

(Also, I will align the styling so that they both display the list as an <ul>.)

[m-mohr]

See the following comment: #102 (comment)

A change from "list" to "data" should make it work.
The missing and offline flags are usually be the same but come from a different data source, so having both information has still some meaning.

Switching to list items makes sense.

[christophfriedrich]

With the changed text and aligned layout it looks like this:

IMO the new text makes it okayish, but not great. Is the collection metadata really "incomplete" just because a backend is not available? Why does the rendering of an online/offline report depend on whether all of the federation backends report the collection I'm currently viewing? Why is it a FederationNotice with a "Federation" heading when the content is not really about the fact that this is on a federation but about (limited) availability within that federation? IMO naming is not ideal in several places and the whole concept could be restructured (hence my initial writing in #101), but I guess we'll just keep it as it is now.

[m-mohr]

Fair enough, this can be improved in the future for sure.

A note with regards to the example though. The example looks pretty "bad" because it only lists EODC once in both components. Effectively this would basically never happen. If it's only hosted on a single backend and the data is incomplete, it means the data would not get delivered at all, so this would already be caught in the collection list by stating the EODC backend is offline and AUT_DEM would never occur in the list.

So to make your example more realtistic, there would need to be at least two backends of a three backend federation in the first box or the box would not be shown at all because all three backends support it. So in most cases you'd only see one of the boxes.