{"id":"672d6dbcd8ea94015d7fa56f","title":"2024 11 08","path":"how-to/committee/release-notes/2024-11-08","contentMarkdown":"#  3rd-8th November 2024 - Created Walks Import facility\n## [Build #39](https://github.com/nbarrett/ngx-ramblers/actions/runs/11734493167/job/32690611173)\n- Created Walks Import facility for use when a group wishes to switch from walks manager population to local.\n- All walk history is copied from walks manager and attempt is made to match historic walks to existing members in Member Admin.\n- If no match is found for a detected walk leader, a minimal member record is created and the associated walks are linked to the member.\n- Changes were made to the Bulk load service to accommodate contact based matching and data population for the above but existing matching logic for monthly data loads remains the same as before.\n- When walks are imported successfully, a prompt is given the switch walks population to Local.\n- If the walks import was not successful, the failing members/walks are highlighted. At this point, it's up to the person running the import to decide whether sufficient historic data is available to continue with the local walks switchover.\n- As part of this commit, all references to Assemble names have been removed as Assemble has been decommissioned by Ramblers.\n- Due to the creation of the Walks Import, the walks/admin page is now accessible by any member that has Walk Admin privs. Previously this could only be navigated to by a member with Walk Admin privs and the walks population was local.\n- Logic for determining whether walk lead button is shown changed to accommodate new rules.\n- Screenshot of page after performing initial data collection but before copying is shown below:\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/977f1beb-839d-46ed-9d01-2320a0d7a40c.jpg)","contentHtml":"<h1>3rd-8th November 2024 - Created Walks Import facility</h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/11734493167/job/32690611173\">Build #39</a></h2>\n<ul>\n<li>Created Walks Import facility for use when a group wishes to switch from walks manager population to local.</li>\n<li>All walk history is copied from walks manager and attempt is made to match historic walks to existing members in Member Admin.</li>\n<li>If no match is found for a detected walk leader, a minimal member record is created and the associated walks are linked to the member.</li>\n<li>Changes were made to the Bulk load service to accommodate contact based matching and data population for the above but existing matching logic for monthly data loads remains the same as before.</li>\n<li>When walks are imported successfully, a prompt is given the switch walks population to Local.</li>\n<li>If the walks import was not successful, the failing members/walks are highlighted. At this point, it&#39;s up to the person running the import to decide whether sufficient historic data is available to continue with the local walks switchover.</li>\n<li>As part of this commit, all references to Assemble names have been removed as Assemble has been decommissioned by Ramblers.</li>\n<li>Due to the creation of the Walks Import, the walks/admin page is now accessible by any member that has Walk Admin privs. Previously this could only be navigated to by a member with Walk Admin privs and the walks population was local.</li>\n<li>Logic for determining whether walk lead button is shown changed to accommodate new rules.</li>\n<li>Screenshot of page after performing initial data collection but before copying is shown below:</li>\n</ul>\n<p><img src=\"https://ngx-ramblers.org.uk/api/aws/s3/site-content/977f1beb-839d-46ed-9d01-2320a0d7a40c.jpg\" alt=\"\"></p>\n"}