Traversing links in Fusion's advanced view of a resource resolves view in wrong bucket
- Dominant language
- Scala
- Stars
- 301
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
Traversing links in Fusion's advanced view of a resource resolves view in wrong bucket
**What part of Nexus is affected**
- [x] Fusion
- [ ] Delta
- [ ] CLI
- [ ] Documentation
**To Reproduce**
Steps to reproduce the behavior, e.g. for Fusion:
1. Go to https://bbp.epfl.ch/nexus/web/bbp/atlas/resources/https%3A%2F%2Fbbp.epfl.ch%2Fneurosciencegraph%2Fdata%2Fviews%2Fes%2Ftmd_similarity_aggregated_view
2. There are 4 views being aggregated, all with the same id, but in different buckets
3. Hover over all 4, and see that they are all resolve to the public/hippocampus one.
**Expected behavior**
Unsure what the expected behavior is in terms good user experience, but this isn't it, just in the sense that multiple matches through different buckets is valid from a data standpoint, so it should be handled?
**Screenshots**
Contributor guide
Research direction
Start by reproducing the linked Fusion resource in the advanced view and inspect how hovering the four aggregated views resolves their links. The fix should preserve the bucket associated with each valid match instead of resolving every view to public/hippocampus; confirm the behavior with a regression test if the relevant test location is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100