Digital Registries Feedback

Owned by Wes Brown
Last updated: Apr 11, 2023
2 min read

Feedback Template

Source ID/Section

Comment

Feedback Type

Jira Issue

Source ID/Section

Comment

Feedback Type

Jira Issue

 

 

Now (blocker), Next (future publication), Feedback (question)

Create issue only once comment has been reviewed

DRS-35

Analyst must have capabilities to automate data exchange between databases internally and externally via API.

  • this should be a requirement for an information mediator, especially the mapping part

 

 

DRS-36

Analyst may have capabilities to use database schema templates so that the registry creation is faster.

  • this is redundant to scheme export/import (e..g to a repository/versioning)

 

 

DRS-22

Statistical queries: Produce standard statistical reports / Allow the analyst/user to analyze data collected in the system

  • this functionality belongs to Analytical & Reporting BBs

 

 

DRS-23

BB must enable client systems to process (CRUD) the database records via Open API services.

  • that sound’s like a general GovStack requirement for all building blocks

 

 

DRS-24

BB must have an Open API service list (Swagger) to visualize all API services and API service versions.

  • that’s a general GovStack requirement for all building blocks

 

 

DRS-26

Statistical queries via API.

  • that should be a general GovStack requirement for all building blocks

 

 

user story 4

Registry Schema API

  • These specs are all marked as must have in the current version - external developer access via API is not a typical use-case.

 

 

general

Are we talking about Registries or Data-Base Management Systems? Especially the paradigm of a fully programmable RDBMS without any business logic does not meet real world requirements and would systematically exclude most existing Digital Registry DPGs where the value lies in configurable best practice algorithms for specific registry types e.g. patient registers or social beneficiary registers.

 

 

section 6.5

[A. Laponin]

Please, align it with requirements in the template: this section shall have list of requirements, i.e., what system has to do and what user has to be able to accomplish using the system.

Now

DR-88: Update the Functional Requirements to Align to the TemplateDone

section 6.5

[A. Laponin]

The section 6.5 is something else and probably can be moved to the section.

Now

DR-87: Move 6.5 Coverage Map from the Functional Requirements SectionDone