Please integrate the new CSS related koosearch umn/api-ref document within the existing CSS document space #308
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infra/otc-metadata#308
Reference in New Issue
Block a user
Dear eco-systems squad,
this issue is created on behalf of the discussion with Vladi how to deal with the new “Koosearch” UMN+API-REF Koosearch is new and a part of the existing “Cloud Search Service (CSS)”. It was agreed with Gergö that those documents should be handled as additional document-types within the CSS document “folder”.
So here the request details:
Full name of the (existing) service: Cloud Search Service
Service abbreviation: CSS
Which document types should be supported: - koosearch-umn and koosearch-api-ref (for now) - since koosearch is part of CSS (and not in dedicated component) those 2 koosearch related document should appear additionally under the CSS document overview (as boxes same as the CSS UMN/API-REF) - this is suggested by me and aligned with + agreed by Gergö.
The path of documentation on doc-exports: UMN: koosearch UMN：docs/doc-exports#1519 koosearch API：docs/doc-exports#1520
Which squad will be responsible for the service: BigData&AI SQuad
In which area the service should land: Since it is no dedicated new service/component those document should land under “Big Data and Data Analysis” - within the CSS/Cloud Search Service space.
Many thanks in advance and all the best,
Matt