- Sep 03, 2024
-
- Aug 28, 2024
-
-
Stephanie Freitag authored
HOLI-9693: retry geometry lookup using place name when receiving point See merge request app/holi-app-volunteering!46
-
Stephanie Freitag authored
-
Stephanie Freitag authored
-
Stephanie Freitag authored
HOLI-9570: add endpoint to filter engagements from the DB by terms and location See merge request app/holi-app-volunteering!44
-
- Aug 27, 2024
-
-
Ole Langbehn authored
-
Stephanie Freitag authored
Co-authored-by:
Daniel Bimschas <daniel.bimschas@holi.team>
-
- Aug 26, 2024
-
-
Stephanie Freitag authored
-
Stephanie Freitag authored
-
Stephanie Freitag authored
-
Stephanie Freitag authored
-
Stephanie Freitag authored
-
- Aug 23, 2024
-
-
Ole Langbehn authored
-
Ole Langbehn authored
-
Daniel Bimschas authored
NOISSUE: increase fmt line-width to 120 See merge request app/holi-app-volunteering!45
-
Daniel Bimschas authored
HOLI-9527: add fields `matchedTopics`, `matchedSkills` and `matchedGeoLocationDistanceInMeters` See merge request app/holi-app-volunteering!43
-
Daniel Bimschas authored
-
Daniel Bimschas authored
-
Daniel Bimschas authored
-
Daniel Bimschas authored
-
Daniel Bimschas authored
-
- Aug 22, 2024
-
-
Daniel Bimschas authored
-
- Aug 20, 2024
-
- Aug 19, 2024
-
-
Daniel Bimschas authored
-
Daniel Bimschas authored
HOLI-9555 location based recos tests See merge request app/holi-app-volunteering!42
-
Daniel Bimschas authored
-
Daniel Bimschas authored
HOLI-9524: use index and fix distance calculation See merge request app/holi-app-volunteering!41
-
- Aug 18, 2024
-
-
Daniel Bimschas authored
This commit extends the `Engagement` type by three new fields that are set if used in a recommendation query response: * `matchedTopics` * `matchedSkills` * `matchedGeoLocationDistanceInMeters` The first two fields contain topics and skills that a recommendation query asked for if (and only if) those were the reason for the recommendation to include a given engagement in the response. A match will only be included if it surpasses a certain threshold (set to 0.5 in this commit). If `geoLocationId` is passed as a query parameter`matchedGeoLocationDistanceInMeters` contains the distance in meters from the geolocation resolved from `geoLocationId`to the geolocation of the engagement opportunity.
-
- Aug 16, 2024
-
-
Daniel Bimschas authored
-
Daniel Bimschas authored
-
- Aug 15, 2024
-
-
Daniel Bimschas authored
* query now (implicitly) uses the HNSW index on embedding_array * query now uses the `<#>` operator to sort by distance which can (and will) take advantage of the index for the newly introduced `location_gps` column which combines (`longitude`,`latitude`) into a PostGIS geometry * distance calculation is fixed - it calculated before with two different units (distance in "angle" (RSID 4326) vs. distance in meters (RSID 3857, Pseudo-Mercator plane projection))
-
- Aug 14, 2024
-
-
Daniel Bimschas authored
-
- Aug 13, 2024
-
-
Daniel Bimschas authored
HOLI-9542 resolve lat lng using geolocationId See merge request app/holi-app-volunteering!40
-
Daniel Bimschas authored
-
Daniel Bimschas authored
HOLI-9483 add location as a weighted ranking criterion to recommendations See merge request app/holi-app-volunteering!37
-
Daniel Bimschas authored
-
Salih Hasan Siddiqi authored
-
- Aug 12, 2024
-
-
Salih Hasan Siddiqi authored
-
Salih Hasan Siddiqi authored
-