IQSS / IQSS/dataverse

Many log messages about externaltools key missing from bundle file

Open
#12,560 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?

Simply looking at a dataset will cause messages like these in the log (this is a sampling, but I think there's a message for every previewer installed):

[2026-07-24T18:23:01.829+0000] [Payara 7.2026.2] [WARNING] [] [edu.harvard.iq.dataverse.util.BundleUtil] [tid: _ThreadID=106 _ThreadName=http-thread-pool::jk-connector(5)] [timeMillis: 1784917381829] [levelValue: 900] [[
  Could not find key "externaltools.textPreviewer.displayname" in bundle file: ]]

[2026-07-24T18:23:01.838+0000] [Payara 7.2026.2] [WARNING] [] [edu.harvard.iq.dataverse.util.BundleUtil] [tid: _ThreadID=106 _ThreadName=http-thread-pool::jk-connector(5)] [timeMillis: 1784917381838] [levelValue: 900] [[
  Could not find key "externaltools.mapPreviewer.displayname" in bundle file: ]]

[2026-07-24T18:23:01.856+0000] [Payara 7.2026.2] [WARNING] [] [edu.harvard.iq.dataverse.util.BundleUtil] [tid: _ThreadID=106 _ThreadName=http-thread-pool::jk-connector(5)] [timeMillis: 1784917381856] [levelValue: 900] [[
  Could not find key "externaltools.spreadsheetPreviewer.displayname" in bundle file: ]]
  • When does this issue occur?
    When looking at a data set page.

  • What happens?
    The log ends up getting many messages every time a dataset page is loaded, which are innocuous, but super noisy.

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

  • What did you expect to happen?
    I would expect no messages from these, as the key-value pair should be provided to us.

I could not find where these are called from in the code, but I would expect not to see these messages, or have the external previewers provide the necessary mapping of these by default. Perhaps this request should be on the external tools repo - should the GDCC external tools repo provide a properties file to handle these?

Which version of Dataverse are you using?
6.10.1, but I've also seen this in 6.6

Any related open or closed issues to this bug report?
Not that I'm aware of

Possible Work around
One could supply the necessary key/values in the Bundles.properties file, but it feels like that shouldn't be necessary.

Or maybe we could just add a default for the current known external previewers to the Bundles file - if they are not used, that should be innocuous, and then if someone installs the previewer, they won't get these messages.

Screenshots:

No matter the issue, screenshots are always welcome.

To add a screenshot, please use one of the following formats and/or methods described here:

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

Start by tracing the BundleUtil warnings triggered while loading a dataset page, then inspect Bundles.properties and the external previewer mappings. Determine whether the keys belong in Dataverse or the external tools repository; done means dataset page loads no longer produce missing-key warnings without a manual workaround.

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
Quiet
Clarity
Needs clarification
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.