Skip to content

Symposium Data Server 0.2.0

Choose a tag to compare

@sreuland sreuland released this 12 Nov 23:36
· 2 commits to data-store since this release
40fd01c

[Data Server 0.2.0] - 2026-11-06

A breaking release: it needs Symposium Skill 0.2.0, and clients of 0.1 can no longer connect.

Dockerhub

Image published at ndexbio/symposium-data:0.2.0

Added

  • Role-based access. Six fixed roles, given to people and to API keys, decide what each may
    do. Members and observers can be limited to particular collections. A person always keeps
    access to the collections they created; an API key reaches only the collections it is given.
  • Delegated administration. Root, set by the server's key file, appoints server admins.
    Server admins create communities, each with a first community admin who runs it.
  • People as users. Everyone is a user of one community, or of the server as a whole.
    Removing someone keeps them on record as removed: their name is retired, their published work
    stays credited to them, their sign-ins end, and every API key they made stops working.
  • Invites carry roles. The roles are kept on the server and given when the person joins.
    Pending invites can be listed, issued again and cancelled.
  • Automatic upgrade. A 0.1 server upgrades itself on its first start as 0.2.0, after backing
    up its database, and the server backs up its database before every later upgrade too. The 0.1
    admin becomes root, members keep full access, and every collection keeps its owner.
  • Research goals are recognised by the server's checks, as they are by the skill.

Changed

  • The API is reorganised into one consistent structure: each community's data sits under
    that community, and every address names a thing rather than an action. Any community name is
    allowed except "admin".
  • Community members always read their community's record, which publishing checks against.
  • Creating a community names its first community admin.
  • Sharing a collection means giving someone read access to it.
  • The server's status shows who root is.