/answer does not return Document metadata

[nenb]

Bug description

(I'm not sure if this is a bug or just user error, or deliberately intended.)

When I store Document metadata in the database, it's not returned when I make a request to /answer. This is unfortunate as the metadata contains lots of useful information about the data source that I would like to display.

How to reproduce the bug?

Upload a single document with metadata.

Make a request to /answer and inspect the response.

Versions and dependencies used

All

Anything else?

No response

[pmeier]

/chats/{id}/answer

ragna/ragna/deploy/_api/core.py

Lines 258 to 264 in 4a667f9

	@app.post("/chats/{id}/answer")
	async def answer(
	user: UserDependency,
	id: uuid.UUID,
	prompt: Annotated[str, Body(..., embed=True)],
	stream: Annotated[bool, Body(..., embed=True)] = False,
	) -> schemas.Message:

returns a Message

ragna/ragna/deploy/_api/schemas.py

Lines 54 to 61 in 4a667f9

	class Message(BaseModel):
	id: uuid.UUID = Field(default_factory=uuid.uuid4)
	content: str
	role: ragna.core.MessageRole
	sources: list[Source] = Field(default_factory=list)
	timestamp: datetime.datetime = Field(
	default_factory=lambda: datetime.datetime.utcnow()
	)

So, directly, no document is returned here at all. The document is part of the Sources that are being returned

ragna/ragna/deploy/_api/schemas.py

Lines 35 to 41 in 4a667f9

	class Source(BaseModel):
	# See orm.Source on why this is not a UUID
	id: str
	document: Document
	location: str
	content: str
	num_tokens: int

Finally we arrive at the Document that indeed does not contain the metadata

ragna/ragna/deploy/_api/schemas.py

Lines 18 to 20 in 4a667f9

	class Document(BaseModel):
	id: uuid.UUID = Field(default_factory=uuid.uuid4)
	name: str

Since we do have the metadata in the DB already, it shouldn't be too hard to link it back to the Document model. Doing that should fix this.

[pmeier]

I've played around with it for a bit and I think this is more a feature request than a bug. That being said, I think the change is for the better. I started a branch in #355. However, this includes breaking changes. I'd rather wait after the 0.2.0 release to merge this.