IQSS / IQSS/dataverse

Error 500 when creating a new dataset using a default template with Custom Terms (Docker - 6.11)

Open
#12,590 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Type: Bug
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

What steps does it take to reproduce the issue?

I ran a new clean instance of dataverse 6.11 using the official docker images. I used two different images and the bug was the same in both:
6.11-noble-r4
6.11-noble

I used the docker compose given as example to make sure none of my custom bootstrap configurations were breaking the instance.

  • When does this issue occur?
  1. Create a New Dataverse Template
  2. In the template "Terms", select "Custom Dataset Terms"
  3. Mark Template as "Default"
  4. Go to "New Dataset"
  • Which page(s) does it occurs on?

New Dataset page

  • What happens?

When going to "New Dataset", an error page pops up with an error 500 Internal Server Error - An unexpected error was encountered, no more information is available.

  • To whom does it occur (all users, curators, superusers)?

All users

  • What did you expect to happen?

To be able to create a new Dataset with a default template with custom terms.

Which version of Dataverse are you using?
6.11

Any related open or closed issues to this bug report?
No

Screenshots:
Default template:

Image

Default template has "Custom terms":

Image

When going to create a new Dataset:

Image

The 500 error occurs:
Image

As a side note, if I leave the template as non-default, I am able to select the template from the creation page and successfully create the dataset:

Image Image Image

Are you thinking about creating a pull request for this issue?
Help is always welcome, is this bug something you or your organization plan to fix?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce with the 6.11-noble Docker image and the documented docker compose quickstart: create a default template with Custom Dataset Terms, then open the New Dataset page. Compare this with selecting the same non-default template; done means the default-template flow opens without an HTTP 500 and permits dataset creation.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, java
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.