Parse ZSPs and store as appropriate datastructure

[birgitlewicki]

Currently the ZSPs have a condensed form with few lines containing ranges of codes.

During the server startup the ZSPs are parsed and each catalog code in the given ranges are checked against the corresponding ADV catalog if it is a valid code. This procedure needs some time and as a consequence the server startup time takes to long.

Because the check for valid codes needs to be done only when we have a catalog update this parsing and checking process will be moved to a script in master-data. This script has only to run after a catalog update. As a result the script will store the ZSPs in an appropriate data structure that will be read into memory directly during server startup without having the longer parsing and checking procedure.

For an appropriate data structure 2 options are checked:

• store the data structure in the db
• store the data structure in a file (similar to the current situation)

[birgitlewicki]

During the initialization of the server the ADV catalogs and ZSPs are parsed, processed and stored in memory which slows down the server boot process. This process is moved to master-data. The resulting catalog data structure is stored in json files. The server now just has to read the json files into memory which goes quite fast.