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
This feature request is rather a question of possibility:
Recently I am dealing with file with a rather large number of differenct column names and row counts. This makes choosing the identifier quite a lot more difficult in my opinion.
Cube Creator does give a warning message if the observation identifiers are not unique and this made me wonder.
Is there a way to maybe give a reference to the row/line number where the identifiers are not unique?
This would make the process of fixing the issue a low easier but I am also not aware how Cube Creator is able to determine the non-uniqueness of the identifiers, so I might be completely on a wrong track here.
The text was updated successfully, but these errors were encountered:
[...] how Cube Creator is able to determine the non-uniqueness of the identifiers
By definition, every observation must have exactly one value for each of its dimensions. When an identifier is not unique, some observations will end up merged together, and thus having multiple values for properites. Cube Creator runs a query over the transformed data
Unfortunately, at the moment there is no SPARQL UI for cube creator's database. It would have been easiest to link to that precise query.
This feature request is rather a question of possibility:
Recently I am dealing with file with a rather large number of differenct column names and row counts. This makes choosing the identifier quite a lot more difficult in my opinion.
Cube Creator does give a warning message if the observation identifiers are not unique and this made me wonder.
Is there a way to maybe give a reference to the row/line number where the identifiers are not unique?
This would make the process of fixing the issue a low easier but I am also not aware how Cube Creator is able to determine the non-uniqueness of the identifiers, so I might be completely on a wrong track here.
The text was updated successfully, but these errors were encountered: