Refactor Cypher queries and setup instructions to use ri-neo4j-importer
As the integration of additional departments in the dataset required more complex Cypher scripts and conditional statement execution, the Neo4j data import is not handled by the resources/import-regf3.cypher
script of this repository anymore. Instead, the ri-neo4j-importer CLI application was implemented to handle all imports. Therefore, this application should be updated to make use of the new importer. This concludes of the following aspects:
Remove import script and upate documentation
The resources/import-regf3.cypher
should be removed and the documentation should be adjusted to explain how the dataset should be created via the ri-neo4j-importer.
Update property names in Cypher queries
The importer also refactors the dataset by adjusting various property names (e.g. by translating them from german to english for a more unified naming). The Cypher queries performed by this backend should be refactored to use these new names instead of the old ones to establish compatibility with the new dataset.
Switch to Neo4j 5
Finally, the database was migrated to Neo4j 5 (as described in #1 (closed)). Therefore, the Neo4j version used by this project should be upgraded to Neo4j 5, too. This includes switching to the version 0.0.4
of the neo4j-normalizer-plugin that establishes compatbility and fixes issues with the normalization of non-standard HTML tags.