* Explore and understand [Cache Configuration](https://ignite.apache.org/docs/latest/configuring-caches/configuration-overview) options within Ignite. Should we allow user to set any of these options themselves?
* Can we optimize the run Transformer process into a simpler script?
* Instead of running `mvn clean install -DskipTests` then running `java -jar -Dspring.profiles.active=local osdu_gcz_transformer-\[VERSION\].jar`... Is there any way we can make this happen in a succinct one-liner? - I am not as familiar with Java capabilities in this regard.
* Investigate best practices regarding authentication with OSDU and how we should be storing/accessing parameters like clientId, clientSecret, etc. (I know Bryan is looking at this one, but if you were interested.. this is one we eventually have to address)
## Provider
* Familiarize with the Provider codebase
*`ignite-provider/src/model.js` and `ignite-provider/lib/ignite-client.js` are the key files to review
* How can we implement logging in the Provider?
* Review Popular NodeJS Logging libraries like winston and pino
* Can we add logs to the Provider at vulnerable/error points, and log all requests processed by Koop?
* Can we setup a nodejs package.json script for running the Provider and consecutively running ngrok without the user having to open command prompt and do it themselves?
* There is an [npm package](https://www.npmjs.com/package/ngrok) for `ngrok`
* We would have to store some ngrok auth info in a config file
## CSP
* Support IBM
* Investigate what it would take to configure an Ignite Cluster and have it accessible by Ignite Thick Clients (like our Transformer) in a Kubernetes environment (Cluster on one Pod and Thick Client in another pod)
* Consider spinning up a local Kubernetes environment using [Minikube](https://minikube.sigs.k8s.io/docs/start/) and testing a GCZ deployment within a controlled environment
* Expand Deployment/Ignite Knoweldge
* When leveraging remote profile, user has ability to configure their own Ignite Cluster for use in the GCZ
* If Ignite Cluster has [persistence](https://ignite.apache.org/docs/latest/persistence/native-persistence) enabled, does the Transformer still work? How about when the Ignite cluster is restarted. Does the data populated by our Transformer persist? How much disk space is it taking up?
## Administration
* Mock up or outline a user experience for configuring both the Transformer and Provider
* Transformer
* Walkthrough and provide Form that lets user create, review, or edit their configuration
* Handle faulty values
* Provider - Guide user through a Layer Definition Configuration process
* Walkthrough and provide Form that lets user create, review, or edit their configuration
* One nice-to-have feature here would be...
* Once user has entered Ignite connection details and geometry type, etc... construct a NodeJS thin client on the backend that connects to that cache and if it is running.. provide back a list of all possible Fields that are able to be pulled down. From there the user could individually select fields and provide their own custom labels, geometry types, etc.
