API for project metadata synchronisation with RDMS

[sandepat]

Is your feature request related to a problem? Please describe.
RDMS needs to display and manage projects consistently with DAISY, but currently lacks a stable, documented way to retrieve complete project metadata for synchronization.

Describe the solution requested
Provide a stable, documented read-only API to fetch project lists and metadata (project ID, name, owners, roles, status). RDMS will only consume this data; DAISY remains the single source of truth with no write access from RDMS.

Describe possible alternatives
Manual exports or ad-hoc endpoints, though these are not suitable for reliable or near real-time synchronization.

Other info context
This is for RDMS–DAISY integration; read-only access is sufficient and preferred for governance and data integrity.

[vildead]

@sandepat can we already define exactly which fields from the project entity are required? https://github.com/elixir-luxembourg/daisy/blob/develop/core/models/project.py

This api will set the schema to use for exchange of the information among our tools (DSS, RDMS, ingestion module, ELN, etc.) - for developers - do we have some standard schema to use? DATS seems to be rather domain specific and too detailed. We had also this: https://github.com/elixir-luxembourg/json-schemas, but it was never used widely...

[vildead]

It looks like there is already an API used by DSS, correct?

[vildead]

Its in place. But authorization is done via globla API key

This should be fixed in future. The doc should also be created at that time.

[sandepat]

@vildead

RDMS Required Fields

Minimum Required

• acronym - Project ID (iRODS collection name)
• title - Project name
• local_custodians - Data owners (for permissions)

Recommended

• description - Project description
• start_date, end_date - Project timeline
• has_cner, has_erp - Compliance flags
• contacts - Project contacts

Schema Approach

Should be simple - flat JSON.

{
  "items": [{
    "id": 123,
    "acronym": "PROJECT_X",
    "title": "Full Title",
    "description": "...",
    "local_custodians": [{"name": "...", "email": "..."}],
    "start_date": "2024-01-01",
    "end_date": "2026-12-31"
  }]
}

The existing /api/projects?fields=acronym,title,description approach works well (each tool requests only what it needs).