Reorganize example/test data locations

Related to #13

copier.yaml

@@ -142,11 +142,10 @@ _skip_if_exists:
   - LICENSE
   - README.md
   - project/*
-  - src/docs/files/about.md
-  - src/{{project_slug}}/data/*
   - src/{{project_slug}}/datamodel/*
   - src/{{project_slug}}/schema/*
   - tests/test_data.py
+  - tests/data/*
 
 _message_after_copy: |
 

template/README.md.jinja

@@ -10,7 +10,7 @@
 
 ## Repository Structure
 
-* [examples/](examples/) - example data
+* [examples/](examples/) - Examples of using the schema
 * [project/](project/) - project files (these files are auto-generated, do not edit)
 * [src/](src/) - source files (edit these)
   * [{{project_slug}}](src/{{project_slug}})
@@ -19,14 +19,15 @@
     * [datamodel](src/{{project_slug}}/datamodel) -- generated
       Python datamodel
 * [tests/](tests/) - Python tests
+* [tests/data](tests/data) - Example data
 
 ## Developer Documentation
 
 The pre-defined commands are written for the command runner [just](https://github.com/casey/just/).
 Use the `just` commands to generate project artefacts:
 * `just` or `just --list`: list all pre-defined tasks
-* `just site`: (re-)create everything
-* `just deploy`: deploys site
+* `just site`: (re-)generate project artefacts & documentation
+* `just deploy`: deploy documentation site to GitHub pages
 
 ## Credits
 

template/examples/README.md.jinja

@@ -1,5 +1,5 @@
-# Examples of use of {{project_slug}}
+# Examples of using {{project_slug}}
 
-This folder contains example data conforming to {{project_slug}}
+This folder contains examples using the datamodel.
 
-The source for these is in [src/data](../src/data/examples)
+The source of the data used in the example is [tests/data](../tests/data/).

template/tests/data/README.md.jinja

@@ -0,0 +1,7 @@
+# Example data for {{project_slug}}
+
+This folder contains example data for testing and demonstrating the datamodel` sorted in subfolders:
+
+- `valid` for data conforming to the datamodel. Used to verify the datamodel.
+- `invalid` for data not conforming to the datamodel. Used to verify the validation.
+- `problem` for data which are not yet handled correctly in the current schema version, again separated into valid/invalid.