Use Pentaho's open source data integration tool (Kettle) to create Extract-Transform-Load (ETL) processes to update a Socrata open data portal. Documentation is available at http://open-data-etl-utility-kit.readthedocs.io/en/stable
Since the documentation recommends putting Kettle folders within the kit folder structure I would suggest adding data-integration*/ to .gitignore
Maybe also add DataSync/config.json so that password and connection settings are not accidently committed to a public repo. I'm not sure. There are also other settings that end up saved in generic files like the Email settings in open-data-etl-kit/ETL/Utilities/ETL_Completion_E-Mail.ktr. It might be helpful to pull all settings like that out and put into `kettle.properties' or some other environment variable type file.
In general, I'm just trying to make it clearer what files & folders can be safely in a public repo vs which ones probably shouldn't be (config settings, dataset specific files, etc).
Since the documentation recommends putting Kettle folders within the kit folder structure I would suggest adding
data-integration*/to .gitignoreMaybe also add
DataSync/config.jsonso that password and connection settings are not accidently committed to a public repo. I'm not sure. There are also other settings that end up saved in generic files like the Email settings inopen-data-etl-kit/ETL/Utilities/ETL_Completion_E-Mail.ktr. It might be helpful to pull all settings like that out and put into `kettle.properties' or some other environment variable type file.In general, I'm just trying to make it clearer what files & folders can be safely in a public repo vs which ones probably shouldn't be (config settings, dataset specific files, etc).