{"id":"6892441013704b029009b2c7","title":"2025 08 05","path":"how-to/committee/release-notes/2025-08-05","contentMarkdown":"# 8th Aug 2025 — [Support for Hybrid population of events #34](https://github.com/nbarrett/ngx-ramblers/issues/34)\n## [build 204](https://github.com/nbarrett/ngx-ramblers/actions/runs/16755488442)\n- This release completes [Issue 34](https://github.com/nbarrett/ngx-ramblers/issues/34). When Walks and Social Event data are configured to use Hybrid data population in System Settings (`admin/system-settings?tab=area-group`), local and remote event data will be automatically blended together.\n- To enable this feature, choose Hybrid in the Walk and/or Social Event Population:\n\n\n\n- This enables a group to import any amount of historic data e.g. via CSV file import and for live ramblers API data to be seamlessly blended with this.\n- In addition, a performance improvement has been made in this release that enables a direct lookup of a ramblers walk id when a [slug](https://en.wikipedia.org/wiki/Slug_(publishing)) is provided in the website url after the `walks/` or `social-events/`path in order to view a single event. NGX-Ramblers now automatically maintains a url to id linkage in the local database which avoids needing to do a full historic lookup of all events via the Ramblers events API and then match by slug. This fixes a performance issue introduced by [#10 SEO-friendly walk links](https://github.com/nbarrett/ngx-ramblers/issues/10).\n- When visiting the `walks/admin/event-data-management` page, event statistics can be viewed grouped by Event Type, Group Code and Input Source as shown in the screenshot below:\n\n\n\n- The **Input Source** can be any of the following values:\n - **Url To Id Lookup**: A linkage between the event url (e.g. https://www.ramblers.org.uk/go-walking/group-walks/evening-walk-candlestick-loop-essendon-4-miles-7km-leisurely-booking) and the id (e.g. **100365968**)\n - **File Import**: The event was imported from a CSV File\n - **Walks Manager Import**: The event was imported from Walks Manager directly via the API (because the group switched from Walks Manager to Local event population)\n - **Manually Created**: The event was created manually within the local event population workflow.\n - **Unknown**: The input Source is not known or set yet (in the case of historic walks that have been manually input prior to this release).","contentHtml":"\n\n\n- This release completes Issue 34. When Walks and Social Event data are configured to use Hybrid data population in System Settings (
admin/system-settings?tab=area-group), local and remote event data will be automatically blended together. \n- To enable this feature, choose Hybrid in the Walk and/or Social Event Population:
\n
\n![\"\"](\"https://ngx-ramblers.org.uk/api/aws/s3/site-content/f52c30bc-6598-4733-8049-c9cc12bc2a0d.jpg\")
\n\n- This enables a group to import any amount of historic data e.g. via CSV file import and for live ramblers API data to be seamlessly blended with this.
\n- In addition, a performance improvement has been made in this release that enables a direct lookup of a ramblers walk id when a slug is provided in the website url after the
walks/ or social-events/path in order to view a single event. NGX-Ramblers now automatically maintains a url to id linkage in the local database which avoids needing to do a full historic lookup of all events via the Ramblers events API and then match by slug. This fixes a performance issue introduced by #10 SEO-friendly walk links. \n- When visiting the
walks/admin/event-data-management page, event statistics can be viewed grouped by Event Type, Group Code and Input Source as shown in the screenshot below: \n
\n![\"\"](\"https://ngx-ramblers.org.uk/api/aws/s3/site-content/8a20a352-5863-49a1-ac79-4e2f44afdae4.jpg\")
\n\n- The Input Source can be any of the following values:
\n- Url To Id Lookup: A linkage between the event url (e.g. https://www.ramblers.org.uk/go-walking/group-walks/evening-walk-candlestick-loop-essendon-4-miles-7km-leisurely-booking) and the id (e.g. 100365968)
\n- File Import: The event was imported from a CSV File
\n- Walks Manager Import: The event was imported from Walks Manager directly via the API (because the group switched from Walks Manager to Local event population)
\n- Manually Created: The event was created manually within the local event population workflow.
\n- Unknown: The input Source is not known or set yet (in the case of historic walks that have been manually input prior to this release).
\n
\n \n
\n"}