-* What database migrations will accompany this change.
-
-* How will the initial set of new data objects be generated, for example if you
- need to take into account existing instances, or modify other existing data
- describe how that will work.
-
-REST API impact
----------------
-
-Each API method which is either added or changed should have the following
-
-* Specification for the method
-
- * A description of what the method does suitable for use in
- user documentation
-
- * Method type (POST/PUT/GET/DELETE)
-
- * Normal http response code(s)
-
- * Expected error http response code(s)
-
- * A description for each possible error code should be included
- describing semantic errors which can cause it such as
- inconsistent parameters supplied to the method, or when an
- instance is not in an appropriate state for the request to
- succeed. Errors caused by syntactic problems covered by the JSON
- schema definition do not need to be included.
-
- * URL for the resource
-
- * URL should not include underscores, and use hyphens instead.
-
- * Parameters which can be passed via the url
-
- * JSON schema definition for the request body data if allowed
-
- * Field names should use snake_case style, not CamelCase or MixedCase
- style.