The following is a description on how you can to use a custom category set that will map to 211’s taxonomy terms. This will allow the client to maintain it’s its own list of category and subcategory terms.
Step 1 - Create a custom mapping
A custom category and subcategory mapping will be creating category and subcategories that will be can be created that is more intuitive to your users instead of the 211 LA tax County taxonomy terms. Each category and subcategory needs to be mapped to a taxonomy idTaxonomy term ID. Michigan 211 can help coming up with this to create a category/subcategory list.
Step 2 - Store the custom mapping to a database
Store the mappings into a database or text file that can drive your UI to have the user of the application be able to select the services by your category and subcategory set. Below is a an example of the structure that needs to be stored.
...
The user interface will allow the user to select the category, subcategory, and geographic parameters (ex: zip code). The following below is an example of what the user interface might be.
...
Step 4 - Get the taxonomy id from the custom database
Once the user has selected the parameters for the query. The taxonomy id ID can then be received given the category and subcategory in the custom database.
Step 5 - Call [GET /services/complete] call with the filter query string parameter
Now that we have the the taxonomy idID, a zip code parameter can also be added in the example below. The zip code will only return services that are supported available for that zip code.
The filter for this call will be {"$area:like":{"type":"zipcode","$table.field":[{"service_program_taxonomy.taxonomy_id":["FP0700.5000"]}],"name":"48235","distance_info":{"type":"zipcode","name":"48235"}}}
...