1tracker-extract(1)               User Commands              tracker-extract(1)
2
3
4

NAME

6       tracker-extract - Extract metadata from a file.
7
8

SYNOPSYS

10       tracker extract FILE
11
12

DESCRIPTION

14       tracker  extract  reads  the file provided and extracts any metadata it
15       can from this file, then displays the metadata on standard output.
16
17       The metadata is displayed as a SPARQL update command, that can  be  run
18       against a SPARQL endpoint to update its copy of the metadata.
19
20       The  actual  extraction  is done by a separate process. This is done to
21       isolate the calling process from any memory leaks  or  crashes  in  the
22       libraries Tracker uses to extract metadata.
23
24       For  more  information  see the libtracker-extract reference documenta‐
25       tion.
26
27

OPTIONS

29       -v, --verbosity=<LEVEL>
30              This sets the log verbosity for the extractor process.
31
32              The possible LEVEL options are:
33
34               ·   debug - Show EVERYTHING, from debug messages to errors.
35
36               ·   detailed - Show enough detail to understand what is happen‐
37                   ing.
38
39               ·   minimal - Show an overview of what is going on
40
41               ·   errors  -  Show  only  warnings, criticals, errors or fatal
42                   events.
43
44
45       -o, --output-format=<FORMAT>
46              Choose which format to use to output results. Supported  formats
47              are sparql, turtle and json-ld.
48
49

EXAMPLES

51       Using command line to extract metadata from a file:
52
53               $ tracker extract /path/to/some/file.mp3
54
55

ENVIRONMENT

57       TRACKER_EXTRACTORS_DIR
58              This  is  the  directory  which  tracker uses to load the shared
59              libraries from (used for extracting metadata for  specific  file
60              types). These are needed on each invocation of tracker-store. If
61              unset it will default to the correct place. This is used  mainly
62              for     testing    purposes.    The    default    location    is
63              /usr/lib/tracker-1.0/extract-modules/.
64
65       TRACKER_EXTRACTOR_RULES_DIR
66              This is the directory which tracker uses to load the rules files
67              from.  The rules files describe extractor modules and their sup‐
68              ported    MIME    types.     The     default     location     is
69              /usr/share/tracker/extract-rules/.
70
71       TRACKER_USE_CONFIG_FILES
72              Don't  use  GSettings,  instead use a config file similar to how
73              settings were saved in 0.10.x. That is, a  file  which  is  much
74              like an .ini file.  These are saved to $HOME/.config/tracker/
75
76

SEE ALSO

78       tracker-store(1), tracker-sparql(1), tracker-stats(1), tracker-info(1).
79
80       /usr/lib/tracker-1.0/extract-modules/
81
82       /usr/share/tracker/extract-rules/
83
84
85
86GNU                               April 2016                tracker-extract(1)
Impressum