UnifiedViews / Core

UnifiedViews
https://www.poolparty.biz/agile-data-integration
Other
30 stars 7 forks source link

Unclear semantics of the stored metadata for files #106

Closed tomas-knap closed 10 years ago

tomas-knap commented 10 years ago

Regarding the documentation, please explain the format of generated metadata as well.

I have a pipeline which extracts three files from the folder, then loads the data to SPARQL endpoint. The resulting metadata is not clear to me:

screen shot 2014-08-11 at 2 25 42 pm

1) http://linked.opendata.cz/resource/odcs/internal/pipeline/exec/363/dpu/271/du/1 http://unifiedviews.eu/AbstractWritableMetadataDataUnit/containsGraph http://linked.opendata.cz/resource/odcs/internal/pipeline/exec/363/dpu/271/du/1

Such triple does not make much sense, A contains A ?

2) Why is the URL file:/opt/working/exec_3632497748545236288134/ used? I would rather see the symbolic name instead of exec_3632... in the URI

3) I do not understand these writeGraphs, containGraphs predicates. Also do not know why there are 4 contains graphs, 3 write graphs.

ghost commented 10 years ago

You should not see such triple as you describe. Please consult me tomorrow. What you see are not metadata! It is internal data, something is wrong.

On 08/11/2014 02:36 PM, Tomas Knap wrote:

Regarding the documentation, please explain the format of generated metadata as well.

I have a pipeline which extracts three files from the folder, then loads the data to SPARQL endpoint. The resulting metadata is not clear to me:

screen shot 2014-08-11 at 2 25 42 pm https://cloud.githubusercontent.com/assets/3014917/3875546/f321d084-2152-11e4-9aaf-786f8ce22cfa.png

1) http://linked.opendata.cz/resource/odcs/internal/pipeline/exec/363/dpu/271/du/1 http://unifiedviews.eu/AbstractWritableMetadataDataUnit/containsGraph http://linked.opendata.cz/resource/odcs/internal/pipeline/exec/363/dpu/271/du/1

Such triple does not make much sense, A contains A ?

2) Why is the URL file:/opt/working/exec_3632497748545236288134/ used? I would rather see the symbolic name instead of exec_3632... in the URI

3) I do not understand these writeGraphs, containGraphs predicates. Also do not know why there are 4 contains graphs, 3 write graphs.

— Reply to this email directly or view it on GitHub https://github.com/UnifiedViews/Core/issues/106.

tomas-knap commented 10 years ago

https://cuni-test1.comsode.eea.sk/unifiedviews/#!PipelineEdit/38, run 363

tomas-knap commented 10 years ago

The reason why this bug emerges was that the transformer in the middle of the pipeline did not produce any data..and since there was no context, sesame used as default context the whole db (every pipeline exec = one db), so that is the reason why I saw these metadata

The bug does not appear if the pipeline produces some data.

ghost commented 10 years ago

bug,