Currently, when you click the Binder button on a dataset with that external tool installed (e.g. my dataset on Harvard Dataverse)...

... you get an error:

{
    "message": "An unexpected error occurred on the server.",
    "type": "internal"
}

I reached out the to person who runs this service at girder.hub.yt and they said we should deploy our own equivalent solution that transforms https://girder.hub.yt/api/v1/ythub/dataverse?datasetPid=doi:10.7910/DVN/TJCLKP&siteUrl=https://dataverse.harvard.edu to https://mybinder.org/v2/dataverse/10.7910/DVN/TJCLKP/ for example. It makes sense. We never intended for it to be a long term solution.

Short term, perhaps we could create and deploy and equivalent rewrite service and adjust our guides...

... to point at docs we write for the new service. Currently, our docs point here:

• Find a place for DV external tool manifest redirecting for binder data-exp-lab/girder_ythub#10

Longer term (or as an alternative), we could work on this issue:

• Support putting variables in the path of a URL for external tools #9345

That way, we wouldn't need to rely on any rewrite service at all. Our external tool framework would be able to construct the URLs that mybinder requires with the DOI in the path instead of in a query parameter.