Draft fairregister service architecture

Meeting 2022-03-10

Users register and login via keycloak.
We will have databases for works metadata and user metadata.
We develop microservices with an API for each task.
Each frontend then connects to the microservice.
The nextcloud app will work like the OnlyOffice App (like in faircloud.eu when opening a document) - it just forwards the file to an iFrame with the fairregister service.
Users can select where to store the metadata and the file.
We will also need a fulfillment microservice which manages the subscriptions.

Darstellungen mit PowerPoint in faircloud:
https://faircloud.eu/nextcloud/index.php/s/D2s4Lqp7F6jk6D4

Selections during the registration process

Save Metadata // metadata is always hashed and stored (legal certainty)
@ (x) faircommons DB (default)
@ (x) IPFS (default) // metadata hash into IPFS; work is not public

Save File // the work does not necessarily have to be stored in the database; if the work is not stored in the database, the user is responsible for its preservation (e.g. nextcloud)
( ) encrypted // file can be saved encrypted
@ ( ) faircommons file system
@ ( ) IPFS // work is public and can be downloaded by others
// works can be stored freely up to a certain quota, then a package is required

After the registration
Blockchain (optional)
@ ( ) Ethereum
@ ( ) Solana
...

( ) create a NFT (optional) // wallet required; payment options

Current faircommons architecture

Architecture: https://faircloud.eu/nextcloud/index.php/s/ECfzpT7pbeYQZLD

Event Flow: https://faircloud.eu/nextcloud/index.php/s/LMocjAjL5J8L6H7