[TRACE-X] Make parts table mass data ready

[rogocof]

Overview

As a user I want to easily filter all parts which interests me for tracing down even a large data sets.

Explain the topic in 2 sentences

The current approach filtering is cumbersome and not convenient, when a user wants to trace down a bulk of parts which for example might have quality issues. That is why we need a more advanced approach to filter including filtering with the goal filter even with large filter criteria like a set of hundreds of ids.

What's the benefit?

• More convenient searching
• Making the table ready to filter even for large input criteria sets
• Make the filtering understandable and repeatable

What are the Risks/Dependencies ?

• Search performance for large datasets to be analyzed
• No dependencies

Detailed explanation

It is important reorganize the current filter options in an user friendly way. We want to propose multiple enhancements like an advanced search filter menu, an optimized search bar and optimized user information like the display of the current filter in a user friendly as well as caching and persistence of last filters.

Current implementation

Non consistent approach of quick filters, global and local table filters.

Proposed improvements

• Advanced Search
  

• Optimized Search Bar

• Search with a large set of ids via clipboard or import

• Explain current applied filter

• Saved last search

Feature Team

Cofinity-X

Contributor

• @rogocof
• @mkanal
  UX-Design:
  @Cofinity-UX
  @sophiepotyka

Committer

• @mkanal
• @ds-mwesener
• @ds-lcapellino

User Stories

• Issue 1, linked to specific repository
• Issue 2, linked to another specific repository

Acceptance Criteria

• Criteria 1
• Criteria 2
• Criteria 3

Test Cases

Test Case 1

Steps

1. Do something
2. Click something
3. Add something

Expected Result

1. Expectation
2. Expectation
3. Expectation

Architectural Relevance

The following items are ensured (answer: yes) after this issue is implemented.

In the context of the standards 126 and 127, typically only one is applicable, depending on the specific use case. Please cross out one of the two standards that does not apply.

• This feature aligns with our current architectural guidelines
  • Data Sovereignty: All data sharing activities across company boundaries follow the Catena-X Regulatory Framework, in particular the Data Exchange Governance, and the Dataspace Protocol via a compliant Connector (like the tractusx-edc or similar, see Connector KIT)
    • CX-0010 Business Partner Number
    • CX-0013 Identity of Member Companies
    • CX-0018 Data Space Connectivity (EDC)
    • CX-0049 DID Document Schema
    • CX-0050 Framework Agreement Credential
    • CX-0149 Verified Company Identity
  • Interoperability: Digital Twins are used (compliant to the Digital Twin KIT and the Industry Core KIT)
    • CX-0001 EDC Discovery API
    • CX-0002 Digital Twins in Catena-X
    • CX-0018 Data Space Connectivity (EDC)
    • CX-0126 Industry Core: Part Type 2.0.0
    • CX-0127 Industry Core: Part Instance 2.0.0
  • Data Format:
    • The data model is based on a published Semantic Model
• The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the overarching architecture
• Potential risks or conflicts with existing architecture has been assessed

Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)

Additional information

• I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)