Ability to hierarchically organize multiple dataverse deployments
Open
Nobody has claimed this yet.
Feature: Search/Browse
Type: Suggestion
User Role: Superuser
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
We have two institutions with their own dataverse instances set up and running, and looking for the ability to create a super-verse treating these two existing apps as its sub-dataverses. I'm a bit confused whether it is supported.
Thank you for the great tool!
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
The issue names no files, tests, or entry points. First clarify whether a super-verse spanning existing Dataverse deployments is supported and document the required hierarchy and behavior; done would require an agreed implementation scope and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100