sumayahasancds
commented
1 year ago The work has been completed and changes were published on 20th March, 2023.
Limitation(s):
- The Product Comparator (Demo) application is utilising a serverless computing service called Lambda to retrieve data from the Register API that currently has Cross-Origin Resource Sharing (CORS) disabled. This is done by scheduling periodic data fetching instead of retrieving the data as needed in real-time. Once CORS is enabled, we will modify the application to retrieve real-time data on demand.
Product Comparator (Demo) is a proof-of-concept (PoC), developed and maintained by the Data Standards Body, to demonstrate how the unauthenticated CDR endpoints can be used for viewing and comparing CDR products, in addition to checking statuses and outages for data holders. This solution uses a datasource.json file to store data holder details across the sectors. Previously, Data holders needed to add/edit their organisations details in the Product Comparator Demo by either creating a Pull Request (PR) on the repository, or by creating an Issue on the repository to keep in sync with Register data.
Data Holder Brands and Data Recipient Software Products are required to call the Register APIs to obtain metadata that enables connection and registration between participants as well as obtaining the status of participants in the CDR. Through this enhancement, the product comparator (demo) application will discover public details of registered Data Holder Brands from the CDR Register.
This will eliminate the need for manual updates to the datasource.json file within the repository for those data holders who maintain a single "publicBaseUri"- the base path for all the public resource APIs (Unauthenticated Resource URLs) including Get Products, Get Status and Get Outages.
If there are different base paths for different public resource APIs from a data holder, the need for overriding rules will be required and maintained manually in a separate JSON file within the repository.