infra/otc-metadata
16
0
Fork 13
Code Issues 5 Pull Requests 1 Packages Releases Wiki Activity

Please integrate the new CSS related koosearch umn/api-ref document within the existing CSS document space #308

New Issue
Open
opened 2025-05-08 11:47:13 +00:00 by matreche · 0 comments
matreche commented 2025-05-08 11:47:13 +00:00
Copy Link

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

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：https://gitea.eco.tsi-dev.otc-service.com/docs/doc-exports/pulls/1519 koosearch API：https://gitea.eco.tsi-dev.otc-service.com/docs/doc-exports/pulls/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
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
gate
Gate it
gate
Gate it
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
A200014817 ansideln cicd ikvrivis magnus otcbot proposalbot sgode smartyno tischrei vhasko vladimirhasko vladimirvshivkov vvshivko zuul
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: infra/otc-metadata#308
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?