Tagsistant
   HOME

TheInfoList



OR:

Tagsistant is a
semantic file system Semantic file systems are file systems used for information persistence which structure the data according to their semantics and intent, rather than the location as with current file systems. It allows the data to be addressed by their content (as ...
for the
Linux kernel The Linux kernel is a free and open-source, monolithic, modular, multitasking, Unix-like operating system kernel. It was originally authored in 1991 by Linus Torvalds for his i386-based PC, and it was soon adopted as the kernel for the GNU ope ...
, written in C and based on
FUSE Fuse or FUSE may refer to: Devices * Fuse (electrical), a device used in electrical systems to protect against excessive current ** Fuse (automotive), a class of fuses for vehicles * Fuse (hydraulic), a device used in hydraulic systems to protect ...
. Unlike traditional file systems that use hierarchies of directories to locate objects, Tagsistant introduces the concept of tags.


Design and differences with hierarchical file systems

In computing, a
file system In computing, file system or filesystem (often abbreviated to fs) is a method and data structure that the operating system uses to control how data is stored and retrieved. Without a file system, data placed in a storage medium would be one larg ...
is a type of data store which could be used to store, retrieve and update files. Each file can be uniquely located by its path. The user must know the path in advance to access a file and the path does not necessarily include any information about the content of the file. Tagsistant uses a complementary approach based on tags. The user can create a set of tags and apply those tags to files, directories and other objects ( devices, pipes, ...). The user can then search all the objects that match a subset of tags, called a query. This kind of approach is well suited for managing user contents like pictures, audio recordings, movies and text documents but is incompatible with system files (like libraries, commands and configurations) where the univocity of the path is a
security Security is protection from, or resilience against, potential harm (or other unwanted coercive change) caused by others, by restraining the freedom of others to act. Beneficiaries (technically referents) of security may be of persons and social ...
requirement to prevent the access to a wrong content.


The tags/ directory

A Tagsistant file system features four main directories: :archive/ :relations/ :stats/ :tags/ Tags are created as sub directories of the tags/ directory and can be used in queries complying to this syntax: :tags/subquery/ /subquery/[+/subquery//@/ where a subquery is an unlimited list of tags, concatenated as directories: :tag1/tag2/tag3/.../tagN/ The portion of a path delimited by tags/ and @/ is the actual query. The +/ operator joins the results of different sub-queries in one single list. The @/ operator ends the query. To be returned as a result of the following query: :tags/t1/t2/+/t1/t4/@/ an object must be tagged as both t1/ and t2/ or as both t1/ and t4/. Any object tagged as t2/ or t4/, but not as t1/ will not be retrieved. The query syntax deliberately violates the POSIX file system semantics by allowing a path token to be a descendant of itself, like in tags/t1/t2/+/t1/t4/@ where t1/ appears twice. As a consequence a recursive scan of a Tagsistant file system will exit with an error or endlessly loop, as done by UNIX find: ~/tagsistant_mountpoint$ find tags/ tags/ tags/document tags/document/+ tags/document/+/document tags/document/+/document/+ tags/document/+/document/+/document tags/document/+/document/+/document/+ .. This drawback is balanced by the possibility to list the tags inside a query in any order. The query tags/t1/t2/@/ is completely equivalent to tags/t2/t1/@/ and tags/t1/+/t2/t3/@/ is equivalent to tags/t2/t3/+/t1/@/. The @/ element has the precise purpose of restoring the POSIX semantics: the path tags/t1/@/directory/ refers to a traditional directory and a recursive scan of this path will properly perform.


The reasoner and the relations/ directory

Tagsistant features a simple reasoner which expands the results of a query by including objects tagged with related tags. A relation between two tags can be established inside the relations/ directory following a three level pattern: :relations/tag1/rel/tag2/ The rel element can be ''includes'' or ''is_equivalent''. To include the ''rock'' tag in the ''music'' tag, the UNIX command mkdir can be used: :mkdir -p relations/music/includes/rock The reasoner can recursively resolve relations, allowing the creation of complex structures: :mkdir -p relations/music/includes/rock :mkdir -p relations/rock/includes/hard_rock :mkdir -p relations/rock/includes/grunge :mkdir -p relations/rock/includes/heavy_metal :mkdir -p relations/heavy_metal/includes/speed_metal The web of relations created inside the relations/ directory constitutes a basic form of ontology.


Autotagging plugins

Tagsistant features an ''autotagging'' plugin stack which gets called when a file or a symlink is written. Each plugin is called if its declared
MIME type A media type (also known as a MIME type) is a two-part identifier for file formats and format contents transmitted on the Internet. The Internet Assigned Numbers Authority, Internet Assigned Numbers Authority (IANA) is the official authority for t ...
matches The list of working plugins released with Tagsistant 0.6 is limited to: * text/html: tags the file with each word in </code> and <code><keywords></code> elements and with ''document'', ''webpage'' and ''html'' too * image/jpeg: tags the file with each <a class="link_plain"; href="/html/ALL/l/E/Exchangeable_image_file_format.html" ;"title="Exchangeable image file format">Exif</a> tag <h1><br><p> The repository</h1></p> Each Tagsistant file system has a corresponding repository containing an <code>archive/</code> directory where the objects are actually saved and a <code>tags.sql</code> file holding tagging information as an <a class="link_plain"; href="/html/ALL/l/S/SQLite.html" ;"title="SQLite">SQLite</a> database. If the <a class="link_plain"; href="/html/ALL/l/M/MySQL.html" ;"title="MySQL">MySQL</a> database engine was specified with the <code>--db</code> argument, the <code>tags.sql</code> file will be empty. Another file named <code>repository.ini</code> is a <div class="linkinfo_desc"><a class = "desc_only" href="/html/ALL/l/G/GLib.html" "title="GLib">GLib</a><span class="linkinfotext"> GLib is a bundle of three (formerly five) low-level system libraries written in C and developed mainly by GNOME. GLib's code was separated from GTK, so it can be used by software other than GNOME and has been developed in parallel ever sinc ...<br></span></div> ini store with the repository configuration. Tagsistant 0.6 is compatible with the MySQL and Sqlite dialects of SQL for tag reasoning and tagging resolution. While porting its logic to other SQL dialects is possible, differences in basic constructs (especially the INTERSECT SQL keyword) must be considered. <h1><br><p> The archive/ and stats/ directories</h1></p> The <code>archive/</code> directory has been introduced to provide a quick way to access objects without using tags. Objects are listed with their inode number prefixed. The <code>stats/</code> directory features some read-only files containing usage statistics. A file <code>configuration</code> holds both compile time information and current repository configuration. <h1><br><p> Main criticisms</h1></p> It has been highlighted that relying on an external database to store tags and tagging information could cause the complete loss of metadata if the database gets corrupted. It has been highlighted that using a flat namespace tends to overcrowd the <code>tags/</code> directory.<ref></ref> This could be mitigated introducing <a class="link_plain"; href="/html/ALL/l/T/Tag_(metadata)#Triple_tags.html" ;"title="Tag (metadata)#Triple tags">triple tags</a>. <h1><br><p> See also</h1></p> *<div class="linkinfo_desc"><a class = "desc_only" href="/html/ALL/l/S/Semantic_file_system.html" "title="Semantic file system">Semantic file system</a><span class="linkinfotext"> Semantic file systems are file systems used for information persistence which structure the data according to their semantics and intent, rather than the location as with current file systems. It allows the data to be addressed by their content (as ...<br></span></div> <h1><br><p> References</h1></p> <h1><br><p> External links</h1></p> * {{Official website, http://www.tagsistant.net/ <br><a href="https://aur.archlinux.org/packages/tagsistant/" target="_blank" class="mw-redirect" title="Arch Linux package">Arch Linux package</a><br><br><a href="https://news.ycombinator.com/item?id=2573318" target="_blank" class="mw-redirect" title="Discussion on Hacker News">Discussion on Hacker News</a><br><br><a href="ttp://www.lesbonscomptes.com/pages/tagfs" target="_blank" class="mw-redirect" title=""></a><br><br><a href="http://lakm.us/logit/2010/03/tagsistant-on-production-2/" target="_blank" class="mw-redirect" title="Tagsistant On Production">Tagsistant On Production</a><br> <a class="link_plain"; href="/html/ALL/l/C/Computer_file_systems.html" ;"title="Computer file systems">Computer file systems</a> <a class="link_plain"; href="/html/ALL/l/C/Data_management.html" ;"title="Data management">Data management</a> <a class="link_plain"; href="/html/ALL/l/C/Semantic_file_systems.html" ;"title="Semantic file systems">Semantic file systems</a> </div> <div id="AdvertBottom1"> </div> <center> <script src="/js/AdvertBottom1.js"> </script> </center> <footer> <div> <br><br> <br><br> <center> <br><a target="_top" href="../index.html"> HOME </a><br> <br>Content is Copyleft<br>Website design, code, and AI is Copyrighted (c) 2014-2017 by Stephen Payne<br><br> <a target="_top" href="https://donate.wikimedia.org/w/index.php?title=Special:LandingPage&country=US&uselang=en&utm_medium=sidebar&utm_source=donate&utm_campaign=C13_en.wikipedia.org"> Consider donating to Wikimedia </a><br> <br> As an Amazon Associate I earn from qualifying purchases <br> </center> </div> </footer> <div id="AddedByJS"> </div> <script src="/js/site.js"> </script> <!--#include file="inc/summary_footer.html" --> </body></html>