Saved Search inconsistencies around unpublished datasets
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Found by @kcondon during testing of #7447
Performed a search, got X results.
Added as a saved search to a brand new DV, only showed Y results (Y bring less than X).
Looking at it further, the missing results were for harvested datasets (should we include these?).
But the other missing where (some) unpublished datasets. Why only some? Well, the going hypothesis (from looking at both code and results) is that:
• Unpublished datasets cannot be directly linked
• however, when unpublished datasets in a linked, published dataverse are indexed, they get indexed as links.
This seems inconsistent and we should establish consistent rules.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin by reproducing the X-versus-Y result difference when saving a search to a new DV. Compare harvested and unpublished datasets, including unpublished datasets in linked published dataverses, and agree on consistent inclusion rules; done means saved-search results follow those rules.
Written by the indexing model from the issue text.
Assessment
- Domain
- search
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100