Hello,
The new content table view is working only partially for our datasets.
Here are the details:
High level view not displaying:
https://climatedata.imf.org/datasets/72e94bc71f4441d29710a9bea4d35f1d/explore
About page displaying correctly
https://climatedata.imf.org/datasets/72e94bc71f4441d29710a9bea4d35f1d/about
However, if from the About page you click on View Table it leads to https://climatedata.imf.org/datasets/72e94bc71f4441d29710a9bea4d35f1d/explore which does not display
Layer data displaying correctly (by adding _0 to the dataset ID)
https://climatedata.imf.org/datasets/72e94bc71f4441d29710a9bea4d35f1d_0
Thank you,
Alessandra
Solved! Go to Solution.
@CIDAdminwe just released a fix for this issue. Please take a look and let us know if you continue to see issues!
Thank you!
Thanks for letting us know about this issue. Can you tell me more about how you accessed this item? It appears that everything is loading correctly from search.
Ah nevermind, I am able to reproduce the bug. It appears that we're losing the correct url between /explore and /about. We will work on a fix.
Thank you Patrick. We have constructed the links with [hub site]/datasets/[Item ID]
From the search it seems to go directly to the table layer (ie the link with the added _0 at the end)
Shouldn’t it lead to the higher level
/datasets/[Item ID]/explore ? Or is that intentional?
The intention is for a human readable url to load rather than item or layer ids, but we can't always create those urls based on org configuration. We use the layer id for feature/map services in order to allow for multi-layer services to render correctly, so it should be expected that you may see `_0` appeneded at times depending on the underlying data source.
@CIDAdminwe just released a fix for this issue. Please take a look and let us know if you continue to see issues!
Thank you!