Saved Search improvements
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Out of scope for performance related issue, so adding as new:
• For saved search we should track a few more things:
- the datetime the saved search was created
- the datetime the saved search was last run (which we could then use, for example, to run them in the order of the most stale)
• Since linking a dataverse returns everything within the dataverse (via indexing) we should not allow users to create a saved search that just links all the objects with a dataverse.
Differences when linking a dataverse vs creating a saved search:
- you also get the dataverse as a card
- you get results immediately (after reindex complete) instead of having to wait for the saved search timer to run
- removing the link removed all the objects
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
Start by locating the saved-search implementation and the code handling dataverse links. Determine where saved-search creation and execution are handled, then define the metadata and restriction behavior described in the issue; the issue names no files or tests, so the completion criteria need clarification before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100