Improved terminal matching and a new unmatched terminals review tool
What's new
- Unmatched terminals review page — when route imports bring in terminal names that don't match known hubs or nodes, admins can now review them in a dedicated page and resolve each one: confirm it as a known node, group it under an existing hub, or create a brand-new hub from it
- "Create new hub" dialog — when creating a hub from an unmatched terminal, you can now edit the hub name before confirming
- Hub grouping dialog shows addresses — both the candidate terminal and the existing hub now display their addresses side by side, making it easier to confirm you're grouping the right locations together
- Smarter name matching on import — node names are now matched case-insensitively during import sync, significantly reducing false "unmatched" results caused by capitalisation differences
- Cleaner auto-generated names — hub and node names created from import data are now properly capitalised instead of using raw import strings
- Route import trigger — admins can now manually kick off a DI route import directly from the route-imports admin page
- Copyable error messages — error notifications on the import pages are now persistent and text-selectable, making it much easier to capture and share error details
What's coming next
- Automatic creation of new nodes directly from the unmatched terminals list, reducing the manual steps needed to get new terminals into the system
Leave a Reply