Skip to content

Link between NOMAD OASIS and NOMAD Central

General

Currently every OASIS is just a clone of the central repository. They are not linked together, not even through simple pings. In addition to simple links, it is necessary to define how OASES can differ from the central installation (in their version, their data, their user rights, ...). This may be communicated to central, too. In this issue, we outline these challenges and provide a road map for implementation and discussion.

Current GIT Issues related to OASIS (2022-05-24)

Requirements: LINK

  • Use case 1: Send telemetry data to central in regular intervals. This is discussed in {## Requirements: Telemetry}
  • Use-case 2: send data buckets + metadata. This is discussed in section {## Requirements: Data LINK}

Requirements: Telemetry

  • Which data should be sent?
    • Users registered
    • Data uploaded, stored
    • Number of searches
    • OASIS location
  • Do we need fine-grained info about site-access? This may be a security/leak risk that some may not like.
  • See #820 (closed)

Requirements: Soft constraints / Installation

  • Central: be careful with DDOS attacks from "too many / malicious OASIS links"
  • LINK is opt-out, enabled by default
  • OASIS owners can disable LINK in a config
  • See roles, #757 (closed)
  • The fact that each OASIS sends telemetry data by default MUST be communicated clearly, also how to disable it
  • We must be careful with "user data processing" requirements (GDPR). Aggregated data should be fine, but maybe some telemetry data can be used to identify users (link clicks, etc.).

Requirements: Data LINK

  • Also called "Synchronization"
  • Send data buckets
  • Send metaschema information, when they are stored in files
  • How to send new metaschemas defined in python? Not send at all?
  • Versioning of data: what if metaschema in the OASIS is newer/older than the one in central?
  • See #784 (closed)
  • See #585 (closed)