GNOME Bugzilla – Bug 639556
Tracker find only folders
Last modified: 2011-04-25 06:59:07 UTC
"Continuation" of bug #639492. In 0.9.33 there were 127 results found: % time tracker-search websocket | wc -l 127 tracker-search websocket 0.04s user 0.00s system 28% cpu 0.150 total wc -l 0.00s user 0.00s system 0% cpu 0.141 total However in 0.9.34 there are 9, all of them are folders: % time tracker-search websocket | wc -l 9 tracker-search websocket 0.02s user 0.00s system 63% cpu 0.044 total wc -l 0.00s user 0.00s system 0% cpu 0.031 total
Please include a log or the list here, just providing stats like that isn't helpful at all. I don't know what data set you're using and I need to check the data is meant to be displayed in tracker-needle in the first place. Can you provide me with the output from tracker-search?
Results: file:///home/mpiechotka/Sources/WebKit/LayoutTests/http/tests/websocket file:///home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-linux/http/tests/websocket file:///home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-linux/websocket file:///home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-mac/http/tests/websocket file:///home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-mac/websocket file:///home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-win/http/tests/websocket file:///home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-win/websocket Previously there was: - A PDF I was interested in (on the first place) - A lot of source files
I see and are those all directories? if they're not, please tell me what tracker-info $url says about one of them. If they are directories then we simply don't list them in the first view, because only files are shown there and useful ones at that was the intention. There perhaps needs to be some clarity about the views.
All directories both in tracker and reality: % tracker-search websocket | grep file | xargs tracker-info | grep 'nie:mimeType' 'nie:mimeType' = 'inode/directory' 'nie:mimeType' = 'inode/directory' 'nie:mimeType' = 'inode/directory' 'nie:mimeType' = 'inode/directory' 'nie:mimeType' = 'inode/directory' 'nie:mimeType' = 'inode/directory' 'nie:mimeType' = 'inode/directory' % tracker-search websocket | sed -n 's@file://@@p' | xargs file /home/mpiechotka/Sources/WebKit/LayoutTests/http/tests/websocket: directory /home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-linux/http/tests/websocket: directory /home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-linux/websocket: directory /home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-mac/http/tests/websocket: directory /home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-mac/websocket: directory /home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-win/http/tests/websocket: directory /home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-win/websocket: directory
I just added folder support to that view. I am not sure how useful this is, this view is really intended to list real data, not organisational data like folder layout. The categories that view should support are: APPLICATIONS MUSIC VIDEOS DOCUMENTS MAIL IMAGES FOLDERS (now) We are likely to support other things like book marks and contacts in the future. I am changing the title of this bug since folders are not really documents. This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
I'm reopening as you misunderstend the bug (or I misunderstood your reply). Currenly *all* tracker finds is *folders* and it do *not* find *documents* (both in tracker-needle and tracker-search).
So you're missing a PDF and some sources? For the files in question, does tracker-info $file_uri show anything? PDFs and sources (.c files?) are usually listed as documents. Is it possible this is a configuration error? Running the following should give some clarity: tracker-control -r (this will reindex everything) /usr/libexec/tracker-miner-fs -v 3 The last command there should produce a log and output which we can use to find out if the files were found and ignored (which is what I suspect here). If you get no where can you attach this log here with the uri of the file you expect to be indexed and I will inspect it.
(In reply to comment #7) > So you're missing a PDF and some sources? > > For the files in question, does tracker-info $file_uri show anything? > % tracker-info "file://$HOME/Documentation/Magazines/Linux Journal/202.pdf" Querying information for entity:'file:///home/mpiechotka/Documentation/Magazines/Linux Journal/202.pdf' Unable to retrieve data for URI, 1.35: syntax error, expected `}' > PDFs and sources (.c files?) are usually listed as documents. Is it possible > this is a configuration error? > I don't think so - it happend after update of tracker > Running the following should give some clarity: > > tracker-control -r (this will reindex everything) > /usr/libexec/tracker-miner-fs -v 3 > > The last command there should produce a log and output which we can use to find > out if the files were found and ignored (which is what I suspect here). If you > get no where can you attach this log here with the uri of the file you expect > to be indexed and I will inspect it. Ok. As reindexing will take whole day (I assume it takes as long as initial) I'll do it as soon as I will be able to left computer running so long.
(In reply to comment #8) > (In reply to comment #7) > > So you're missing a PDF and some sources? > > > > For the files in question, does tracker-info $file_uri show anything? > > > > % tracker-info "file://$HOME/Documentation/Magazines/Linux Journal/202.pdf" > Querying information for > entity:'file:///home/mpiechotka/Documentation/Magazines/Linux Journal/202.pdf' > Unable to retrieve data for URI, 1.35: syntax error, expected `}' Hmm, can you try: tracker-info file:///path/to/home/Documentation/Magazines/Linux%20Journal/202.pdf I don't think it would work the way you tried it. > > PDFs and sources (.c files?) are usually listed as documents. Is it possible > > this is a configuration error? > > > > I don't think so - it happend after update of tracker > > > Running the following should give some clarity: > > > > tracker-control -r (this will reindex everything) > > /usr/libexec/tracker-miner-fs -v 3 > > > > The last command there should produce a log and output which we can use to find > > out if the files were found and ignored (which is what I suspect here). If you > > get no where can you attach this log here with the uri of the file you expect > > to be indexed and I will inspect it. > > Ok. As reindexing will take whole day (I assume it takes as long as initial) > I'll do it as soon as I will be able to left computer running so long. The whole day? That doesn't sound right. You're using Tracker 0.9? How many files/folders are you indexing and is your machine relatively modern?
(In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #7) > > > So you're missing a PDF and some sources? > > > > > > For the files in question, does tracker-info $file_uri show anything? > > > > > > > % tracker-info "file://$HOME/Documentation/Magazines/Linux Journal/202.pdf" > > Querying information for > > entity:'file:///home/mpiechotka/Documentation/Magazines/Linux Journal/202.pdf' > > Unable to retrieve data for URI, 1.35: syntax error, expected `}' > > Hmm, can you try: > > tracker-info > file:///path/to/home/Documentation/Magazines/Linux%20Journal/202.pdf > > I don't think it would work the way you tried it. > % tracker-info file:///path/to/home/Documentation/Magazines/Linux%20Journal/202.pdf Querying information for entity:'file:///path/to/home/Documentation/Magazines/Linux%20Journal/202.pdf' Results: % > > > PDFs and sources (.c files?) are usually listed as documents. Is it possible > > > this is a configuration error? > > > > > > > I don't think so - it happend after update of tracker > > > > > Running the following should give some clarity: > > > > > > tracker-control -r (this will reindex everything) > > > /usr/libexec/tracker-miner-fs -v 3 > > > > > > The last command there should produce a log and output which we can use to find > > > out if the files were found and ignored (which is what I suspect here). If you > > > get no where can you attach this log here with the uri of the file you expect > > > to be indexed and I will inspect it. > > > > Ok. As reindexing will take whole day (I assume it takes as long as initial) > > I'll do it as soon as I will be able to left computer running so long. > > The whole day? That doesn't sound right. You're using Tracker 0.9? How many > files/folders are you indexing and is your machine relatively modern? Yes. Whole day == working day (8-12h - I haven't measured exactly). I'm not sure about number of file/folders but it is arounf 40GiB of data. Machine have 2.8 Core 2 Duo with 4 GiB of RAM. The problem could be the bug #639492 however.
(In reply to comment #10) > % tracker-info > file:///path/to/home/Documentation/Magazines/Linux%20Journal/202.pdf > Querying information for > entity:'file:///path/to/home/Documentation/Magazines/Linux%20Journal/202.pdf' > Results: Note the "/path/to/home/" which needs replacing with your real home path ;) > Yes. Whole day == working day (8-12h - I haven't measured exactly). I'm not > sure about number of file/folders but it is arounf 40GiB of data. Machine have > 2.8 Core 2 Duo with 4 GiB of RAM. Hmm, still sounds rather long to me. > The problem could be the bug #639492 however. That fix was for tracker-needle only. It doesn't affect tracker-search.
Ups. Sorry for the previous post - I've travelled all day yesterday so I was a little confused at the evening. (In reply to comment #11) > (In reply to comment #10) > > % tracker-info > > file:///path/to/home/Documentation/Magazines/Linux%20Journal/202.pdf > > Querying information for > > entity:'file:///path/to/home/Documentation/Magazines/Linux%20Journal/202.pdf' > > Results: > > Note the "/path/to/home/" which needs replacing with your real home path ;) > tracker-info "file://$HOME/Documentation/Magazines/Linux%20Journal/202.pdf" Querying information for entity:'file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/202.pdf' Results: % > > Yes. Whole day == working day (8-12h - I haven't measured exactly). I'm not > > sure about number of file/folders but it is arounf 40GiB of data. Machine have > > 2.8 Core 2 Duo with 4 GiB of RAM. > > Hmm, still sounds rather long to me. > > > The problem could be the bug #639492 however. > > That fix was for tracker-needle only. It doesn't affect tracker-search. I meant bug #635847.
(In reply to comment #12) > Ups. Sorry for the previous post - I've travelled all day yesterday so I was a > little confused at the evening. > > (In reply to comment #11) > > (In reply to comment #10) > > > % tracker-info > > > file:///path/to/home/Documentation/Magazines/Linux%20Journal/202.pdf > > > Querying information for > > > entity:'file:///path/to/home/Documentation/Magazines/Linux%20Journal/202.pdf' > > > Results: > > > > Note the "/path/to/home/" which needs replacing with your real home path ;) > > > > tracker-info "file://$HOME/Documentation/Magazines/Linux%20Journal/202.pdf" > Querying information for > entity:'file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/202.pdf' > Results: > > > % Hmm, most strange. Does using the following command line produce any files? If so, can you grep for the one you're interested in to see if it turns up. I would expect your file to be listed here with the mime type of 'application/pdf': tracker-sparql -q "SELECT ?document nie:url(?document) nie:mimeType(?document) WHERE { ?document a nfo:FileDataObject . ?document tracker:available true . } ORDER BY ASC(nie:url(?document)) OFFSET 0 LIMIT 512" NOTE: if you have > 512 files we might need to refine this query.
(In reply to comment #13) > (In reply to comment #12) > > Ups. Sorry for the previous post - I've travelled all day yesterday so I was a > > little confused at the evening. > > > > (In reply to comment #11) > > > (In reply to comment #10) > > > > % tracker-info > > > > file:///path/to/home/Documentation/Magazines/Linux%20Journal/202.pdf > > > > Querying information for > > > > entity:'file:///path/to/home/Documentation/Magazines/Linux%20Journal/202.pdf' > > > > Results: > > > > > > Note the "/path/to/home/" which needs replacing with your real home path ;) > > > > > > > tracker-info "file://$HOME/Documentation/Magazines/Linux%20Journal/202.pdf" > > Querying information for > > entity:'file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/202.pdf' > > Results: > > > > > > % > > Hmm, most strange. Does using the following command line produce any files? If > so, can you grep for the one you're interested in to see if it turns up. I > would expect your file to be listed here with the mime type of > 'application/pdf': > > tracker-sparql -q "SELECT ?document nie:url(?document) nie:mimeType(?document) > WHERE { ?document a nfo:FileDataObject . ?document tracker:available true . } > ORDER BY ASC(nie:url(?document)) OFFSET 0 LIMIT 512" > > NOTE: if you have > 512 files we might need to refine this query. It produces more then 512 files. I've used tracker-sparql -q "SELECT ?document nie:url(?document) nie:mimeType(?document) WHERE { ?document a nfo:FileDataObject . ?document tracker:available true . ?document nie:mimeType 'application/pdf' . } ORDER BY ASC(nie:url(?document)) OFFSET 0 LIMIT 512" However surprisingly it lists: urn:uuid:7395157e-65a4-29e4-86db-816169a0a543, file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/193.pdf, application/pdf urn:uuid:c598ebb8-56ba-9515-2ed9-fa39a740bdf8, file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/194.pdf, application/pdf urn:uuid:d8527b01-257a-6649-0f7f-ee3baac489cd, file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/195.pdf, application/pdf urn:uuid:b710d890-4f1c-e472-e6c8-9e88a08b7508, file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/196.pdf, application/pdf urn:uuid:1a414dcf-c65e-7da7-6052-c57578a5e4c2, file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/199.pdf, application/pdf urn:uuid:43d00b4d-89af-b0af-f20e-7aa64572c540, file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/200.pdf, application/pdf urn:uuid:ef87855e-ef2b-4a3a-91c9-116158605814, file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/201.pdf, application/pdf urn:uuid:7a321d06-b842-f07b-ed1d-a72f0efdf88f, file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/193.pdf, application/pdf urn:uuid:62d55df8-38d1-756b-9b4b-ad3a0e66c79e, file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/194.pdf, application/pdf urn:uuid:7f305e40-13c4-8416-cf58-e7d7cf9c3434, file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/195.pdf, application/pdf urn:uuid:8750997b-f094-da84-7225-7086ac392832, file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/196.pdf, application/pdf urn:uuid:7ca10b08-1bbf-f237-c8b6-0c38866f1462, file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/197.pdf, application/pdf I don't have and never had directory "Linux Jurnal". The file I was looking for is not listed. PS. Now tracker-search find some files about websocket: Results: file:///home/mpiechotka/Sources/WebKit/LayoutTests/ChangeLog-2010-01-29 file:///home/mpiechotka/Sources/WebKit/LayoutTests/fast/constructors/constructor-as-function-crash-expected.txt file:///home/mpiechotka/Sources/WebKit/LayoutTests/fast/dom/prototype-inheritance-2-expected.txt file:///home/mpiechotka/Sources/WebKit/LayoutTests/fast/dom/prototype-inheritance-expected.txt file:///home/mpiechotka/Sources/WebKit/LayoutTests/fast/js/global-constructors-expected.txt file:///home/mpiechotka/Sources/WebKit/LayoutTests/http/tests/websocket file:///home/mpiechotka/Sources/WebKit/LayoutTests/inspector/extensions-api-expected.txt file:///home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-gpu/test_expectations.txt file:///home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-linux/http/tests/websocket file:///home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-linux/websocket file:///home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-mac/http/tests/websocket file:///home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-mac/websocket file:///home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium/test_expectations.txt file:///home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-win/http/tests/websocket file:///home/mpiechotka/Sources/WebKit/LayoutTests/platform/chromium-win/websocket file:///home/mpiechotka/Sources/WebKit/LayoutTests/platform/mac/test_expectations.txt file:///home/mpiechotka/Sources/WebKit/LayoutTests/platform/qt/Skipped file:///home/mpiechotka/Sources/WebKit/LayoutTests/platform/win/Skipped file:///home/mpiechotka/Sources/WebKit/Source/WebCore/ChangeLog-2010-05-24 file:///home/mpiechotka/Sources/WebKit/Source/WebCore/CMakeLists.txt file:///home/mpiechotka/Sources/WebKit/Source/WebCore/DerivedSources.make file:///home/mpiechotka/Sources/WebKit/Source/WebCore/WebCore.gypi file:///home/mpiechotka/Sources/WebKit/Source/WebCore/WebCore.pri file:///home/mpiechotka/Sources/WebKit/Source/WebCore/WebCore.pro file:///home/mpiechotka/Sources/WebKit/Tools/ChangeLog-2010-05-24 file:///home/mpiechotka/Sources/WebKit/WebKit/gtk/NEWS file:///home/mpiechotka/Sources/WebKit/WebKit/mac/ChangeLog-2010-01-29
(In reply to comment #14) > It produces more then 512 files. I've used > > tracker-sparql -q "SELECT ?document nie:url(?document) nie:mimeType(?document) > WHERE { ?document a nfo:FileDataObject . ?document tracker:available true . > ?document nie:mimeType 'application/pdf' . } > ORDER BY ASC(nie:url(?document)) OFFSET 0 LIMIT 512" > > However surprisingly it lists: > > urn:uuid:7395157e-65a4-29e4-86db-816169a0a543, > file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/193.pdf, > application/pdf > urn:uuid:c598ebb8-56ba-9515-2ed9-fa39a740bdf8, > file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/194.pdf, > application/pdf > urn:uuid:d8527b01-257a-6649-0f7f-ee3baac489cd, > file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/195.pdf, > application/pdf > urn:uuid:b710d890-4f1c-e472-e6c8-9e88a08b7508, > file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/196.pdf, > application/pdf > urn:uuid:1a414dcf-c65e-7da7-6052-c57578a5e4c2, > file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/199.pdf, > application/pdf > urn:uuid:43d00b4d-89af-b0af-f20e-7aa64572c540, > file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/200.pdf, > application/pdf > urn:uuid:ef87855e-ef2b-4a3a-91c9-116158605814, > file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/201.pdf, > application/pdf > urn:uuid:7a321d06-b842-f07b-ed1d-a72f0efdf88f, > file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/193.pdf, > application/pdf > urn:uuid:62d55df8-38d1-756b-9b4b-ad3a0e66c79e, > file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/194.pdf, > application/pdf > urn:uuid:7f305e40-13c4-8416-cf58-e7d7cf9c3434, > file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/195.pdf, > application/pdf > urn:uuid:8750997b-f094-da84-7225-7086ac392832, > file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/196.pdf, > application/pdf > urn:uuid:7ca10b08-1bbf-f237-c8b6-0c38866f1462, > file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/197.pdf, > application/pdf OK, can you copy and paste one of these urls and use it with tracker-info to list what properties are associated with the resource. It should say it is an nfo:Document. > I don't have and never had directory "Linux Jurnal". The file I was looking for > is not listed. Curious. We use the following query: SELECT ?urn nie:url(?urn) tracker:coalesce(nie:title(?urn), nfo:fileName(?urn), \"$unknown\") tracker:coalesce(nco:fullname(?creator), nco:fullname(?publisher), \"\") fn:concat(nfo:pageCount(?urn), \" $pages\") ?tooltip WHERE { ?urn a nfo:Document ; nie:url ?tooltip ; fts:match \"$criteria_escaped\" . OPTIONAL { ?urn nco:creator ?creator . } OPTIONAL { ?urn nco:publisher ?publisher . } } ORDER BY DESC(fts:rank(?urn)) DESC(nie:title(?urn)) OFFSET $offset LIMIT $limit Which means it has to be an nfo:Document and have an nie:url and match with fts:match. The former 2 should always exist, the later might not work if you don't have FTS enabled. Do you have have FTS enabled in your build?
(In reply to comment #15) > (In reply to comment #14) > > It produces more then 512 files. I've used > > > > tracker-sparql -q "SELECT ?document nie:url(?document) nie:mimeType(?document) > > WHERE { ?document a nfo:FileDataObject . ?document tracker:available true . > > ?document nie:mimeType 'application/pdf' . } > > ORDER BY ASC(nie:url(?document)) OFFSET 0 LIMIT 512" > > > > However surprisingly it lists: > > > > urn:uuid:7395157e-65a4-29e4-86db-816169a0a543, > > file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/193.pdf, > > application/pdf > > urn:uuid:c598ebb8-56ba-9515-2ed9-fa39a740bdf8, > > file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/194.pdf, > > application/pdf > > urn:uuid:d8527b01-257a-6649-0f7f-ee3baac489cd, > > file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/195.pdf, > > application/pdf > > urn:uuid:b710d890-4f1c-e472-e6c8-9e88a08b7508, > > file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/196.pdf, > > application/pdf > > urn:uuid:1a414dcf-c65e-7da7-6052-c57578a5e4c2, > > file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/199.pdf, > > application/pdf > > urn:uuid:43d00b4d-89af-b0af-f20e-7aa64572c540, > > file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/200.pdf, > > application/pdf > > urn:uuid:ef87855e-ef2b-4a3a-91c9-116158605814, > > file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/201.pdf, > > application/pdf > > urn:uuid:7a321d06-b842-f07b-ed1d-a72f0efdf88f, > > file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/193.pdf, > > application/pdf > > urn:uuid:62d55df8-38d1-756b-9b4b-ad3a0e66c79e, > > file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/194.pdf, > > application/pdf > > urn:uuid:7f305e40-13c4-8416-cf58-e7d7cf9c3434, > > file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/195.pdf, > > application/pdf > > urn:uuid:8750997b-f094-da84-7225-7086ac392832, > > file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/196.pdf, > > application/pdf > > urn:uuid:7ca10b08-1bbf-f237-c8b6-0c38866f1462, > > file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/197.pdf, > > application/pdf > > OK, can you copy and paste one of these urls and use it with tracker-info to > list what properties are associated with the resource. It should say it is an > nfo:Document. > % tracker-info file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/197.pdf Querying information for entity:'file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/197.pdf' 'urn:uuid:7ca10b08-1bbf-f237-c8b6-0c38866f1462' Results: 'http://purl.org/dc/elements/1.1/date' = '2010-07-30T20:15:07Z' 'http://purl.org/dc/elements/1.1/date' = '2010-11-17T18:41:17Z' 'http://purl.org/dc/elements/1.1/source' = 'urn:nepomuk:datasource:9291a450-1d49-11de-8c30-0800200c9a66' 'tracker:added' = '2010-12-23T03:02:43Z' 'tracker:modified' = '30640' 'rdf:type' = 'http://www.w3.org/2000/01/rdf-schema#Resource' 'rdf:type' = 'http://www.semanticdesktop.org/ontologies/2007/01/19/nie#DataObject' 'rdf:type' = 'http://www.semanticdesktop.org/ontologies/2007/01/19/nie#InformationElement' 'rdf:type' = 'http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#Document' 'rdf:type' = 'http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#FileDataObject' 'rdf:type' = 'http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#TextDocument' 'rdf:type' = 'http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#PaginatedTextDocument' 'nie:byteSize' = '17534278' 'nie:dataSource' = 'urn:nepomuk:datasource:9291a450-1d49-11de-8c30-0800200c9a66' 'nie:isPartOf' = 'urn:uuid:05a8cee3-599f-3083-1250-98d2ee28d3b1' 'nie:url' = 'file:///home/mpiechotka/Documentation/Magazines/Linux%20Jurnal/197.pdf' 'nfo:belongsToContainer' = 'urn:uuid:05a8cee3-599f-3083-1250-98d2ee28d3b1' 'tracker:available' = 'true' 'nie:isStoredAs' = 'urn:uuid:7ca10b08-1bbf-f237-c8b6-0c38866f1462' 'nie:mimeType' = 'application/pdf' 'nfo:fileLastAccessed' = '2010-11-17T18:41:17Z' 'nfo:fileLastModified' = '2010-07-30T20:15:07Z' 'nfo:fileName' = '197.pdf' 'nfo:fileSize' = '17534278' 'nfo:pageCount' = '84' % tracker-info file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/195.pdf Querying information for entity:'file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/195.pdf' 'urn:uuid:d8527b01-257a-6649-0f7f-ee3baac489cd' Results: 'http://purl.org/dc/elements/1.1/date' = '2010-06-06T16:16:34Z' 'http://purl.org/dc/elements/1.1/date' = '2011-01-17T17:28:13Z' 'http://purl.org/dc/elements/1.1/source' = 'urn:nepomuk:datasource:9291a450-1d49-11de-8c30-0800200c9a66' 'tracker:added' = '2011-01-15T13:02:37Z' 'tracker:modified' = '351874' 'rdf:type' = 'http://www.w3.org/2000/01/rdf-schema#Resource' 'rdf:type' = 'http://www.semanticdesktop.org/ontologies/2007/01/19/nie#DataObject' 'rdf:type' = 'http://www.semanticdesktop.org/ontologies/2007/01/19/nie#InformationElement' 'rdf:type' = 'http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#Document' 'rdf:type' = 'http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#FileDataObject' 'rdf:type' = 'http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#TextDocument' 'rdf:type' = 'http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#PaginatedTextDocument' 'nie:byteSize' = '15016313' 'nie:dataSource' = 'urn:nepomuk:datasource:9291a450-1d49-11de-8c30-0800200c9a66' 'nie:isPartOf' = 'urn:uuid:9f2247be-cb31-c7d7-e967-a8b7142258cc' 'nie:url' = 'file:///home/mpiechotka/Documentation/Magazines/Linux%20Journal/195.pdf' 'nfo:belongsToContainer' = 'urn:uuid:9f2247be-cb31-c7d7-e967-a8b7142258cc' 'tracker:available' = 'true' 'nie:isStoredAs' = 'urn:uuid:d8527b01-257a-6649-0f7f-ee3baac489cd' 'nie:mimeType' = 'application/pdf' 'nfo:fileLastAccessed' = '2011-01-17T17:28:13Z' 'nfo:fileLastModified' = '2010-06-06T16:16:34Z' 'nfo:fileName' = '195.pdf' 'nfo:fileSize' = '15016313' 'nfo:pageCount' = '84' %