wamnet-provider-sync

To sync WAM NET provider data to Neo4j, the Skill applies delta synchronization by downloading open data CSVs, detecting new, changed, and closed providers, and updating the Neo4j ServiceProvider nodes accordingly.

Delta synchronization detects closed service providers by comparing WAM NET CSV updates against existing Neo4j nodes, flags them as closed, and analyzes the impact on clients using those providers to generate update reports.

Yes, you can normalize Shift-JIS CSV files from WAM NET for Neo4j import. The Skill automatically handles Shift-JIS CSV inputs, normalizing service types and phone numbers before converting them into Neo4j graph format.

The best way to generate update reports across prefectures is using delta synchronization that detects changes in WAM NET open data, analyzes client impact, and outputs reports detailing new, changed, and closed service providers.

Yes, you need Neo4j and python-dotenv to run WAM NET data synchronization. Neo4j serves as the database for ServiceProvider nodes, while python-dotenv manages environment configurations for the scripts.

WAM NET CSV data synchronization requires normalizing service types and phone numbers to ensure consistent Neo4j node properties and accurate delta detection when comparing updated provider records against existing database entries.