Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/AllianceBioversityCIAT/alliance-research-indicators-client/llms.txt

Use this file to discover all available pages before exploring further.

The Notifications page at /notifications is your inbox for activity across Alliance Research Indicators. Every event that affects a result you own or are watching arrives here in real time — no manual refresh needed. The application maintains a persistent WebSocket connection from the moment you sign in, so new notifications appear the instant the server emits them.

​
How real-time delivery works

When you authenticate, the Angular application connects to the WebSocket gateway via Socket.IO and registers your identity (user_id, first_name, and platform). The WebsocketService then listens on two channels:
  • notifications — result-level events such as status changes and review outcomes
  • alert-<platform> — platform-wide broadcast messages from administrators
Both channels deliver their payload as an in-app toast notification at the bottom of the screen. The Notifications page collects these events into a persistent feed so you can review them later. If the WebSocket connection drops — for example due to a network interruption — the application continues to function normally using REST. Notifications sent while you were disconnected appear the next time the page is loaded.

​
Notification types

The Notifications page is divided into two tabs:

​
Updates

Updates are notifications about result lifecycle changes:
  • Result submitted — a colleague has submitted a result that you are a reviewer for
  • Result updated — someone has edited a result that you own or are watching
  • Result accepted — a MEL Regional Expert has accepted a result you submitted
  • Result returned with feedback — a result you submitted has been returned for revision
Each update item shows the initiating user’s avatar and initials, the action verb, the result title and code, and how long ago the event occurred.

​
Requests

Requests are notifications that require a response from you:
  • Contributor request — a colleague from another initiative is asking to link their result to one you own as a co-contributor
Each request item shows a Review button that takes you directly to the relevant result, and a Decline button to reject the request without opening the result.

​
Filtering notifications

Within each tab, three filter buttons let you narrow the list:
FilterShows
UnreadNotifications you have not yet opened
ReadNotifications you have already viewed
AllEvery notification regardless of read status
After submitting a result for MEL review, switch to the Notifications page and set the filter to Unread. When the reviewer accepts or returns your result, the event appears here immediately — you do not need to open the result itself to check its status.

​
Notification item actions

Each notification in the feed links directly to the relevant result. Clicking the result title or the Review button (on requests) navigates you to /result/<platform>-<code> and opens the result editor. A more options menu (⋮) on each item provides additional actions such as marking as read or dismissing the notification.
Notifications are platform-scoped. If you work across multiple federated platforms (for example, you have accounts in both Alliance Research Indicators and PRMS), each platform maintains its own notification feed. Cross-platform result events are surfaced through the platform you are currently signed into.

Submitting results

Learn the review flow that triggers notification events

Roles and permissions

Understand which notification types each role receives

Build docs developers (and LLMs) love

Get started for freeTalk to us