Filtering digital twins based on history/timestamp

[agg3fe]

Overview

Purpose here is to retrieve only the shells that have been created after given timestamp,
so that consumer does not have to fetch and process all the shells every time, enabling more efficient and resource-saving operations.
Below mentioned two APIs would have this additional feature.
example :
GET /shell-descriptors?createdAfter=2021-01-01T00:00:00Z
GET /lookup/shells?createdAfter=2021-01-01T00:00:00Z

Explain the topic in 2 sentences

The consumer of DTR can provide the timestamp as query param to API, and fetch only shells created after that timestamp.

What's the benefit?

Enabling more efficient and resource-saving operations

What are the Risks/Dependencies ?

• Issue raised with IDTA

Detailed explanation

Current implementation

There is no option to filter the result based on timestamp.

Proposed improvements

Adding timestamp for filtered out result.

Feature Team

Contributor

• @agg3fe
• @shijinrajbosch
• @thomas-henn

Committer

• @agg3fe

User Stories

• Issue 1, linked to specific repository
• Issue 2, linked to specific repository
• Issue 3, 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)

[agg3fe]

This issue belongs to https://github.com/catenax-eV/sig-roadmap/issues/407

[stephanbcbauer]

was presented during open planning 25.09