Will test it later, havent had a chance to look at the code yet. Would it be possible to update them via GQL? I have a plugin that does auto-search and match either via my tag DB or by searching StashDB. Wouldn't recommend it for prod but would be great as a plugin

Will test it later, havent had a chance to look at the code yet. Would it be possible to update them via GQL? I have a plugin that does auto-search and match either via my tag DB or by searching StashDB. Wouldn't recommend it for prod but would be great as a plugin

So, currently you can already do this with this:

New Tag:

mutation {
    tagCreate(input: {
      name: "Example Tag"
      stash_ids: [
        {
          endpoint: "https://stashdb.org/graphql"
          stash_id: "abc123-def456"
        }
      ]
    }) {
      id
      name
      stash_ids {
        endpoint
        stash_id
      }
    }
  }

Update Existing:

 mutation {
    tagUpdate(input: {
      id: "123"
      stash_ids: [
        {
          endpoint: "https://stashdb.org/graphql"
          stash_id: "abc123-def456"
        }
      ]
    }) {
      id
      name
      stash_ids {
        endpoint
        stash_id
      }
    }
  }

Not user friendly as is.

Also, since the StashID can only be applied via scene tagger (via UI), there is effectively not way have multiple StashIDs linked to the same tag. Be it from the same stash-box instance or multiple ones.

I think at least manual input field is needed. Though a proper search interface be it tagger or something else would be ideal.

Not user friendly as is.

Also, since the StashID can only be applied via scene tagger (via UI), there is effectively not way have multiple StashIDs linked to the same tag. Be it from the same stash-box instance or multiple ones.

I think at least manual input field is needed. Though a proper search interface be it tagger or something else would be ideal.

I agree with you overall. Currently I kept it the same implementation as the rest of the StashID infrastructure. This could be step 1 of a larger project of eventually adding in a tagger for Tags. I could modify it to allow users to add in StashID's in the tag edit modal as a stopgap till that eventuality. I think it would need to be a conversation with WP for the larger scope of the project.

Edit: Since you can apply it via GraphQL you could also apply them via plugin

I think at least manual input field is needed.

Agree with Gykes here - let's push manually linking into a separate PR targeting 0.30 release. I'd like to get something in for manually linking stash-ids to all supporting objects (performers, studios, scenes, etc).

Static code review only. Not yet tested.

Needs the following missing bits:

* cover tag stash id table in `anonymise.go`

* add `StashIDs` to `jsonschema.Tag` and import/export functionality

* add unit test coverage for the new fields, see the performer tests for reference

Fixed, took me a minute to figure out the unit testing but I think it's good?

I think at least manual input field is needed.

Agree with Gykes here - let's push manually linking into a separate PR targeting 0.30 release. I'd like to get something in for manually linking stash-ids to all supporting objects (performers, studios, scenes, etc).

Once you are content with the major implementation I can go ahead and do the UI ability to manually add StashIDs.