Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing minimal custom-based dimensions metadata #1567

Open
1 of 4 tasks
JLCochardSFA opened this issue Jan 8, 2025 · 0 comments
Open
1 of 4 tasks

Missing minimal custom-based dimensions metadata #1567

JLCochardSFA opened this issue Jan 8, 2025 · 0 comments
Assignees
Labels
🐛 bug Something isn't working

Comments

@JLCochardSFA
Copy link

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)

  • CSV Mapping
  • Transformation
  • Publishing
  • Other: Cube content understandability

Relevant links

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

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):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]

Additional context

@JLCochardSFA JLCochardSFA added the 🐛 bug Something isn't working label Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants