Hi, We have based our data portal on the Globus Modern Research data portal.
Since late 2023, perhaps due to the move to Globus Collection v5, our data portal is no longer able to successfully transfer data. Our endpoint was migrated to a v5 Collection and it is working just fine outside of the portal. I went back to this repo (https://github.com/globus/globus-sample-data-portal) hoping to find some direction on what needs to be fixed. I also tried the Globus Sample Data Portal https://mrdp.globus.org/ I see the same error "Internal error" here too no matter what destination collection I use. The collections work just fine outside of the sample data portal. Attached is a screen shot of the error I see when I click transfer.
Is this sample data portal working for everyone else or is there an update that needs to be made? I've been assuming a change needs to happen in declaring the scope.
Thank you,
Heather
Hi Heather,
I think you're looking in the right place.
For the MRDP sample code, the best place to look to track changes is directly at the Pull Request history. [^1]
I see an update to the scope string used as a major part of #66, and there's a significant update (although it may look rather innocuous) in #70 because it updates the globus-sdk version used from 2.x to 3.x .
The scope string update from PR #66 introduces the use of a data_access scope, which is required for a GCS v5 Mapped Collection.[^2]
It's very likely that this is exactly the update you need.
If you run into trouble while trying to do this, please send along a sample of the logs for us to read through. You can send to `sup...@globus.org` if you're uncomfortable sharing log data with the public list, or if you feel uncertain about which parts of the logs might be sensitive.
The server error in the screenshot really just tells us "something went wrong", and we'll need a bit more detail to drive this to resolution.
Best,
-Stephen
---
[1]: We should add a changelog, but I think it's relevant that the MRDP sample doesn't change very frequently. And there aren't versions of the code, so any changelog would be continuous/rolling. Overall, it won't "feel like a product" because it's meant as a starting point/example. But you can read the PRs to see what changes you want to pull in, and I think that's a pretty sensible way to use the project.
[2]: You may see mention of v5.3 vs v5.4. For 99% of users, every GCS v5 is a v5.4 endpoint, so you can usually ignore v5.3 and lower.