The canis from gonzalo-roberto-diaz

create test infrastructure at the services level

Reproduce query cases for dogBreeds

Think about what where/order by clauses will be necessary for dog breeds.
Decide whether a "Specification" approach or simply an additional interface like in here: http://stackoverflow.com/questions/11880924/how-to-add-custom-method-to-spring-data-jpa
would be necessary for those.
Implement such complements.

create a new Database release 2.0

add validation for the breed insertion

Implement dev vs test configuration

replace config files with .yaml file with profiles.
make the canis-rest Application class work, as well as the integration tests, all pointing to the proper databases.

pass weight and size to metric

also ensure that distance are in KM

formula for serving size

create of retrieve a reliable formula for calculating the serving size
validate that cup sizes be given in quarters

separate dog-breeds from the main schema creation in liquibase

Clean up example classes

Clean up "Parent" classes from DAO, services and REST projects.

correct controllers' path for create and update

Implement example of parametric sort with page

create a test for the dog breeed validation

add more spitzer-primitive breeds

recalculate dog sizes

also refactor the way they are transformed to and from number

Services missing an interface implementation

Migrate DAO to SpringData

migrate to SpringData using SpringBoot
ensure that there is an H2 implementation for tests, handle auto-creation properly

http://spring.io/guides/gs/accessing-data-jpa/

set up the rest service as Spring Boot

make more columns in dog_breeds non-nullable

training rank and text
weight min and max
size min and max
shedding rank

Change JPA and domain classes according to database changes

create a type table, roughly in line with the types in http://www.fci.be

Ensure that USA and Canada have the same geo system

USA's system is more detailed at the moment, possibly unnecessarily.
Determine use cases, what use to make of Google, and what is stored after search.

set up liquibase

Use an exported script, and set up a directory structure for releases and the maven plugin.
Use SQL format for files.

merge the MAIN_FEATURES field into a "general description" initial text field, populate it.

implement unit tests on the REST layer

find a way to run the Integration Tests independently

implement queries by initial letter, name (substring) and category

implement integration tests on the REST layer

remove column

DOG_SHEDDING_AMOUNT_ID

create classes for DogBreed

Add basic REST controller, service and DAO.

replace shedding with more textual information

"amount" and "frequency" are inadequate to represent a dog's shedding

eagerly fetch many-to-one relationships to DogBreed

Use something like this:

@ManyToOne(fetch=FetchType.EAGER, optional= false, cascade = CascadeType.ALL )
@JoinColumn(name = "CHILD_ID",referencedColumnName="ID",nullable=false)
private Child child;

Release 2.0

Database work
- put everything on the database made so far into a "release 1.0" and start working freely (#22)
- create a type table, roughly in line with the types in http://www.fci.be (#23)
- add them to the database, remove the "dog purpose" section, classify according to the previous table (#24)
- merge the MAIN_FEATURES field into a "general description" initial text field, populate it.(#25)
- remove shedding amounts, add it to the text in grooming (#14)
- create a new base release 2.0 with all previous changes (#26)
Application work
- Change JPA and domain classes according to database changes (#27)
- implement queries by initial letter, name (substring) and category (#28)
- create a separate "model" class for interaction from the services layers up. Possibly builders.(#32)
- add validation for the breed insertion (#30)

put everything on the database made so far into a "release 1.0" and start working freely

remove the healthy columns

remove healthy rank and healthy text columns

transform dog size into an enumeration

Add test for dog breed insertion considering existing name

test adding a breed with existing name

Add lifespan to the dog breed information.

Race-related issues

move the Belgian Malinois as only one of the races of the Belgian Shepherd Dog, add the rest
put in the "Sections" (i,e, sheepdogs and cattledogs) under classification number 1
complete section 1 data entry
delete the "safe for kids" field
create a sub-project canis-utils to automate dog size and serving size entries
ensure that those entries are not mandatory