As discussed in #533, projects are not force to belong to a category (neither in their model definition nor in the DB schema).
However, this is something we are giving for granted in some other places, as every time we create a new project (either web interface or API) we are assigning a default category to the project, as not doing so resulted in the project not being displayed throughout PyBossa.
Later modifications of the project could result in a project with no category, which is what we have been trying to avoid by fixing both the API project creation as the web based one, so I believe this constraint should be added.
As discussed in #533, projects are not force to belong to a category (neither in their model definition nor in the DB schema). However, this is something we are giving for granted in some other places, as every time we create a new project (either web interface or API) we are assigning a default category to the project, as not doing so resulted in the project not being displayed throughout PyBossa. Later modifications of the project could result in a project with no category, which is what we have been trying to avoid by fixing both the API project creation as the web based one, so I believe this constraint should be added.