Ali Khalili

One idea would be to store all the given properties of a component with a unique ID. Then we can use the container component to send those properties to that...

Hi @NielsHoffmann you can customise the parameters per triple store. For GraphDB, the config can be found at https://github.com/ali1k/ld-r/blob/master/services/utils/helpers.js#L170 just add the JWT as an optional parameter there and customise...

See the conceptual model at [http://ld-r.org/docs/pluginAuth.html](http://ld-r.org/docs/pluginAuth.html) In some of the publications, the detailed process is described: [http://research.ld-r.org](http://research.ld-r.org) in short, the selectors are similar to the ones used in the configurations.

for the web server caching we can use the Nginx caching https://www.nginx.com/blog/nginx-caching-guide/

Can you check [https://github.com/ali1k/ld-r/blob/master/services/utils/helpers.js#L170](https://github.com/ali1k/ld-r/blob/master/services/utils/helpers.js#L170) to see how read/write behavior for GraphDB is defined?

in the fact configuration you can use the ldr:position property which would sort the selected properties. Have you tried that?

I think the issue is that for dynamic datasets, the LD-R always used `ClioPatria` as default triple store and then you need to go to the configurations and change the...

I don't see any config about the username, password here. You should edit this in your server config (click on the configurations icon). You should know the difference between static...

this means you cannot connect to the SPARQL endpoint that hosts your configurations! check your config for `'http://ld-r.org/configurations': {` in your server.js file. And use `username` instead of `user`

Not necessarily as LD-R is just a UI on top of a SPARQL endpoint. If the connection is not established, the UI can still run but with error messages. And...