Update metadatablock logic to fail if dataverse collection does not exist
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
When uploading a metadatablock via tsv file, you can specify a dataverse collection (when you do, that block is only available in the subtree of the installation).
Currently, if you do this and the dataverse collection does not exist, the upload succeeds with the block being universally available. This issue is a suggestion to change the behavior, so it fails in this case.
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 metadata block TSV upload entry point and the logic that resolves a specified dataverse collection. Verify the behavior for a nonexistent collection, then add coverage showing that the upload fails instead of making the block universally available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100