tracker3-sparql – Use SparQL to query the Tracker databases. Synopsistracker3 sparql -q <sparql> [-u] | -f <file> tracker3 sparql -t [class] [-s <needle>] [-p] tracker3 sparql [-c] [-p] [-x] [-n [class]] [-i [property]] [-s <needle>] tracker3 sparql [–get-longhand <class>] [–get-shorthand <class>]DescriptionThis command allows probing of the current database schema (also known as ontology) and running…
tracker3-search – Search for content by type or across all types Synopsistracker3 search [options…] [[expression1] …] Descriptiontracker3 search searches all indexed content for expression. The resource in which expression matches must exist (see –all for more information). All results are returned in ascending order. In all cases, if no expression is given for an argument…
tracker3-reset – Reset the index and configuration Synopsistracker3 reset [–filesystem | –rss] [–file FILE] DescriptionThe reset command will change either your configuration or index irreversibly and should be used with care. Other than tags, actual data (e.g. files) should not be affected by this command. The "index" is a link between your content (either locally…
tracker3-info – Retrieve all information available for a certain file. Synopsistracker3 info [options…] <file1> [[file2] …] Descriptiontracker3 info asks for all the known metadata available for the given file. Multiple file arguments can be provided to retrieve information about multiple files. The file argument can be either a local path or a URI. It also…
tracker3-index – Index content using the Tracker filesystem miner Synopsistracker3 index tracker3 index –add [–recursive] <dir> [[dir] …] tracker3 index –remove <path> [[dir] …]DescriptionThis command causes the Tracker filesystem miner to process the given directories. These changes are persistent across future restarts. If invoked without arguments, the currently indexed locations will be listed. See Alsotracker-miner-fs-3(1).
tracker3-import – Import data into a Tracker database. Synopsistracker3 import FILE.ttl Descriptiontracker3 import imports data into a Tracker database. The data must conform to the existing ontology of the database. The data must be in Turtle format. You can use a tool such as rapper(1) to convert the data from other formats to Turtle. See…
tracker3-extract – Extract metadata from a file. Synopsystracker3 extract FILE Descriptiontracker3 extract reads the file provided and extracts any metadata it can from this file, then displays the metadata on standard output. The metadata is displayed as a SPARQL update command, that can be run against a SPARQL endpoint to update its copy of the…
tracker3-export – Export all data from a Tracker database. Synopsistracker3 export [options…] [IRI…] Descriptiontracker3 export exports data stored in a Tracker database, in Turtle format. By default all data is exported, if any IRI, only those resources will be printed. The output is intended to be machine-readable, not human readable. Use a tool such as…
tracker3-endpoint – Create a SPARQL endpoint Synopsistracker3 endpoint [–dbus-service | -b] <service_name> [–database-path | -d] <database_path> [[–ontology | -o] <ontology_name> | [–ontology-path | -p] <ontology_path>] [–http-port] <port> [–loopback] [[–system | –session]]DescriptionThis command allows creating SPARQL endpoints. The endpoint will be able to handle SPARQL select and update queries, and notify about changes in it. The…
tracker3-daemon – Start, stop, restart and list daemons responsible for indexing content Synopsistracker3 daemon [options…] tracker3 daemon -s | -t [daemons] | -k [daemons] | -l tracker3 daemon -f | -w [ontology] tracker3 daemon –miner <miner> –pause[-for-process] <reason> tracker3 daemon –miner <miner> –resume <cookie>DescriptionTracker indexes content with daemon processes that run in the background. The…
tracker-xdg-portal-3 – Portal to Tracker endpoints Synopsistracker-xdg-portal-3 [–version | -v]DescriptionThis daemon allows access to Tracker endpoints in a controlled manner. By default access to every service is disallowed, services may be whitelisted through additional policy in the .flatpak-info file. When whitelisting services, the policy may define specific graph names to allow access to, the default…
tracker-writeback – Used to write metadata set in Tracker back to physical files. Synopsistracker-writeback [OPTION…] Descriptiontracker-writeback is not supposed to be run by the user since it is started by its .desktop file when the user logs in. It can also be started manually of course for debugging purposes. You can not run more than…
tracker-writeback-3 – Used to write metadata set in Tracker back to physical files. Synopsistracker-writeback [OPTION…] Descriptiontracker-writeback is not supposed to be run by the user since it is started by its .desktop file when the user logs in. It can also be started manually of course for debugging purposes. You can not run more than…
tracker-tag – Add, remove and list tags. Synopsistracker tag FILE1 [FILE2 …] [-l <limit>] [-o <offset>] [-r] tracker tag -t [[TAG1] [TAG2] …] [-s] [-r] tracker tag -a <TAG> [-e <description>] tracker tag -d <TAG>DescriptionList tags for local files or by the tag labels themselves if -t is used. It’s also possible to manage tags…
tracker-store – database indexer and query daemon Synopsistracker-store [OPTION…] Descriptiontracker-store provides both a powerful database daemon which allows clients to query or update their data using the highly descriptive SPARQL language. tracker-store does not do any file crawling or any mining of data itself, instead other processes do that while tracker-store serves as a daemon…
tracker-status – Provide status and statistics on the data indexed Synopsistracker status tracker status –stat [-a] [[expression1]…] tracker status –collect-debug-infoDescriptionDisplay the status of the current index and data set. With the –stat option, displays statistics about the RDF classes and how many of each exist for data set that has been indexed. For example, "10…
tracker-stats – Provides statistics on the data indexed Synopsistracker-stats [OPTION…] [[EXPRESSION…] [EXPRESSION…]] DescriptionDisplay statistics about RDF classes in and how many of each exist for the data set that has been indexed. By default, only common and useful classes are shown, e.g. nfo:Document or nfo:Folder, for a full set of statistics, see the option. If…
tracker-sql – Use SQL to query the Tracker databases. Synopsistracker sql -q <sql> | -f <file>DescriptionThis command allows probing of the current database. When using commands like tracker sparql, the SPARQL used is translated into SQL before being run on the database. This allows direct use of the database using SQL avoiding the SPARQL engine…
tracker-sparql – Use SparQL to query the Tracker databases. Synopsistracker sparql -q <sparql> [-u] | -f <file> tracker sparql -t [class] [-s <needle>] [-p] tracker sparql [-c] [-p] [-x] [-n [class]] [-i [property]] [-s <needle>] tracker sparql [–get-longhand <class>] [–get-shorthand <class>]DescriptionThis command allows probing of the current database schema (also known as ontology) and running…
tracker-search – Search for content by type or across all types Synopsistracker search [options…] [[expression1] …] Descriptiontracker search searches all indexed content for expression. The resource in which expression matches must exist (see –all for more information). All results are returned in ascending order. In all cases, if no expression is given for an argument…