Feature Request/Idea: allow recursive indexing of collections
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Feature Request
The /api/admin/index/dataverses endpoint indexes the collection but not its contained datasets. It might be nice to allow ?recurse=true or something similar, to allow more surgical re-indexing without traipsing through the DB or constructing a list of identifiers from the API then generating appropriate index API calls.
What kind of user is the feature intended for?
Sysadmin
What inspired the request?
We updated a custom metadata block today, and opted to re-index everything (~2 hrs, by clearing timestamps) rather than generate a list of the 79 datasets involved. It would be nice if the /api/admin/index/dataverses API endpoint could optionally recurse through the collection for us.
Any open or closed issues related to this feature request?
None that I found.
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 tracing the /api/admin/index/dataverses endpoint and its current collection-indexing flow. Define the behavior of an optional recurse=true parameter, including how contained datasets are discovered and indexed, while preserving the existing non-recursive behavior. Done means a collection can trigger targeted indexing of its datasets through the API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100