You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we build a cube containing custom-based dimensions (predicates), all metadata related to these predicates are only stored in the constraints part as shape information.
This has as an effect that if someone selects one of these predicates, she/he gets a 404 page because this predicate is not defined as such in th triplestore. I'm convinced that it would be easy to create a few triples in addition to the ones of the constraint to have a minimal description of these predicates. This will greatly enhance the understandability of the cube content, because the shapes in the constraint part are definitely not for end-users.
If we build a cube containing custom-based dimensions (predicates), all metadata related to these predicates are only stored in the constraints part as shape information.
This has as an effect that if someone selects one of these predicates, she/he gets a 404 page because this predicate is not defined as such in th triplestore. I'm convinced that it would be easy to create a few triples in addition to the ones of the constraint to have a minimal description of these predicates. This will greatly enhance the understandability of the cube content, because the shapes in the constraint part are definitely not for end-users.
Describe the bug
In this example, https://culture.ld.admin.ch/sfa/StateAccounts_Function/1/observation/OC1-F1-1951, the custom-based dimension https://culture.ld.admin.ch/sfa/StateAccounts_Function/function is not defined in the triplestore, even if this predicate has been documented in Cube Creator (see https://culture.ld.admin.ch/sfa/StateAccounts_Function/1/shape/#blank-5 in the constraint part of this cube).
I suggest that a minimal definition structure is built and stored.
Affected functionalities (all that apply)
Relevant links
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I think the minimal description could be the following one
https://culture.ld.admin.ch/sfa/StateAccounts_Function/function
a rdf:Property;
schema:name "Fonction"@fr, "Function"@en, "Funktion"@de, "Funzione"@de.
A link to the shape constraint could be eventually added.
Screenshots
Desktop (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: