Asset Registry System (ARS): Development Phase 3, Work Package 1

[PipBrewer]

Work Package 1: Updates to Asset Registry Service storage protocol

Work Package Overview
This work package outlines the change required for deploying the Asset Registry Service (ARS) on DeIC resources. It requires the ARS to change the protocol used to upload assets to the Asset Registry Service from SMB to HTTPS. It is also required to make the system more modular and extensible.

Description
Based on the recent knowledge about the resources received from DeIC for deployment of the Asset Registry Service, the SMB protocol used in the initial solution needs to be changed to HTTPS. This is because the Asset Registry Service and the Data Integration Module are not located in the same local network as DeIC (which is spread over several universities across Denmark). The change in protocol was decided to be the most optimal solution for the requirements.

This work package will be complete when the assets can be uploaded and retrieved via HTTP from ARS.

Estimated consultancy hours: 118 hours
Estimated internal hours (primarily BS): 10 hours
Estimated start date: 21/02/2024
Estimated end date: 25/02/2024

Extended requirements: https://github.com/NHMDenmark/DaSSCo-Tranche-1-work/tree/main/Asset%20Registry%20System%20(ARS)
Github board: https://github.com/orgs/NHMDenmark/projects/32

[PipBrewer]

https://github.com/NHMDenmark/DaSSCo-asset-service/blob/develop/documentation/meetings/2024-03-13-testing-and-bugs.md

[PipBrewer]

Status as at 06/01/2025 which was shared with Northtech on 20/12/2024 by KSP:

Originally estimated hours: 118
Currently billed hours: 244
Estimated hours remaining: 19
Status: 93% complete

This work package is almost complete. Three of the requirements for this may have a bit more work on then but are lower priority than most other work remaining. These are:

Requirement	Description	Hours Predicted	Github Ticket
1.17	Provide health status for the systems like ERDA, IDP, ARS on request	8	#43
1.18	Solution is scalable	3	#35
1.21	Https design should offer concurrency, offer optimal management of storage space	8	#43