Navigate tool (clickable IDs)

[jankrepl]

This ticket is blocked by the actual frontend completely switching to entitycore and using entitycore identifiers everywhere.. Update, the migration to entitycore was done. So we can work on this ticket.

Idea

We introduce a new env var - frontend url.

The tool itself will be a url generator that takes in

• entity_route: Literal["reconstruction-morphology", ...]
• entity_id: UUID | None - if UUID provided it would point at the GET ONE page and if not it would point at a GET ALL page.
• ... (maybe some query params since the frontend does seem to suport query params like brainRegion)

And it spits out a valid URL in the frontend. You can figure out those urls by just browsing the frontend or checking the actual Next.js code and inspecting the page hierarchy. The user could then click on it in the chat if they want to be redirected there.

For example, see below a url of a reconstruction morphology

f"{frontend_url}/app/virtual-lab/explore/interactive/experimental/morphology/{morphology_id}"

EDIT:
I just created a ticket that could simplify our life here for single entity pages: https://github.com/openbraininstitute/prod-explore-functionality/issues/245

[jankrepl]

So maybe this should be done as a rule rather than as a tool. Follow up to #387

[BoBer78]

There might be a resolving url in NextJs to be able to resolve the ID of entities.

[evakennyobi]

Can you add planned start / end dates for this please @BoBer78

It also still requires resources from others (frontend?). Is that already covered in a separate ticket & labelled 'up next' for discussion on Friday? Thanks

[BoBer78]

This will indeed require some resources from the frontend. I added the up_next tag so that we can discuss on Friday.