Community Catalogues

What are community catalogs?

Community catalogs are thematic or organizational subsets of the SSC that are curated by specialist communities, projects, or networks themselves. They use the shared technical infrastructure of the SSC, but retain their own profile with their own landing page, description, and responsible parties.

Possible usage scenarios

Research communities: Presentation of all relevant services related to a topic (e.g., research data management, laboratory infrastructure, method services), including contact points, consulting services, and documentation.

Service networks and projects: Visualization of networked services that are organized across universities, such as joint help desks, support structures, or coordinated service packages.

Thematic networks: Presentation of services, events, resources, and tools for specific topics such as “digital teaching,” “AI in research,” or “sustainability.”

Advantages for communities

Central visibility: All relevant offerings are presented in one place but remain integrated into the overall SSC inventory.

Own profile: Each community has its own landing page with a description, contacts, and specifically selected services.

Updatability: Content can be continuously maintained and adapted to new requirements by designated responsible persons without the need to set up a separate technical system.

Role in the overall SSC

The community catalogs complement the central SSC by providing guidance for specific target groups and highlighting cross-links between institutions, organizations, and projects. This allows users to search the entire SSC on the one hand and quickly find the most relevant offerings for them in “their” community view on the other.

A separate community catalog can be set up in the SSC by following these steps:

1. First, the application form for community catalogs (only available in German) must be completed in full and sent to redaktion.bua-shared-services@hu-berlin.de.
2. The application will then be reviewed by the SSC team for technical and formal compliance.
3. Once the review has been successfully completed, a separate WordPress instance will be created for the community in question and the admin access details will be handed over to the designated responsible persons.
4. If required, support can be provided during the rollout, for example with structural issues, initial content creation, or editorial work.

Questions and suggestions should be directed to the SSC team at the email address provided.