Frank Elsinga
Frank Elsinga
This Issue tracks: - **who uses the API**, - **what features** you are using and - **what change-timelines** ("I need 3 Weeks at minimum, because ...") you would prefer. If...
Fixes https://github.com/TUM-Dev/NavigaTUM/issues/942 Maybe #960 Maybe #30 ## Proposed Changes (include Screenshots if possible) - Adds the ability to index via a vector store - Added the ability to search via...
as mentioned in https://github.com/TUM-Dev/navigatum/blob/main/deployment/README.md we still need to tap into the potential datasources of the physics roomfinder
This issue is here to collect requested WC changes in one issue until we have a more scalable Feedback system. *Key* | Links | Comment | |---|---|---| | 0509.EG.926 |...
**Is your feature request related to a problem? Please describe.** Our searching library, meilisearch has introduced hybrid search in the last release. This allows using vector embeddings and thus allows...
Fixes #669 ## Proposed Changes (include Screenshots if possible) - Extracted the Coordinate picking logic to its own component (also prepares us for #501) - Added an E2E Test to...
**Is your feature request related to a problem? Please describe.** Currently, we don't do a good job communicating learning-room availability to our users. **Describe the solution you'd like** If on...
**Is your feature request related to a problem? Please describe.** Currently, our project involves a lot of manual cloning, checking if everything works and letting checks run. This could be...
**Is your feature request related to a problem? Please describe.** Our overlay quality is very dependent on the building and on the data the Roomfinder has on this. **Describe the...
**Is your feature request related to a problem? Please describe.** Our Search weights probably need some tinkering. We saw, in #283, that our current approach most likely is not optimal....