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] Add support for custom post-processing scripts on new items #362

Closed
pierre-delecto opened this issue Feb 11, 2020 · 5 comments
Closed
Labels
feature Pull requests that add a new feature investigate Investigation needed
Milestone

Comments

@pierre-delecto
Copy link

I would like to be able to process newly added scenes. My scenes come in with a defined naming structure, but current solutions do not easily update the scene based on the naming structure. For example, the scene filename parser works well, but there is no easy way to limit it to new items. Parsing would preferably happen automatically for new scenes.

I would propose supporting custom scripts to be executed against newly added scenes. This would allow custom processing, such as adding a data, title, performers, etc. By passing in a scene_id (and perhaps an auth token for graphQL), most processing could be automated. This model works well for other projects like nzbget/sabnzbd.

An alternative would be to try to build post-processing directly into stash. By allowing custom scripts, extensibility is improved.

@pierre-delecto pierre-delecto changed the title [Feature] Short Form Title (50 chars or less.) [Feature] Add support for custom post-processing scripts on new items Feb 11, 2020
@Leopere Leopere added investigate Investigation needed question labels Feb 11, 2020
@bnkai
Copy link
Collaborator

bnkai commented Feb 11, 2020

One way could be by adding system tags and then making the autoparser only work on them.
For example after scanning all scenes should get marked with a system defined tag (e.g. system_new ).
If the scene is manually updated this tag would then be removed. Autoparser could then check scenes with this tag only and remove it after it process them.
That way we could also have a system_locked tag that makes the scenes editable only manually by the user and not by autoparser or say the clean task or the tag/performer/studio auto tagger or any non-interactive ( automated) action.

@bnkai bnkai added the feature Pull requests that add a new feature label Feb 11, 2020
@pierre-delecto
Copy link
Author

I like the idea of allowing the scene file parser work specifically with new files. Even with that though, adding data would still requires manual intervention (manual scan, manual file parse). There would preferably be a way to automate parsing when new files are detected.

@ChaosTherum
Copy link

I could definitely use something along these lines it would make importing youtube-dl files super easy just pull the metadata that youtube-dl saves alongside the file.

@WithoutPants WithoutPants added this to the Version 0.8.0 milestone Aug 30, 2021
@WithoutPants
Copy link
Collaborator

Resolved by #1452.

@FoxxMD
Copy link

FoxxMD commented Jun 29, 2022

@ChaosTherum did you get a yt-dl metadata plugin implemented, by chance?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Pull requests that add a new feature investigate Investigation needed
Projects
None yet
Development

No branches or pull requests

6 participants