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

feat: add option to perform GPT prompts over items from dataset without crawling #81

Open
Patai5 opened this issue Oct 27, 2024 · 4 comments
Labels
cancelled For cancelled Issues for various reasons enhancement New feature or improving/enhancing the existing ones for end users priority: nice to have Small bug or feature. Put to backlog and long-term planning. source: internal Reported or found out by us zenhub: product backlog

Comments

@Patai5
Copy link
Contributor

Patai5 commented Oct 27, 2024

Discussed in slack:
https://apify.slack.com/archives/CGZSN9DQC/p1729755239716379


We should add an option to perform basic prompting for dataset items as string inputs straight into GPT with no crawling. Basically provide an easy-to-use GPT API straight from this Actor.

I guess we have to add the dataset ID as input field, but what fields should we take from it as input? I suppose that we could make the input field from the dataset configurable as well? We can put both into a standalone “Dataset Input Settings” or something.

It will be pretty annoying to implement into the current "crawler" architecture ://

@Patai5 Patai5 added enhancement New feature or improving/enhancing the existing ones for end users priority: nice to have Small bug or feature. Put to backlog and long-term planning. source: internal Reported or found out by us labels Oct 27, 2024
@jancurn
Copy link
Contributor

jancurn commented Oct 27, 2024

Please let's not bake this into this Actor but create a new instead. Each Actor should do one thing and do it well - see https://github.com/apify/actor-whitepaper?tab=readme-ov-file#philosophy

We even have a full specs for an Actor to run GPT prompts against Dataset: https://docs.google.com/document/d/1wVCNDY5Sv8dLcpcP4JEnSbRxgNkX9IHjC9U4ACu1tGc/edit?tab=t.0

CC @tomasjindra

@Patai5 Patai5 added the cancelled For cancelled Issues for various reasons label Oct 27, 2024
@Patai5
Copy link
Contributor Author

Patai5 commented Oct 27, 2024

Right, I see, good points 👍 Yeah, making it a standalone Actor would be better :)

@Patai5 Patai5 closed this as not planned Won't fix, can't repro, duplicate, stale Oct 27, 2024
@PavlinaVencovska
Copy link
Contributor

@metalwarrior665 Sounds like out of the scope of our team, who do we delegate this on to make it happen?

@metalwarrior665
Copy link
Contributor

I think the Video team can do it, not huge priority

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cancelled For cancelled Issues for various reasons enhancement New feature or improving/enhancing the existing ones for end users priority: nice to have Small bug or feature. Put to backlog and long-term planning. source: internal Reported or found out by us zenhub: product backlog
Projects
None yet
Development

No branches or pull requests

4 participants