Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Stash endpoints for all item types #5433

Open
Valkyr-JS opened this issue Nov 2, 2024 · 0 comments
Open

[Feature] Stash endpoints for all item types #5433

Valkyr-JS opened this issue Nov 2, 2024 · 0 comments

Comments

@Valkyr-JS
Copy link

Is your feature request related to a problem? Please describe.
I'm working on a pipeline for curating my data, which includes a number of Stash instances referencing each other via endpoints. This works well for scenes, studios and performers, but cannot be done for any other data types.

Describe the solution you'd like
Stash endpoints should be able to be set on all, or at least most, data types. Images and galleries would benefit as much as scenes do. Endpoints could make tags easier to manage in databases with multiple Stash boxes where tag names and descriptions may conflict. That leaves groups and markers, which also could benefit. Allowing endpoints for all data types may encourage third-party development of scrapers or even stash boxes to cater to that data, e.g. as mentioned here.

Describe alternatives you've considered
For my own pipelines usage - which I appreciate is a unique user issue more than a wider community one - I have tried using aliases or performer disambiguations to store unique IDs related to the endpoint I'm referencing. This isn't an ideal solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant