• Information on current monitoring activities is available on the platform, as well as specialised information such as methodological standards, mapping instructions, reports and scientific publications.
• All relevant and available (meta-)data and information on nationwide biodiversity monitoring can be found and accessed via the platform.
• Biodiversity and monitoring data can be filtered and retrieved via various applications and are illustrated in the form of maps and graphics.
• Information on selected topics of biodiversity monitoring is provided in a form suitable for the target group, for example in the form of articles, videos and infographics.

• The portal serves the exchange between the different stakeholders in biodiversity monitoring.
• Needs-based tools and formats are provided to support those involved in biodiversity monitoring.

Key factors influencing the success of the portal are described after a trend and environmental analysis. This includes evaluating opportunities, synergies, goal conflicts, challenges, and risks. The initial unique selling points of the portal become apparent.

Stakeholders and users are surveyed regarding their needs and the value added by the portal. Initial content priorities are established.

Specific requirements are developed based on use cases.

Es wird eine klare Intention inklusive Kernbotschaften für das Portal definiert. Zudem werden die Vision, Mission, Kern- und Teilziele sowie Alleinstellungsmerkmale und Erfolgsfaktoren formuliert.

The content concept for the portal is elaborated, including recommendations for core functionalities, system architecture, and a timeline and capacity plan for implementing the basic version of the portal.

In addition to analysing the stakeholders and potential user groups, the portal's relevant subject areas were identified and described. These include politics, legal and regulatory framework conditions, information technology, cooperation options, science and society.

In addition, selected existing websites relevant to the Monitoring Centre's portal were analysed with regard to possible interfaces, functionalities and necessary differentiations from other portals, for example.

Essential questions for the further portal conception were derived in each case and will be taken up in the further process. Some fundamental questions are raised repeatedly, for instance:

• What niche does the portal occupy?
• How will it be used? How will it be different from existing initiatives?
• Should it be everything? Information AND data AND networking portal?

More than 800 people from the biodiversity monitoring community took part in the Monitoring Centre's survey on portal development, conducted between February and March 2024. Of these, 523 completed the full questionnaire.

Our aim is to create a portal that is user-friendly and provides relevant services in a reliable and sustainable way. The primary objective of this survey was to gather the general preferences and initial requirements of potential users for the content of a national biodiversity monitoring portal.

The respondents represent a wide range of professionals and interested parties from associations, academia, government, business and the general public. This diversity is reflected in the wide range of needs expressed, providing us with valuable insights into the diverse requirements of future users. First results are shown in the figures below. The interim report will provide more detailed results. 

In parallel to the survey, requirement assessment workshops and interviews were conducted to further define and refine the use cases. Through this process, over 200 user stories and best practice suggestions have already been collected. A wide range of needs were identified, which can be grouped into the following overarching categories:

• Provide access to data and filters
• Providing an overview of monitoring programmes
• Improve data quality and provide metadata
• Highlight collaborators and promote networking among stakeholders
• Evaluate data quality and usability
• Provide curated materials and information
• Develop APIs and standards
• Link existing structures
• Enable data contributions while maintaining data sovereignty

The following key messages emerged from the needs analysis for the further content development of the information and networking portal:

1. The portal should serve as a central hub for biodiversity monitoring by the monitoring community.
2. The portal should provide direction, highlighting the "biodiversity data and expert information scattered across different institutions".
3. The requirements and assumptions from the initial concept of the Monitoring Centre are validated by the needs assessment.
4. In addition to access to curated data and knowledge via the portal, which was mentioned by almost all participants, a (complementary) offer of active networking opportunities was mentioned less frequently.
5. There is a high demand for information on monitoring activities and their stakeholders, as well as for consolidated findings, in particular from nationwide monitoring programmes.
6. In a first basic version, consolidated information on existing data (where it is located, how to access it) is more important than direct access to raw data.
7. A powerful search and filter facility is essential.
8. Users expect scientific content on biodiversity status, trends and actions.
9. High data quality and timeliness are critical.
10. International information relevant to biodiversity monitoring in Germany should be integrated.
11. National and international cooperation is important, with strategic partnerships playing a key role.
12. Analytical tools are expected in the portal.
13. A step-by-step development of the portal is recommended, starting with a lean basic system that already provides significant added value.
14. From a technical point of view, the portal needs to enable exchange with other stakeholders and access to data and information. Standards and open interfaces should be used to achieve this.
     

The main findings from the development of use cases for the further design of the information and networking portal are as follows

1. Use Cases and User Stories: 130 use cases were developed based on user stories gathered from the needs assessment within the monitoring community and grouped into 13 functional areas (API, Operation, Data Entry, Expert Introduction, Main Application, Content Editing, Educational and Informational Materials, Monitoring Activities, User Community, User Management, (Raw) Data, Search/Information and Events).
2. Prioritisation: The use cases are divided into three priority levels: core version, future extensions and those outside the current focus.
3. Prioritisation criteria: Important criteria for prioritising use cases include benefit for the user, alignment with the Centre's objectives, representativeness, complexity, frequency of user requirements mentioned during the analysis, and cost of implementation.
4. Core functions of the basic version: The key functions for the first version of the portal are the main application (interface, landing page, navigation) and the search/information functions.
5. Key content themes: Detailed, filterable overviews of monitoring programmes, networking within the monitoring community and publication of results are the key themes for the initial content of the portal.
6. Modular architecture: The functional areas mentioned in point 1 will be integrated into modules to allow a step-by-step expansion of the portal.
7. Interface designs: High fidelity mockups (interface designs) have been created for key pages such as the home page, search page, detail page and a data story.
8. Non-functional requirements: Key non-functional requirements such as intuitive user navigation, clear interfaces, portal performance and accessibility have been outlined in initial designs.
9. System architecture defined: The first draft of the system architecture includes clearly defined user groups, a breakdown of system components and external systems.
10. External integration: Interfaces for import and export with external systems require technical and legal clarification, which will be further defined as the project progresses.

• The portal's role as providing direction and central hub is top priority.
• Focus on up to date, relevant content and best practice. Key topics: background information, overview of monitoring programmes and stakeholders.

• Quickly develop the basis system with the most essential features and content. Implement first, optimise later - avoid lengthy analysis phases and feedback loops.
• Recommendation: Stop collecting more requirements and focus on the first core issues.
• Develop (internal) prototypes for specific aspects.

Systematically keep content up to date and network to ensure regular updates and inclusion of current issues.

Communicate clearly and early on the content, goals, roadmap and value of the portal - both internally (within BfN, committees) and externally (monitoring community).

• Clear definition of responsibilities: Head office of the Monitoring Centre, BfN, external service providers.
• Establish editorial workflows.
• A dedicated, small portal team with defined roles and decision-making processes will minimise editorial complexity and enable rapid response to changes.
• Start testing immediately (technical test environment, ideally in-house).
• Document decision processes: Create an Architectural Decision Record (ADR) to document what was decided, when and how (path decision documentation).