1tracker-info(1) User Commands tracker-info(1)
2
6 tracker-info - Retrieve all information available for a certain file.
7
10 tracker info [options...] <file1> [[file2] ...]
11
14 tracker info asks for all the known metadata available for the given
15 file.
16 Multiple file arguments can be provided to retrieve information about
18 multiple files.
19 The file argument can be either a local path or a URI. It also does not
21 have to be an absolute path.
22
25 -f, --full-namespaces
26 By default, all keys and values reported about any given file
27 are returned in shortened form, for example, nie:title is shown
28 instead of http://www.semanticdesktop.org/ontolo‐
29 gies/2007/01/19/nie#title. This makes things much easier to see
30 generally and the output is less cluttered. This option reverses
31 that so FULL namespaces are shown instead.
32 -c, --plain-text-content
34 If the resource being displayed has nie:PlainTextContent (i.e.
35 information about the content of the resource, which could be
36 the contents of a file on the disk), then this option displays
37 that in the output.
38 -i, --resource-is-iri
40 In most cases, the file argument supplied points to a URL or
41 PATH which is queried for according to the resource associated
42 with it by nie:url. However, in cases where the file specified
43 turns out to be the actual URN itself, this argument is required
44 to tell "tracker info" not to do the extra step of looking up
45 the URN related by nie:url.
46 For example, consider that you store URNs by the actual URL
48 itself and use the unique nie:url in another resource (which is
49 quite reasonable when using containers and multi-resource condi‐
50 tions), you would need this argument to tell "tracker info" that
51 the file supplied is actually a URN not URL.
52 -t, --turtle
54 Output results as Turtle RDF. If -f is enabled, full URIs are
55 shown for subjects, predicates and objects; otherwise, shortened
56 URIs are used, and all the prefixes Tracker knows about are
57 printed at the top of the output.
58
61 TRACKER_SPARQL_BACKEND
62 This option allows you to choose which backend you use for con‐
63 necting to the database. This choice can limit your functional‐
64 ity. There are three settings.
65 With "direct" the connection to the database is made directly to
67 the file itself on the disk, there is no intermediary daemon or
68 process. The "direct" approach is purely read-only.
69 With "bus" the tracker-store process is used to liase with the
71 database queuing all requests and managing the connections via
72 an IPC / D-Bus. This adds a small overhead BUT this is the only
73 approach you can use if you want to write to the database.
74 With "auto" the backend is decided for you, much like it would
76 be if this environment variable was undefined.
77 TRACKER_PRAGMAS_FILE
80 Tracker has a fixed set of PRAGMA settings for creating its
81 SQLite connection. With this environment variable pointing to a
82 text file you can override these settings. The file is a \n sep‐
83 arated list of SQLite queries to execute on any newly created
84 SQLite connection in tracker-store.
85
88 tracker-store(1), tracker-sparql(1).
89 http://nepomuk.semanticdesktop.org/
91 http://www.w3.org/TR/rdf-sparql-query/
93GNU Oct 2008 tracker-info(1)