Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Dataverse] Additional filters - Cross filter #230

Open
ChaimaaZaoui opened this issue May 9, 2023 · 5 comments
Open

[Dataverse] Additional filters - Cross filter #230

ChaimaaZaoui opened this issue May 9, 2023 · 5 comments
Labels
feature 🤌 new features Ready for TechSpec Ticket to be pulled into Technical specification column

Comments

@ChaimaaZaoui
Copy link

ChaimaaZaoui commented May 9, 2023

Feature: [Dataverse] Additional filters - Cross filter

As an end-user of the portal on the .../dataverse page,
I want to cross filter the dataverse
So that only items having the metadata I previously selected in a filter are to be selected in the next filter

Acceptance criteria

Scenario 1 : Cross filter

Given that I am an end-user navigating the portal using a desktop
And I want to cross filter
When I select an item on a filter,
Then the selectable items in the rest of the filters must meet the criteria of the first selected item and so on
And the items that doesn't meet the criteria are hidden

When I select an item in resources
Then only the applicable filter to the resources are to be shown.

Scenario 2 : Cross Filter application in dataverse

Given that I am an end user navigating the portal on .../dataverse page
When I select a criteria in a filter
Then the system should retrieve the current resources that have that criteria in their metadata in the ontology
And the system should detect according the first filter on the metadata, the possible criteria in all the other filter that could be selected
And display only the resources on the right hand-side of .../dataverse page
And the UI will hide the non-corresponding criteria as in #196 (comment)

Environment

Additional informations

None.

┆Issue is synchronized with this Wrike task by Unito

@ChaimaaZaoui ChaimaaZaoui added the feature 🤌 new features label May 9, 2023
@ChaimaaZaoui ChaimaaZaoui self-assigned this May 9, 2023
@ChaimaaZaoui
Copy link
Author

Estimation to be done the 17th, please prepare the technical specification

@ChaimaaZaoui
Copy link
Author

Hey team! Please add your planning poker estimate with Zenhub @0xLodz @AnjaMis @ErikssonJoakim @lolottetheclash

@ChaimaaZaoui
Copy link
Author

Please add your planning poker estimate with Zenhub @amimart

@ChaimaaZaoui
Copy link
Author

Please add your planning poker estimate with Zenhub @ccamel

@ChaimaaZaoui
Copy link
Author

Note that this ticket is of high complexity, and could take over a week of dev even with peer programming

@ChaimaaZaoui ChaimaaZaoui removed their assignment May 17, 2023
@ChaimaaZaoui ChaimaaZaoui added the Ready for TechSpec Ticket to be pulled into Technical specification column label May 31, 2023
@AnjaMis AnjaMis moved this to 📋 Backlog in 💻 Development Sep 29, 2023
@AnjaMis AnjaMis moved this from 📋 Backlog to 📆 To do in 💻 Development Sep 29, 2023
@ccamel ccamel moved this from 📆 To do to 📋 Backlog in 💻 Development Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature 🤌 new features Ready for TechSpec Ticket to be pulled into Technical specification column
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant