(REQUIRED) Create a new register/database (via API or Web user interface);

Go to requirement

feature is on the roadmap for next project phase

(REQUIRED) Create and configure the schema of the register (API or Web user interface);

Go to requirement

(REQUIRED) Change schema configuration and publish the new version of the database and API services (API or Web user interface);

Go to requirement

(REQUIRED) Enter data to the register (API or Web user interface);

Go to requirement

(REQUIRED) View data records in the register (API or Web user interface);

Go to requirement

(REQUIRED) Update data in the register (API or Web user interface);

Go to requirement

(REQUIRED) Import/export data from/to external files;

Go to requirement

(REQUIRED) Import/export registry database schema;

Go to requirement

(REQUIRED) Create API services;

Go to requirement

(REQUIRED) View statistics (API or Web user interface);

Go to requirement

(REQUIRED) Inspect transaction log of registry data operations (API or Web user interface);

Go to requirement

To validate

(REQUIRED) Manage access to registry data. Authorize users to see and edit registry records or data fields (Attribute-Based Access Control management);

Go to requirement

(REQUIRED) Share data with other users via e-mail, or via a unique and secure Uniform Resource Locator (URL) sharing can be field level or record level.

Go to requirement

(REQUIRED) Search data from the register;

Go to requirement

(REQUIRED) Read data from the register;

Go to requirement

(REQUIRED) Create data in the register;

Go to requirement

(REQUIRED) Update data in the register;

Go to requirement

(REQUIRED) Delete data in the register;

Go to requirement

(REQUIRED) Validate if given content exists in specified register;

Go to requirement

To validate

(REQUIRED) Read statistics.

Go to requirement

To validate

(RECOMMENDED) Open Cancel mandatory requirement: "Cloud-native, i.e. Docker and Kubernetes". Digital Registries must have also an on-site installation option.

Go to requirement

(RECOMMENDED) Robust Operates in low-resource environments Cancel mandatory requirement: "Occasional power". In Digital Registries not possible, thus should be optional. This can be solved with backup power resources (UPS) and a generator that keeps the systems running without interruptions. Cancel mandatory requirement: "Low-reliability connectivity". Client-server systems are not reliable in this situation, instead additional hand held connection-less data capturing devices should be used and data reentered/uploaded to the servers when connection is restored (not covered in this version scope).

Go to requirement

(RECOMMENDED) Databases must not include business logic Cancel mandatory requirement. "no triggers/stored procedures shall be used". Some stored procedures may be needed for database record ID generation.

Go to requirement

(REQUIRED) Privacy and protection of user data Add mandatory requirement. The following requirement should be added to other Building Blocks' cross-cutting requirements: Each owner of the personal data (e.g. citizen) must be able to see who has looked at their personal data in the registry. All captured personal user data must be marked as “personal data”. Users can make requests to see the information/logs of accessing personal information. API must be available for authenticated users to see their own personal data audit logs.

Go to requirement