58 lines
7.2 KiB
HTML
58 lines
7.2 KiB
HTML
<html>
|
|
<head>
|
|
<title>advanced - parents</title>
|
|
<link href="hydrus.ico" rel="shortcut icon" />
|
|
<link href="style.css" rel="stylesheet" type="text/css" />
|
|
</head>
|
|
<body>
|
|
<div class="content">
|
|
<h3 id="intro"><a href="#intro">quick version</a></h3>
|
|
<p>Tag parents let you automatically add a particular tag every time another tag is added. The relationship will also apply retroactively.</p>
|
|
<h3 id="the_problem"><a href="#the_problem">what's the problem?</a></h3>
|
|
<p>Tags often fall into certain heirarchies. Certain tags <i>always</i> imply certain other tags, and it is annoying and time-consuming to add them all individually every time.</p>
|
|
<p>For example, whenever you tag a file with <i>ak-47</i>, you probably also want to tag it <i>assault rifle</i>, and maybe even <i>firearm</i> as well.</p>
|
|
<p><img src="tag_parents_venn.png" /></p>
|
|
<p>Another time, you might tag a file <i>character:eddard stark</i>, and then also have to type in <i>house stark</i> and then <i>series:game of thrones</i>. (you might also think <i>series:game of thrones</i> should actually be <i>series:a song of ice and fire</i>, but that is an issue for <a href="advanced_siblings.html">siblings</a>)</p>
|
|
<p>Drawing more relationships would make a significantly more complicated venn diagram, so let's draw a family tree instead:</p>
|
|
<p><img src="tag_parents_got.png" /></p>
|
|
<h3 id="tag_parents"><a href="#tag_parents">tag parents</a></h3>
|
|
<p>Let's define the child-parent relationship 'C->P' as saying that tag P is the semantic superset/superclass of tag C. <b>All files that have C should also have P, without exception.</b> When the user tries to add tag C to a file, tag P is added automatically.</p>
|
|
<p>Let's expand our weapon example:</p>
|
|
<p><img src="tag_parents_firearms.png" /></p>
|
|
<p>In that graph, adding <i>ar-15</i> to a file would also add <i>semi-automatic rifle</i>, <i>rifle</i>, and <i>firearm</i>. Searching for <i>handgun</i> would return everything with <i>m1911</i> and <i>smith and wesson model 10</i>.</p>
|
|
<p>This can obviously get as complicated and autistic as you like, but be careful of being too confident--this is just a fun example, but is an AK-47 truly <i>always</i> an assault rifle? Some people would say no, and beyond its own intellectual neatness, what is the purpose of attempting to create such a complicated and 'perfect' tree? Of course you can create any sort of parent tags on your local tags or your own tag repositories, but this sort of thing can easily lead to arguments between reasonable people. I only mean to say, as someone who does a lot of tag work, to try not to create anything 'perfect', as it usually ends up wasting time. Act from need, not toward purpose.</p>
|
|
<h3 id="how_to_do_it"><a href="#how_to_do_it">how you do it</a></h3>
|
|
<p>Go to <i>services->manage tag parents</i>:</p>
|
|
<p><img src="tag_parents_dialog.png" /></p>
|
|
<p>Which looks and works just like the manage tag siblings dialog.</p>
|
|
<p>Note that when you hit ok, the client will look up all the files with all your added tag Cs and retroactively apply/pend the respective tag Ps if needed. This could mean thousands of tags!</p>
|
|
<p>Once you have some relationships added, the parents and grandparents will show indented anywhere you 'write' tags, such as the manage tags dialog:</p>
|
|
<p><img src="tag_parents_ac_1.png" /></p>
|
|
<p>Hitting enter on cersei will try to add <i>house lannister</i> and <i>series:game of thrones</i> as well.</p>
|
|
<p><img src="tag_parents_ac_2.png" /></p>
|
|
<h3 id="remote_parents"><a href="#remote_parents">remote parents</a></h3>
|
|
<p>Whenever you add or remove a tag parent pair to a tag repository, you will have to supply a reason (like when you petition a tag). A janitor will review this petition, and will approve or deny it. If it is approved, all users who synchronise with that tag repository will gain that parent pair. If it is denied, only you will see it.</p>
|
|
<h3 id="parent_favourites"><a href="#parent_favourites">parent 'favourites'</a></h3>
|
|
<p>As you use the client, you will likely make several processing workflows to archive/delete your different sorts of imports. You don't always want to go through things randomly--you might want to do some big videos for a bit, or focus on a particular character. A common search page is something like <code>[system:inbox, creator:blah, limit:256]</code>, which will show a sample of a creator in your inbox, so you can process just that creator. This is easy to set up and save in your favourite searches and quick to run, so you can load it up, do some archive/delete, and then dismiss it without too much hassle.</p>
|
|
<p>But what happens if you want to search for multiple creators? You might be tempted to make a large OR search predicate, like <code>creator:aaa OR creator:bbb OR creator:ccc OR creator:ddd</code>, of all your favourite creators so you can process them together as a 'premium' group. But if you want to add or remove a creator from that long OR, it can be cumbersome. And OR searches can just run slow sometimes. One answer is to use the new tag parents tools to apply a 'favourite' parent on all the artists and then search for that favourite.</p>
|
|
<p>Let's assume you want to search bunch of 'creator' tags on the PTR. What you will do is:</p>
|
|
<ul>
|
|
<li>Create a new 'local tag service' in <i>manage services</i> called 'my parent favourites'. This will hold our subjective parents without uploading anything to the PTR.</li>
|
|
<li>Go to <i>tags->manage where tag siblings and parents apply</i> and add 'my parent favourites' as the top priority for parents, leaving 'PTR' as second priority.</li>
|
|
<li>
|
|
<p>Under <i>tags->manage tag parents</i>, on your 'my parent favourites' service, add:</p>
|
|
<ul>
|
|
<li><code>creator:aaa->favourite:aesthetic art</code></li>
|
|
<li><code>creator:bbb->favourite:aesthetic art</code></li>
|
|
<li><code>creator:ccc->favourite:aesthetic art</code></li>
|
|
<li><code>creator:ddd->favourite:aesthetic art</code></li>
|
|
</ul>
|
|
<p>Watch/wait a few seconds for the parents to apply across the PTR for those creator tags.</p>
|
|
</li>
|
|
<li>Then save a new favourite search of <code>[system:inbox, favourite:aesthetic art, limit:256]</code>. This search will deliver results with any of the child 'creator' tags, just like a big OR search, and real fast!</li>
|
|
</ul>
|
|
<p>If you want to add or remove any creators to the 'aesthetic art' group, you can simply go back to <i>tags->manage tag parents</i>, and it will apply everywhere. You can create more umbrella/group tags if you like (and not just creators--think about clothing, or certain characters), and also use them in regular searches when you just want to browse some cool files.</p>
|
|
</div>
|
|
</body>
|
|
</html>
|