Closed ethieblin closed 1 year ago
Sure, go ahead ! See that other discussion on how to implement something similar but for the Jena full-text search syntax, it can give you pointers on where to start: https://github.com/sparna-git/Sparnatural/issues/447
What I will do is that I will create the necessary entries in the configuration ontology for you to plugin the widget code. But, without waiting for this, what you can do is modify the behavior of the GraphDBSearchWidget so that it generates the query you need: https://github.com/sparna-git/Sparnatural/blob/69a72c2fad840c1c39eeb84601bc1e95de123ce1/src/sparnatural/components/widgets/SearchRegexWidget.ts#L100
I think you are all set !
Quick question regarding the contribution: I see there is a "pretty" script in the package, however when I run it, it modifies a lot of files in the repository. Are there any coding rules (linting, formatting) I should follow to contribute ?
I don't use this "pretty" script from the package. Don't use it. There are no specific rules to follow. I trust your "bon sens". I use VSCode as dev environment.
Hello, I think there is a small typo in the URI of http://data.sparna.fr/ontologies/sparnatural-config-core/VirtuosoSearchProperty in the http://data.sparna.fr/ontologies/sparnatural-config-core, it uses a slash as delimiter but in the code you provided, it uses a #
Hello, I think there is a small typo in the URI of http://data.sparna.fr/ontologies/sparnatural-config-core/VirtuosoSearchProperty in the http://data.sparna.fr/ontologies/sparnatural-config-core, it uses a slash as delimiter but in the code you provided, it uses a #
Thanks this is fixed in the ontology
Hello,
We would like to discuss the addition of a new Subclass of SearchProperty, which would look like GraphDBSearchProperty, but for Virtuoso (bif:contains instead of the lucene queries). This would make Sparnatural a bit more Virtuoso-compatible. We propose to develop that feature for you, if you agree with the following proposal:
What we were thinking of for that new configuration would be:
This query processing would have the following advantages: