Skip to main content

As there is still missing a button that hides a public dataset from catalog, we’re trying to do a workaround.
For that, we would like to incorporate a public dataset of our secondary workspace, which isn’t publicly promoted, into a dashboard/code-editor’s page of our primary workspace.
 

Has someone tried something similar? Has it worked out?

My first thought was to do it via “domain” attribute of “ods-dataset-context” widget, but that didn’t work out:
 

<ods-dataset-context context="test"
                     test-dataset="test-index-dataset"
                     test-domain="https://myseconddomain.opendatasoft.com/"
                     >
</ods-dataset-context>

Thanks for your ideas :)

Hello Domi,

The method you’re using is the right one.

The best way to find out why this is not working would be to go to the developer tools of your browser, on the network tab, and filter on the dataset name, which should query the dataset endpoint of the API.

Would you be able to share any errors you find here, or the lack thereof?

Thanks

Hi Thomas,

thanks for your help.
I checked it, authorization failed, so I got a 401 status code. Beginner error, my dataset was set private.

After that, I tried two things, both worked out for me. In the end, I want the portal to be private, thus the second alternative is my preferred one.

  • I switched the “hidden” portal to be public
  • As I described in the message above, I want the portal really to be hidden. So it should be private. I created an apikey with my account and changed the code to 
    <ods-dataset-context context="test"
                         test-dataset="test-index-dataset"
                         test-domain="https://myseconddomain.opendatasoft.com/"
                         test-apikey="myapikey"
                         >

    Since the dataset was set private, it didn’t work out, when I tried this before. Yeah…

Thank you for your help though, leaded me to the solution :)

Best regards
Domi

Terms & ConditionsCookie settingsAccessibility statement
Huwise Terms & Conditions Cookie settings