Skip to content

Reports

FedMS reporting capability is built on Drupal Views. The default set of reports is available at:

1
/admin/reports

…and the FedMS-specific reports under:

1
/admin/content

…with views grouped by entity type.

Shipped views

Out of the box, FedMS ships these views (across the modules):

Federation views

View What it shows
views.view.orgs All organizations.
views.view.organizations A filtered org listing (per role).
views.view.content Group content overview.
views.view.event_sessions Sessions of an event.
views.view.upcoming_events Upcoming events per org.
views.view.upcoming_events_globally Upcoming events across all orgs.
views.view.group_media Media attached to a group.
views.view.group_members Members of a group.
views.view.group_memberships Membership records (with status).
views.view.group_users Users per group.
views.view.groups_unprocessed Events/sessions whose lifecycle flags haven't been processed — drives the cron-based task spawning.

Task views

View What it shows
views.view.entity_tasks Tasks per entity.
views.view.milestone_tasks Tasks grouped by milestone.
views.view.milestones Milestone overview.
views.view.user_sessions Sessions per user.

Profile views

View What it shows
views.view.who_s_new New users (Drupal core view, rewritten by FedMS).

Customizing reports

Content Managers can edit views and create new ones. To create a new report:

  1. /admin/structure/views/add.
  2. Pick the entity type (group, fedms_event, fedms_task, user, …).
  3. Configure filters, fields, sort, format.
  4. Save.

If you build a report that other Managers might find useful, save it as a config-exported view so it ships with the next deployment.

Exporting data

Most views support export via the views_data_export module — download as CSV, XLSX, JSON, or XML for offline analysis or for import into a BI tool.

To enable export on a view: edit the view → add a display → pick Data export → save.

Custom reporting

For reports that need joins or aggregations beyond what Views can express, write a custom controller in a site-specific module. See Developer guide → Architecture.

Audit logging

Beyond the views, FedMS captures detailed audit information:

  • Every content entity (events, sessions, tasks, attachments) is revisionable — every change is preserved.
  • Memberships are soft-removed — group_relationship.status records the current state without destroying the history.
  • ECA model executions can be logged at debug level (turn off in production).

The dedicated Activity logging feature is tracked at fedms/components/federation#22.

Performance

Some shipped views have pagination caps that aren't always sufficient — for example, the per-milestone task list shows only 10 rows. See fedms/support#64.

For heavy reporting, consider:

  • Setting up the Drupal Search API with a backend like Solr.
  • Disabling the pager on reports you regularly export in full.
  • Adding indices on hot columns (fedms_task.actionable, fedms_task.due, fedms_task.status).

Next steps