eclipse-tractusx / sig-release

https://eclipse-tractusx.github.io/sig-release
Apache License 2.0
7 stars 6 forks source link

Extension of search function for sharing members to search for all Business Partners in the pool #603

Open rybtim opened 3 months ago

rybtim commented 3 months ago

Description

Currently, it's only possible for a Sharing Member to find company data of other Catena-X members via the Pool API. Also, it's only possible to search by name and BPN. It is required to find Catena-X business partners (not only Catena-X members) while creating new business partners in MDM systems of the Sharing Member via pre-defined extended search criteria, like country, city, street etc.

Pool data model and APIs MUST be adapted to include an extended search capability. Pool API standardization document MUST describe this extended search capability. BPDM Framework Agreement (bpdm.pool.*) MUST be adapted to allow Sharing Members to consume all the business partners known to Catena-X , instead of only the Catena-X members / data space participants. And a new data asset must be defined for that matter.

Impact

Additional information

jjeroch commented 3 months ago

Attention @rybtim : Upcoming PI Planning Preparation

As we gear up for the forthcoming PI Planning session, it is crucial that all features under consideration align with our established Feature Quality Standards and Definition of Done (DoD) guidelines. To ensure your feature is thoroughly prepared and stands a strong chance of being prioritized, please provide comprehensive documentation that includes the following components:

  1. Feature Summary: An executive overview that encapsulates the essence and objectives of the feature.
  2. Change Description:
    • High-Level Overview: A succinct synopsis of the proposed changes and their overarching impact.
    • Detailed Analysis: An in-depth exploration of the specific alterations, including a clear exposition of the anticipated impact on existing systems.
  3. Impacted Components: A list identifying all system components that will be affected by the feature implementation, accompanied by a brief explanation of the nature of the impact.
  4. Acceptance Criteria: A set of clearly defined conditions that must be met for the feature to be considered complete and acceptable.
  5. Test Scenarios: A detailed outline of test cases that cover all functional paths of the feature to ensure robust validation and verification.
  6. Risks/Dependencies

Please note that any feature submissions lacking these essential elements will not be eligible for consideration in the upcoming PI Planning. It is imperative that your documentation is both thorough and precise to facilitate a smooth and effective planning process.

Please let me know in case you have any questions

Grand-Thibault commented 3 months ago

@rybtim please add more to the description

rybtim commented 2 months ago

No implementation feature for R. 24.08. Handover to Expert Group plannend and moved to Inbox

stephanbcbauer commented 2 months ago

@rybtim added you as assignee because we need a contact person for every feature.

stephanbcbauer commented 2 months ago

Didn't think about it before, but since the feature is still in Inbox, the open decision label is not needed. Opinions?

JulianStoll commented 2 weeks ago

https://github.com/eclipse-tractusx/bpdm/issues/781