You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the Figure Enrichment tutorial it is easy to add classification metadata to an image through the element.annotations.append(data) function.
However this data is not stored during the export to Markdown format. Would there be a way to write it alongside the image path in the final MD document ? Would be great for our RAG application.
The text was updated successfully, but these errors were encountered:
I'm searching for a way to add context to images of my pdfs which will eventually help in image summarization.
Is picture enrichment the answer ?
@gauravmindzk What I meant by "picture enrichment" was model captionning with a vision LLM, with added context from the document. For my use case, I used [this template] https://ds4sd.github.io/docling/examples/develop_picture_enrichment/ ) as a base to set up a call to an on-premise Pixtral instance to caption the images, and then store the answer in the annotations field.
We have some idea on how to enable the serialization of that data when exporting to markdown or other formats.
@dolfim-ibm Thanks for your feedback, I didn't know about the PictureMiscData field. I forked the docling_core project and wrote a crude "ANNOTATION" markdown export format that writes the content of the annotations as the "alt" description for the image in the MD file. That solution fits my need for now, but its nice to know that you have some plans to serialize it in the future.
Image annotations to MD
Following the Figure Enrichment tutorial it is easy to add classification metadata to an image through the
element.annotations.append(data)
function.However this data is not stored during the export to Markdown format. Would there be a way to write it alongside the image path in the final MD document ? Would be great for our RAG application.
The text was updated successfully, but these errors were encountered: