Do promos have to be associated with a project?

[GoogleCodeExporter]

What if a story that is being promoted appears, let's say, on a national
publication.  

Should we enter a project into the database that had a title of undefined?
 Or, conversely, in /promos/model.py is it possible to make this field not
a required field:

project = models.ManyToManyField(Project)

I posted the question on the django IRC and recieved the suggestions:

* check out the modelforms docs discuss overriding fields

* and it's possible to modify fields in the form's constructor

Original issue reported on code.google.com by jgty...@gmail.com on 26 Apr 2009 at 3:53

[GoogleCodeExporter]

Additionally, in a slightly related topic, if when submitting a promo, the 
precise
topic_path that you want to use is not yet entered in the selection list, how 
is this
best handled?  

Is it possible to have an additional text field (along with the selection list) 
to
enter an additional topic_path if the one they want to add is not listed.

Original comment by jgty...@gmail.com on 26 Apr 2009 at 4:02

• Added labels: Milestone-Week4

[GoogleCodeExporter]

On the projects model lets make project required = False and also allow for 
adding topic paths.  Also  I think 
editors should handle projects, since it is a higher level thing.  If you are 
submitting a promo and it's part of a 
project then we can have an project notes field where you can add that 
information and then the editor will 
process the promo submission and possibly assign the promo to a project.

We should also note that projects tend to be sub-projects.  So there is a 
tendency to have an over-arching 
project composed of multiple sub-projects, each produced by three or four 
students.  This can make projects 
a little more complicated than we like it.  My suggestion to keep projects for 
the over-arching one, not the 
sub-projects.

Original comment by mand...@gmail.com on 26 Apr 2009 at 9:33

[GoogleCodeExporter]

I agree about your description of sub-projects.

Would it be helpful to deal with sub-projects in the same way we would topics? 
Stories belonging to a specific sub-project could have a unique topic_path and 
use
its own template for display.

Thanks for the clarification on the required field.  

Original comment by jgty...@gmail.com on 26 Apr 2009 at 9:44

• Added labels: Projects

[GoogleCodeExporter]

We do not want to expand projects at this point.  We want to set limits to our 
features at this point and see how 
it goes over.  Think of managing projects like affiliates, mainly an editoral 
task.

Original comment by mand...@gmail.com on 26 Apr 2009 at 9:47

[GoogleCodeExporter]

see r327

Original comment by jgty...@gmail.com on 27 Apr 2009 at 12:17

• Changed state: Fixed

[GoogleCodeExporter]

The patch looks great. thanks!

Original comment by mand...@gmail.com on 27 Apr 2009 at 5:34

[GoogleCodeExporter]

I'm opening this ticket back up because I think projects is important and this 
thread probably is not finished 
since we don't have projects in the interface yet. 

Original comment by mand...@gmail.com on 3 May 2009 at 10:46

• Changed state: Started