summaryrefslogtreecommitdiff
path: root/issues
diff options
context:
space:
mode:
authorArun Isaac2023-02-13 17:46:40 +0000
committerArun Isaac2023-02-13 17:46:40 +0000
commit83495cb2b34a0c3500a8d15089bc99ea175ce45e (patch)
tree191974f6590b1c24815ea37eb1af04c49f8d4e22 /issues
parent44cae596a9c0f195c4e21f198bf93d7f4cbb96f3 (diff)
downloadgn-gemtext-83495cb2b34a0c3500a8d15089bc99ea175ce45e.tar.gz
Close full text search issue.
Diffstat (limited to 'issues')
-rw-r--r--issues/full-text-search.gmi10
1 files changed, 10 insertions, 0 deletions
diff --git a/issues/full-text-search.gmi b/issues/full-text-search.gmi
index fac0040..4a32a18 100644
--- a/issues/full-text-search.gmi
+++ b/issues/full-text-search.gmi
@@ -14,3 +14,13 @@ Implement full text search on the dumped RDF using xapian. This may be a feature
We also considered that virtuoso supports full text search in SPARQL. But, the query syntax is not as natural as xapian, and there may be no stemming. So, this option was rejected.
=> http://docs.openlinksw.com/virtuoso/rdfsparqlrulefulltext/ Virtuoso full text search
+
+## Completion
+
+An initial full text search has been implemented. This initial implementation indexes data from the SQL database and provides an API to search that index. See the index-genenetwork script and the search API implementation in the genenetwork3 repository.
+=> https://github.com/genenetwork/genenetwork3/blob/main/scripts/index-genenetwork
+=> https://github.com/genenetwork/genenetwork3/blob/main/gn3/api/search.py
+
+In the future, full text search must index RDF rather than data from SQL. Please open a new issue or reopen this issue when working on that.
+
+* closed