Not all tags match StashDB names

[oikmeg]

The following tags are spelt differently StashDB, so they should probably be changed here as well:

• Blow Job -> Blowjob
• Hand Job -> Handjob
• Face Fucking -> Face Fuck
• Tit Job -> Titjob

https://stashdb.org/tags/86783b99-3e60-4be0-909e-d00afe65c9ef https://stashdb.org/tags/ec272479-c544-4aa8-8fc8-4bf9e05df467 https://stashdb.org/tags/2e87d2e5-482d-4acd-818c-58450e9ed216 https://stashdb.org/tags/3e563733-8a78-424f-a89a-1abaabdd2494

I would have submitted a PR for OPTIONS, but I'm guessing these are tagged on the API as well this way

[cc1234475]

Hi @oikmeg, As this tool is not stashdb specific I didn't try and match it to it's naming structure. I've used the alias feature in stash to remap what the plugin returns to my tagging schema.

However if we did want to do this, on the server side the name scheme is baked into the model and the training data. so it would require us to retrain the model with updated names. So if we wanted to remap them we could try and do it by having a lookup table.

[oikmeg]

I don't think we'd need to retrain anything. It should be possible to use key:value store in this script. Use the model as key and the stashdb as value of the tag.

That way the tag is written locally to whatever value is, and the model can lookup based on key. Similar to how translation key/value work.

Example:

const OPTIONS = {
    "Blow Job": "Blowjob"
}

[existing-paradox]

I know this thread is mostly dead... But it would make more sense to add aliases to your Stash instance to handle tag matching between stashtag and your preferred naming structure.