MS

DGRSDT Research Calls Platform

DGRSDT Research Calls Platform

Overview

National research-call platform for DGRSDT: multi-tenant calls, expert evaluation, financial selection and multi-year project follow-up.

The goal

Algerian research funding runs through calls: the ministry announces a programme, institutions and laboratories answer with consortium proposals, experts score them, a selection is made, and the funded projects are followed for years — progress reports, spending, final report.

Before this platform that whole chain lived in documents: a call published as a PDF, proposals sent by e-mail, evaluation grids circulated as spreadsheets, selections consolidated by hand, and follow-up in whatever format each institution kept. Nothing was comparable across institutions, nothing was traceable, and personal data moved in attachments.

The brief was to put the entire chain in one national platform:

  1. Publish calls — by institution, with a real calendar, documents, budget headings and an evaluation grid, not a scanned announcement.
  2. Receive proposals — a consortium dossier that is structurally complete before it can be submitted, not a PDF checked by hand.
  3. Evaluate and select — experts designated per proposal, scored against the call's own grid, with the outcome computed rather than discussed.
  4. Follow the projects — work packages, budgets, meetings, progress reports, final report, for the whole life of the grant.
  5. Stay lawful — Algerian law 18-07 on personal data is not decoration here: consent, encryption, retention, access requests and a register of operations are part of the product.

What was built

Institutions as tenants

Each institution ("plateforme") has a code, a director, a logo, an address and its own staff. Everything it creates — calls, proposals, experts, reports — lives inside its tenant. National administrators see everything; an institution sees only itself; a researcher is attached to an institution and sees only its calls. The isolation is enforced twice: at the query level and in the policies.

Calls with a real calendar

A call carries nine typed periods — submission, administrative validation, administrative appeal, final validation, expert assessment, expert appeal, final validation of expert results, financing, finalisation. Each period has dates and a flag saying whether a proposal may still be edited, so the Submit button exists only when the calendar allows it. Extensions are recorded next to the initial dates, never instead of them. An hourly command opens and closes calls on their own dates, through the same code path an administrator uses when clicking "activate", so the register of operations cannot tell the two apart — and the institution is notified either way.

The proposal dossier

A proposal is a project workspace, not a form: thematic areas and activities capped by the call, keywords, expected dates, work packages, objectives with weights and completion, tasks, partners, budgets by the call's own headings, required documents, members, invitations and join requests. A completeness engine lists every missing mandatory item in red; the status only becomes Ready to submit when the list is empty.

Evaluation and selection

Staff designate experts per proposal; each designation opens a report seeded with the call's grid — scored questions with a minimum and a maximum, plus priority factors with offered answers. An expert accepts or declines (conflict of interest), fills the grid with a comment per question, and submits. The result is computed against the call's two thresholds: a total below the minimum, or any answer below the critical minimum, fails the report. Two passing reports move the project to financial review; two failing reports reject it; the remaining reports are closed. Nothing about that rule is hardcoded in a controller.

Project follow-up

Once financed, the project gets its own panel at /project/{slug}: work packages, objectives and tasks, a meetings calendar, partners and their budgets, documents, members, progress reports per work package, financial reports and the final report. Institutions validate what they receive, and the whole thing is printable — a committee sheet purged of contact details, and a full Typst-compiled PDF report.

Administration, statistics, compliance

A national admin panel manages institutions, accounts, roles, calls, projects and the register of operations; a read-only statistics panel exposes indicators across institutions; data-protection requests have their own queue and their own e-mails. Consent is versioned, personal columns are encrypted with key rotation, files live on a private disk behind signed routes, records carry public ULIDs instead of integers, and retention is enforced by scheduled purges. Nightly encrypted backups run with an off-host copy and a freshness monitor.

Three languages

The interface, the e-mails, the notifications, the validation messages and the user manual exist in Arabic, French and English. Arabic is right-to-left with a self-hosted font — no font CDN, in line with the same law's stance on transfers abroad.

Architecture

Layer Choice
Backend PHP 8.4, Laravel 13
UI Filament 5, five panels — app (researchers, experts), project (funded project space), platform (institutions), admin (national), statistics (read-only)
Reactivity Livewire 4, Alpine.js
Tenancy Filament panel tenancy on Platform and on Project, a global scope keyed on the active tenant, policies re-checking membership
Data MySQL 8 / MariaDB 10.6, 119 migrations, 42 Eloquent models
Authorisation spatie/laravel-permission + 43 policies + per-institution roles
Files spatie/laravel-medialibrary, private disk, signed download routes
Output Typst for project PDFs, PhpSpreadsheet for multi-sheet reports, five Filament exporters
Ops Deployer, supervisor workers, scheduler cron, Laravel Pulse, nightly encrypted backups
Tests Pest 4, 102 test files on a dedicated MySQL schema

The decision that carried the most weight was to make the call the unit of configuration. Thresholds, grid, budget headings, documents and calendar all hang off the call, so a new programme is data entry rather than a deployment — and two institutions can run different rules on the same code.

Portfolio

Related work

Contact

Get in touch

Have a project in mind?
Just say hello.

Address

Sidi Bel Abbess, Algeria