Cubes (INT) not usable in vizualize (INT)

[PDumasBAR]

Describe the bug
Cube seems ok, but not usable by Visualize
Cube checker says some elements are missing but they seem defined

Affected functionalities (all that apply)

• CSV Mapping
• Transformation
• Publishing
• Other

Relevant links
Cube-Creator Project BFE_OGD104
Cube checker Project BFE_OGD104

To Reproduce
Steps to reproduce the behavior:

1. Go to Cube_Creator
2. Open project OGD104 (Jana Stojanovic)
3. Goto tab Publication
4. Click the link to Visualize in the last publication
5. Follow the link to Cube Checker (bottom right)
6. See the missing elements

• No Shape (not verifiable in the Cube-Creator)
• Unknown status undefined (set in the Cube-Creator)
• Cube lacks the predicate schema:workExample https://ld.admin.ch/application/visualize (set in the Cube-Creator)

Expected behavior
The cube is selected in Visualize and the user can create a graph based on it

Screenshots

Desktop (please complete the following information):

• Windows 10
• Edge

Additional context
OGD104 is not the only cube from Jana that Visualize doesn't see (OGD106, OGD101, etc.).

[tpluscode]

I cannot explain what's happening. At least on two occasions, visualize actually opened fine and I managed to publish a visualization: https://int.visualize.admin.ch/en/v/hhsqDqJgvDiu

Mostly it does fail to load though. I double checked the cube checker results:

1. Shape does exist (https://s.zazuko.com/efe5zh)
2. Status is Published (https://s.zazuko.com/3pCF8XZ)
3. Visualize link is present (https://s.zazuko.com/pCPga7)

I don't think this is a problem on cube creator's side. Ideas, @ptbrowne?

[ptbrowne]

To get the last version of the cube, we send a request from the client to lindas.admin.ch/query, it seems like now we get a CORS error ?

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://lindas.admin.ch/query. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 503.

[ptbrowne]

It's not a CORS issue, but a 503 from lindas.admin.ch/query preventing us from getting the latest IRI.

[tpluscode]

I was about to say. @ludovicm67 would that be visible in trifid logs maybe?

[ptbrowne]

Apparently it's identified https://zulip.zazuko.com/#narrow/stream/32-bar-ld-ext/topic/forgot.20the.20status.20page.20for.20lindas.2Eadmin.2Ech/near/326193

[ludovicm67]

Last week we did the big jump to provide the new version of Trifid on LINDAS.
There was a CORS issue that was reported and that was fixed quickly.
The Trifid instance was also crashing, which was leading to 503 errors that you saw.
We managed to stabilize it last week also.
That's what I can say from my side.

Can you check if the issue is still there?

[PDumasBAR]

Hi Ludovic,
No change !
The cube checker says the same elements (shape, status and workExample) are missing in this cube Cube-Creator Project BFE_OGD104 and other cubes (OGD101, OGD106, OGD111) from Jana.

This behavior is not constant. I was able to work once with OGD111 in visualize, but only once out of 5 tries.

[tpluscode]

@ptbrowne would you have another look into the checker and the guards which are in place when loading the visualization UI?

As you see in my earlier comment, the queries do find all the cube data in Lindas, so I don't think cube creator is to blame. Also evident by the fact that every now and then a visualisation can be created successfully.

[ludovicm67]

As said also, the mentioned issues about the Trifid instance at Lindas (CORS and 503) are fixed and it looks stable.
So the issue should be caused by the Trifid instance from there.

[ptbrowne]

I wonder if visualize-admin/visualization-tool#1014 will fix the problem, it seems the "sometimes it works", "sometimes it doesn't" could have been caused by the datasource being saved to localhost and then reused on subsequent loads.