fusepoolp3 / p3-dashboard Goto Github PK

Please update the default port on which the transformer starts according to https://github.com/fusepoolP3/overall-architecture/blob/master/default-ports.md

The widget shuold refresh without blocking.

I'm not sure where this issue belongs so I post it here. I just did a demo at ICT2015 and when I copied the BatchRefine config URI from the LDP interface it seems that I copied the URI with a leading space. When I add this to the transformer factory of BatchRefine it registers a transformer with the space which leads in a non-functioning transformer in the end.

It was surely my fault but I think this should be catched in the UI so it doesn't happen to others.

index.html contains:
var platformURI = "http://" + host + ":8181/ldp/platform";
For Virtuoso, LDP containers are rooted under /DAV
e.g. ":8181/DAV/home/fusepool/ldp/platform"
Although we could define a virtual directory /ldp and map /DAV/home/fusepool/ldp to it, it would be better if the parent directory of platform could be made configurable.

The sparql endpoint URI passed to P3Check.initP3Platform() uses a hardcoded path '/sparql/select'. Virtuoso uses '/sparql'. Again the sparql endpoint path needs to be configurable.

I can't see the situation when one has more than one such widget and need a title to distinguish them.

Not sure how many users actually use the multi-profile feature, but I guess I'm not the only one who's annoied by having to enter a configuration name AND a description when first starting the dashboard. What about having "default" as default name and not presenting any dialog?

Instead of providing an empty text field the test UI for transformers should query them and either provide autocomplete or probably better simply a list of supported input/output mime-types.

Indeed, the default port seems to be right in the repository ;-)
Could you please create a new release? Thanks!

Even though I configured some widgets they do not show up anymore on data.fusepool.info. The container is there, for example:

http://data.fusepool.info:8205/?defaultContainer=http://data.fusepool.info:8181/ldp/dcr/default-configuration/BAR-complete-pipeline

If you list that in the resource UI, everything looks fine.

The transformers do show up but not everytime in the UI.

I think the easiexst is to include it as a git submodule

The Readme should explain how to compile and how to run from the jar, mvn exec is for developer who know this shortcut anyway.

I was really confused that after my tests with BatchRefine all transformed files were the same like the input file. This is because I cannot specify the input type and default in BatchRefine seems to be CSV. Currently the requested Accept-header is */*so BatchRefine technically does it right I think.

I would propose that transformers should in this case output RDF as this is the main goal of P3 but we also need to be able to specify the output type in the widget UI.

See https://github.com/fusepoolP3/p3-autoconfiguration-tool/issues/3

The created subject URIs use the LDP server hostname/port, not the proxy hostname/port. The Dashboard expects subject URIs to contain the latter.

I've just listed it in https://github.com/fusepoolP3/overall-architecture/blob/master/default-ports.md

I configured an OpenRefine transformer as described in issue #9. When I create a widget on the dashboard for this transformer and upload a file, nothing seems to happen. I never see any request in the batchrefine log.

I can't find the definition of the ontology, don't know what it is for. Especially

<http://vocab.fusepool.info/wrldpc#type> "T-LDPC"

looks horrible. An LDPC is a TLDPC if it has an eldp:transformer, for expressing types there is rdf:type and the type should be an URI not a literal.

I created an OpenRefine transformer which works fine when I post data via curl. If I try to test the newly registered transformer in the Transformer test-UI it seems that neither the Accept Header nor the Content Type are properly set in the request.

Curl edition (which works):

 curl -XPOST -H "Accept:text/turtle" -H 'Content-Type:text/csv' --data-binary @20141205_AEG_ADL_ALOD_niv_doc-xlsx.csv http://sandbox.fusepool.info:8310\?refinejson\=http%3A%2F%2Fsandbox.fusepool.info%3A8181%2Fldp%2Fbla-json.json

The dialog looks like this:

In BatchRefine log I see:

batchrefine p3 14:14:47.135 [...BatchRefineTransformer] Origin:http://sandbox.fusepool.info:8200 (0ms)
batchrefine p3 14:14:47.135 [...BatchRefineTransformer] Connection:keep-alive (0ms)
batchrefine p3 14:14:47.135 [...BatchRefineTransformer] Content-Type:text/plain; charset=UTF-8 (0ms)
batchrefine p3 14:14:47.135 [...BatchRefineTransformer] Accept:*/* (0ms)
batchrefine p3 14:14:47.135 [...BatchRefineTransformer] Cache-Control:no-cache (0ms)
batchrefine p3 14:14:47.136 [...BatchRefineTransformer] Pragma:no-cache (1ms)
batchrefine p3 14:14:47.136 [...BatchRefineTransformer] ```