Document Data Loading Validation Logic

ADD TO THIS DOCUMENT: https://github.com/earthcube/geocodes_documentation/wiki/DataLoadingValidationStory#what-do-we-need-do-to-setup-testing

Document the testing that will be needed to validate the data loading.
Repeat, document the steps we will need to implement to validate the data loading.

This is not asking for the implementation of the tests. It is asking for the testing plan with the steps that will will need to implement.

Places to possibly look:

- https://github.com/gleanerio/notebooks
- https://github.com/fils/EarthCubeGraphAnalytics

Tasks:

[x] **Spec**: Summon working
[x] **Spec**: expected JSON-LD
[x] **Spec**: JSON-LD data load to triple store
[ ]**Spec**: JSON LD Renders in UI
[ ] **Spec** Tool Linkage:
[ ] spec: org provenance information
[ ] **SPEC** automate use Geocode_Metadata_Approval tests as part of a CI workflow
[ ] **SPEC** SHACL and other validation of full source/repository data

### Examples

**Spec**: Summon working
[x] we have earthcube reports in the scheduler, and tests in the geocodes metadata
* count of records from a sitemap (matches) count of records that made it into the bucket
* possible tool: [sitemap assay](https://github.com/gleanerio/notebooks/blob/master/notebooks/sitemap_assay.ipynb)

**Spec**: expected JSON-LD
[x] approval tests in the geocodes metadata
possible tooling: https://github.com/gleanerio/notebooks/tree/master/notebooks/validation
* validate jsonld using ?
* does it have xxxx

**Spec**: JSON-LD data load to triple store
[x] we have earthcube reports in the scheduler,
* count of files in s3 bucket (matches) count of graphs for an organization/record
* For (% of data load or all if < 100 records)
* retrieve JSONLD
* urn
* name
* retrieve a graph by a urn from the service api
* did we get a record
* does information (name, urn, [other properties]) match
* retrieve from triplestore using user interface query with name as

**Spec**: JSON LD Renders in UI
* for a random number of jsonld in org.
* create a set of curl url
* open in a web test suite (selenium, etc) and see that they at least partially render to expectations

**Spec** Tool Linkage:
* for a set of known files, do we match the look linkages.
* This probably needs to be an approval test.

spec: org provenance information
* where is the org provenance, does it look useful.
* pssoble tool: https://github.com/gleanerio/notebooks/blob/master/notebooks/exploring/orgAndProv.ipynb

**SPEC** automate use Geocode_Metadata_Approval tests as part of a CI workflow

**SPEC** SHACL and other validation of full source/repository data