Store data collection workbooks in repository?

[Brian Lewis]

Need better configuration management around these objects which are central to the operation in countries where they are used.

However, since these will not be diffed (?) but overwritten en as binary files; they could have a big effect on the size of the repo?

Also, it could be worth considering an export function that exports all code modules to external files; which then could in themselves be managed and diffed. This would provide better insight into code fixes and changes than just storing the versioned workbook. (This would be similar to the philosophy of storing Sql objects in the repo to provide history)

[Brian Lewis]

@ghachey your thoughts?

[Ghislain Hachey]

I still rather they are committed as binary files also to make pulling out the latest WK easy. On the same commit you can also export all core modules to external files. Something like

External Tools
  Annual Census Workbook
    Workbooks
    Core Modules

The workbooks would keep the latest master for each country adopting this.

The exports of all code modules is that something that comes in built in with Excel?

No data to be included as this is public repository.

[Ghislain Hachey]

Considering this resolved. Next requirements will be as part of next verison of workbook