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

MetadataBuilder #5702

Open
Tracked by #5330
sjrl opened this issue Sep 1, 2023 · 5 comments
Open
Tracked by #5330

MetadataBuilder #5702

sjrl opened this issue Sep 1, 2023 · 5 comments
Assignees
Labels
2.x Related to Haystack v2.0 P2 Medium priority, add to the next sprint if no P1 available type:feature New feature or request

Comments

@sjrl
Copy link
Contributor

sjrl commented Sep 1, 2023

See the proposal: #5540 and see feature request for Haystack v1


LLMs clients output strings, but many components expect other object types, and LLMs may produce output in a parsable format that can be directly converted into objects. Output parsers transform these strings into objects of the user’s choosing.

MetadataBuilder. It takes the string replies and inserts them as metadata into the Documents that were originally passed to the LLM. I'm open to renaming this one, since the goal would be to output Documents with inserted metadata.

For example, a PromptNode could be used to summarize a longer doc and the user would like to have the result inserted as metadata for that Document. There it would allow us to easily add category tags, sentiment, summaries (...) to docs that can be utilized later at query time (e.g. to filter down the search space efficiently or utilize the metadata for online retrieval/generation steps)

@sjrl sjrl added the 2.x Related to Haystack v2.0 label Sep 1, 2023
@sjrl sjrl mentioned this issue Sep 1, 2023
@Timoeller Timoeller added the P2 Medium priority, add to the next sprint if no P1 available label Oct 12, 2023
@mathislucka mathislucka added the type:feature New feature or request label Dec 22, 2023
@masci masci added this to the 2.0.0 milestone Jan 8, 2024
@anakin87
Copy link
Member

More information on the expected use cases and component I/O can be found here.

In general, it is probably best to focus on developing this component once looping and input lists are handleable by the Pipelines.
(Otherwise, we would be going to build a component that is effectively unusable in the Pipelines.)

@anakin87 anakin87 removed their assignment Jan 22, 2024
@masci masci modified the milestones: 2.0.0, 2.1.0 Feb 23, 2024
@masci masci added P3 Low priority, leave it in the backlog and removed P2 Medium priority, add to the next sprint if no P1 available labels Feb 23, 2024
@masci masci removed this from the 2.1.0 milestone Apr 1, 2024
@mrm1001 mrm1001 added P2 Medium priority, add to the next sprint if no P1 available and removed P3 Low priority, leave it in the backlog labels Jun 28, 2024
@julian-risch
Copy link
Member

@sjrl We are considering this issue for our next sprint. Is there any new info that will be relevant for the implementation of this component?

@anakin87
Copy link
Member

This is probably relevant: https://www.notion.so/deepsetai/Advanced-Use-Case-Automatic-Metadata-Enrichment-8fdfc56e82434459963beaa7a9dc5069

@sjrl
Copy link
Contributor Author

sjrl commented Jun 28, 2024

Hey @julian-risch thanks for reaching out! No new info on my end. I think the work @davidsbatista did that @anakin87 linked is exactly the type of use case we are thinking about. In general metadata enrichment of files to help with retrieval through filters, embed meta fields, etc. Also possibly for downstream applications (e.g. they want to show a summary along side a retrieved file). I'd be particularly interested in a set up that would allow me to automatically extract things like title, authors, publication date, etc. from PDF files and then save that as metadata with the file.

@davidsbatista
Copy link
Contributor

see #5700 - it's related/duplicated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.x Related to Haystack v2.0 P2 Medium priority, add to the next sprint if no P1 available type:feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants