Trusted Remote Storage and files not accessible by Dataverse

[Matti Lassila]

I wonder, is it intentional that Dataverse tries to access the file in Trusted Remote Storage when attaching a TRS-located file to the dataset, even if setting files-not-accessible-by-dataverse has been set to false as instructed in configuration guide?

My goal is to link to a dataset landing page in a target system, instead of actual file. When storageIdentifier in JSON payload points to an actual file which can be accessed by Dataverse, I do not get an error. When the storageIdentifier points to a landing page, I get the following error. I'm running Dataverse 6.10.1 .

#|2026-04-16T16:03:13.803+0300|SEVERE|Payara 7.2026.3|edu.harvard.iq.dataverse.api.errorhandlers.ThrowableHandler|_ThreadID=102;_ThreadName=http-thread-pool::jk-connector(3);_TimeMillis=1776344593803;_LevelValue=1000;|
_status="ERROR";_code=500;_message="Internal server error. More details available at the server logs.";_incidentId="1cf5601d-2d55-4174-abbf-f03761f2d41e";_internalError="ArrayIndexOutOfBoundsException";_requestUrl="https://xxxxx/api/v1/datasets/:persistentId/add?persistentId=doi:10.5072/FK2/BRLYML";_requestMethod="POST"||#]

[#|2026-04-16T16:03:13.803+0300|SEVERE|Payara 7.2026.3|edu.harvard.iq.dataverse.api.errorhandlers.ThrowableHandler|_ThreadID=102;_ThreadName=http-thread-pool::jk-connector(3);_TimeMillis=1776344593803;_LevelValue=1000;|
java.lang.ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0
at edu.harvard.iq.dataverse.dataaccess.RemoteOverlayAccessIO.retrieveSizeFromMedia(RemoteOverlayAccessIO.java:172)

My TRS config is:

-Ddataverse.files.vault.type=remote
-Ddataverse.files.vault.label=Vault
-Ddataverse.files.vault.base-url=https://internalurl.xy/records
-Ddataverse.files.vault.remote-store-name=Remote dataset
-Ddataverse.files.vault.base-store=file
-Ddataverse.files.vault.upload-out-of-band=true
-Ddataverse.files.vault.public=true
-Ddataverse.files.vault.ingestsizelimit=0
-Ddataverse.files.vault.download-redirect=true
-Ddataverse.files.vault.files-not-accessible-by-dataverse=false
-Ddataverse.files.vault.remote-store-url=https://internalurl.xy/info
-Ddataverse.files.vault.remote-store-name=Vault

[James Myers]

Sounds like a problem with the documentation - files-not-accessible-by-dataverse

should be true when you're using a landing page. 

-- Jim

---

From: dataverse...@googlegroups.com <dataverse...@googlegroups.com> on behalf of Matti Lassila <matti....@gmail.com>
Sent: Thursday, April 16, 2026 10:55 PM
To: Dataverse Users Community <dataverse...@googlegroups.com>
Subject: [Dataverse-Users] Trusted Remote Storage and files not accessible by Dataverse

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/0e3fe896-4c4a-4649-a887-01c532017f28n%40googlegroups.com.

[Matti Lassila]

Changing files-not-accessible-by-dataverse to true had no effect. I still get an error which indicates that Dataverse is trying to gauge file size using HTTP HEAD which fails when target system is not accessible or does not return Content-Length header. It seems that getting TRS to work with an isolated storage system requires that files-not-accessible-by-dataverse is utilized also in the file add stage. I'll open a bug in issue tracker as Philip suggested in Zulip.

[Florio Orocio Arguillas]

Hi friends,

 

Is there a way to increase the size of the Terms of Use metadata field?

 

I’d like it to show all five (5) paragraphs of the Data Use Agreement when downloading a file.  Right now, it shows only half of the 1st paragraph and requires scrolling to read all five.

 

Let me know if there is a way to resize it to show all five. 

 

Thanks.

 

Best regards,

 

Florio

 

[Julian Gautier]

Hi Florio,

This screenshot shows an example of what you mean, right?

This is the popup that folks see when they try to download a file in a dataset that has custom dataset terms, like a Data Use Agreement that someone pasted into the Terms of Use field.

Julian Gautier (he/him)

Product Research Specialist, IQSS

Interested in helping test Dataverse? Sign up for user experience research

[Florio Orocio Arguillas]

Hi Julian,

 

Exactly!

 

Is there a way to configure Dataverse so that someone downloading a file from a dataset sees the full Terms of Use (or a very large chunk of it, but can scroll)?  Your example showed only 4 lines, about the same as ours.

 

Let me know.

 

Thanks.

 

Florio

 

 

From: 'Julian Gautier' via Dataverse Users Community <dataverse...@googlegroups.com>

Sent: Tuesday, April 21, 2026 11:37 AM
To: Dataverse Users Community <dataverse...@googlegroups.com>

Subject: [Dataverse-Users] Re: How to increase the size of Terms of Use metadata field

 

Hi Florio,

 

This screenshot shows an example of what you mean, right?

 

 

This is the popup that folks see when they try to download a file in a dataset that has custom dataset terms, like a Data Use Agreement that someone pasted into the Terms of Use field.

 

Julian Gautier (he/him)

Product Research Specialist, IQSS

Interested in helping test Dataverse? Sign up for user experience research

 

On Monday, April 20, 2026 at 12:37:23 PM UTC-4 fo...@cornell.edu wrote:

Hi friends,

 

Is there a way to increase the size of the Terms of Use metadata field?

 

I’d like it to show all five (5) paragraphs of the Data Use Agreement when downloading a file.  Right now, it shows only half of the 1st paragraph and requires scrolling to read all five.

 

Let me know if there is a way to resize it to show all five. 

 

Thanks.

 

Best regards,

 

Florio

 

--

You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/1adc8a8f-1f2b-48c4-9f25-0c01f68da8c1n%40googlegroups.com.

[Julian Gautier]

No, there isn't an official way to make the popup show more of what's entered in the Terms of Use field, or in other fields that depositors can add text to when defining their custom terms.

We had this same concern when designing this popup, so I'm glad you've brought this up! Could you create a GitHub issue about this? I looked through the issues in https://github.com/IQSS/dataverse/issues and couldn't find one describing this pain point.

I wonder if an easier possible solution for your case might be to turn that Data Use Agreement into one of the options in users see when depositing datasets. Then when someone tries to download a file in a dataset that has that license, the popup shows a link that the user can click to take them to a page where there's more space to show the license/Data Use Agreement.

Here's an example of this from the QDR repository:

Clicking that blue "Standard Access" link takes users to https://qdr.syr.edu/policies/qdr-standard-access-conditions, where the whole page can be used to show what users need to know about using the data. 

The Dataverse installation guide has more about this at https://guides.dataverse.org/en/latest/installation/config.html#configuring-licenses.

[Florio Orocio Arguillas]

Thanks, Julian.

 

This is good to know.

 

I also submitted a feature request to address this issue via the GitHub link you provided.

 

Best regards,

 

Florio

 

 

From: 'Julian Gautier' via Dataverse Users Community <dataverse...@googlegroups.com>

Sent: Tuesday, April 21, 2026 12:18 PM
To: Dataverse Users Community <dataverse...@googlegroups.com>

Subject: Re: [Dataverse-Users] Re: How to increase the size of Terms of Use metadata field

 

No, there isn't an official way to make the popup show more of what's entered in the Terms of Use field, or in other fields that depositors can add text to when defining their custom terms.

 

We had this same concern when designing this popup, so I'm glad you've brought this up! Could you create a GitHub issue about this? I looked through the issues in https://github.com/IQSS/dataverse/issues and couldn't find one describing this pain point.

 

I wonder if an easier possible solution for your case might be to turn that Data Use Agreement into one of the options in users see when depositing datasets. Then when someone tries to download a file in a dataset that has that license, the popup shows a link that the user can click to take them to a page where there's more space to show the license/Data Use Agreement.

 

Here's an example of this from the QDR repository:

 

 

Clicking that blue "Standard Access" link takes users to https://qdr.syr.edu/policies/qdr-standard-access-conditions, where the whole page can be used to show what users need to know about using the data. 

 

The Dataverse installation guide has more about this at https://guides.dataverse.org/en/latest/installation/config.html#configuring-licenses.

--

You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/1dc29d57-8baa-410a-b6a5-0ee35e32bee3n%40googlegroups.com.

[Julian Gautier]

Great!

[Betsy]

Hello, 

Just in case this helps those folks that manage the feature requests on GitHub, I put in a related feature request back in January: https://github.com/IQSS/dataverse/issues/12117. My request was more broad, but definitely related the one Florio is requesting. 

Take care,

Betsy

Johns Hopkins Uni

[Julian Gautier]

Hi Betsy. Yes I think it's really helpful! Thanks! I tried looking for GitHub issues that described this pain point but couldn't.

I've noted in the GitHub issue that Florio created at https://github.com/IQSS/dataverse/issues/12347 that the one you created is related.