Kergomard, Stephan [skergomard], 7 NOV 2025: I think this is a bad idea, as a feature that is additional/optional in most cases is presented center stage and takes a lot of space. I would kindly ask you to find a less obtrusive place to present this.

Schmitz, Tim [tschmitz], 7 NOV 2025: As a consequence of the already accepted Allow Deactivation of LOM-Tab/Subtab, the 'Content Sharing' tab can be deactivated in the Administration. The 'Organizational Metadata' tab is only shown when appropriate, like the Custom Metadata and Taxonomy subtabs in the current Metadata tab, so both of the new tabs would only be shown when they are actually useful. Since there are not many installations where both LOM and Custom Metadata is in use, users with Edit Settings permission would on most installation not see an additional tab, but one or the other.

The 'Content Sharing' tab would increase the number of tabs shown to users with read permission only (but, again, only on installations where LOM is actually useful), but this would serve to structure the information given to these users more clearly, instead of throwing everything into bloated aggregation screens (like the current Info tab). I think simply counting up tabs misses the point here, especially since this is a step in the direction of eventually being able to abandon the Info tab.

I'm not sure why 'All or Nothing' deactivation of the 'Content Sharing' tab would be a bad thing. What parts would you like to be able to toggle individually?

Samoila, Oliver [oliver.samoila], 07 NOV 2025:
Thank you very much for a solution that, as I understand it, should also enable the important information from the ‘Info’ tab to find a new home. In my view, this will then support the cases in which this information is needed. This is also how I understand ‘especially as the “Metadata” tab has become more and more important for OER scenarios’.

What I cannot see in the proposed solution is how to avoid overloading all the scenarios in which ILIAS is used without a focus on OER.Reference is made here to the ‘Allow Deactivation of LOM Tab/Subtab’ feature, but there is no guarantee that this would be implemented at the same time. Maybe it will be. Maybe it won't. If not, a lot of users will be confronted with new tabs with long titles and their need for attention.

I would therefore like to suggest that, in analogy to cross-sectional functions such as ‘Competencies’, ‘Badges’, ‘Custom Metadata’ and others, these functions be intentionally activated in the “Settings” tab of an object. Then the ‘Content Sharing’ tab can be displayed and used accordingly. Depending on the scenario – and not for everyone who has not asked contact with it or wants it for their users.
(This would also mean that no global decision-making would be required for a platform.)

Schmitz, Tim [tschmitz], 7 NOV 2025: I agree that this feature should not be implemented without Allow Deactivation of LOM-Tab/Subtab, I'm fine with making that a strict requirement. I also like the idea of a LOM-checkbox on Settings screens, it makes sense to follow this established pattern. I think this functionality is offered by Object component, so the feasability to implement the checkbox right now depends on the roadmap there, but I'd be open to include it in this feature. Thanks for the suggestion!  

Kergomard, Stephan [skergomard], 10 NOV 2025: Thank you very much for your explanation. I do still not believe this is good enough. All of this is far too complicated for what we want to achieve. Starting with the issue that nobody should care about the difference of LOM and Custom Metadata and taxonmies. This to me sounds like a distinction without a difference. I would again kindly ask you to reconsider the whole thing. Independently of this, I would see two additional requirements: