websites/dennogumi.org-archive
Archived
1
0
Fork 0
Code Releases Activity

Second round, clean up http:// links with {{ site.url }}

Browse source
This commit is contained in:
Luca Beltrame 2015-05-16 12:27:23 +02:00
parent 788e4609f6
commit a6570a4144
122 changed files with 278 additions and 278 deletions
Download patch file Download diff file Expand all files Collapse all files

4
_posts/2011-06-29-pykde4-queries-with-nepomuk.markdown
View file

@ -16,7 +16,7 @@ tags:
- python
---
In one of my previous blog posts I dealt with [tagging files and resources with Nepomuk](http://www.dennogumi.org/2010/10/pykde4-tag-and-annotate-files-using-nepomuk). But Nepomuk is not only about storing metadata, it is also about _retrieving_ and _interrogating _data. Normally, this would mean querying the metadata database directly, using queries written in SPARQL. But this is not intuitive, can be inefficient (if you do things the wrong way) and error prone (oops, I messed up a parameter!).
In one of my previous blog posts I dealt with [tagging files and resources with Nepomuk]({{ site.url }}/2010/10/pykde4-tag-and-annotate-files-using-nepomuk). But Nepomuk is not only about storing metadata, it is also about _retrieving_ and _interrogating _data. Normally, this would mean querying the metadata database directly, using queries written in SPARQL. But this is not intuitive, can be inefficient (if you do things the wrong way) and error prone (oops, I messed up a parameter!).
Fortunately, the Nepomuk developers have come up with a high level API to query already stored metadata, and today's post will deal with querying tags in Nepomuk. As per the past tutorials, the full source code is available [in the kdeexamples module](https://projects.kde.org/projects/kde/kdeexamples/repository/revisions/master/changes/bindings/python/nepomuk/nepomuk_tag_query_example.py).
@ -122,7 +122,7 @@ Lastly, we want to get some _results_ out of this query. There are different met
First we convert the query to a nepomuksearch:// url, which then we pass to KIO.listDir, to list the entries. Unlike [my previous post on KIO](http://www.dennogumi.org/2011/01/pykde4-retrieve-data-using-kio), this job emits entries() every time one is found, so we connect the signal to our search_slot method. We also connect the job's result() signal in a way that it will disconnect the job once it's over.
First we convert the query to a nepomuksearch:// url, which then we pass to KIO.listDir, to list the entries. Unlike [my previous post on KIO]({{ site.url }}/2011/01/pykde4-retrieve-data-using-kio), this job emits entries() every time one is found, so we connect the signal to our search_slot method. We also connect the job's result() signal in a way that it will disconnect the job once it's over.