Maestro V5 - Song compatible

[leoraba]

Summary of request

Part of #279
This request focuses on enhancing the indexing capabilities to support the following scenarios: indexing the entire repository (all studies/organizations), a specific study/organization, or an individual document. The source of data for these operations will be Song, and this functionality aligns with ongoing business processes.

Details

• Endpoint Support: Maestro should expose REST endpoints to handle various levels of indexing operations:
  • Index Entire Repository: POST /index/repository/{repositoryCode} – Triggers indexing for the entire repository associated with the given repositoryCode.
  • Index Specific Study: POST /index/repository/{repositoryCode}/study/{studyId} – Initiates indexing for a particular study within the specified repository.
  • Index Specific Document: POST /index/repository/{repositoryCode}/study/{studyId}/analysis/{analysisId} – Handles indexing for a specific document or analysis within a study.
• Library Functionality: In addition to REST endpoints, Maestro should provide functions that allow these indexing operations to be invoked programmatically when used as a library.
• Data Source Integration: Maestro should leverage Song endpoints to fetch the necessary data for indexing. This will ensure compatibility and efficient data retrieval from the Song system.
• Environment Configuration: Song parameters, such as host, port, and authentication credentials, should be configurable through environment variables to simplify deployment and management.
• Scalability: Maestro must be equipped to handle and efficiently index large volumes of data, ensuring performance and reliability even for substantial datasets.