search

ThreeSixtyGiving / datatester

Scripts to asses the quality of data from http://data.threesixtygiving.org
MIT License
3 stars 2 forks source link

PSA - Repo name change datagetter->datatester #44

Closed michaelwood closed 4 years ago

michaelwood commented 5 years ago

In order not to create conflicting dependencies on the datastore which will use the datagetter the getter part and the quality parts are now in separate repos. datatester and datagetter.

For continuity of service this repo is just a rename of the datagetter so can be considered unchanged. When the datagetter is ready as a separate project this project will depend on it and the datagetter parts will be removed. See issue #45

robredpath commented 5 years ago

I'm not sure that dataquality is the best name for this, as there's already a Data Quality Tool in the 360Giving world. I thought we'd said that we were separating out the 'daily data test' components from the 'datagetter' components? daily-data-test then feels like an appropriate name to use.

michaelwood commented 5 years ago

I went with dataquality because of the presence of checks/validation (via cove) and various reports being generated by this collection of scripts. I wasn't sure if the tests are always going to be 'daily' so didn't include that. I'm not wedded to this name though! happy for more experienced folk to determine a better name.

robredpath commented 5 years ago

Good point. Maybe datatester to go alongside datagetter? Although, the 'daily data test' is a well-established part of the 360Giving data infrastructure, so it is likely to be daily for a long time. More frequent doesn't make sense (the standard has daily granularity baked in), and less frequent is less useful.

michaelwood commented 5 years ago

Sure - Updated to datatester