id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
3	Model implementation	olivier	olivier	"As shown on GlobalArchitecture, the data will be available through a Model layer. The basic idea is:
 * to modelize the main data structures: Collection, !MediaItem and Part 
 * to completely encapsulate the SQL queries into this model

The choice we made of using the DjangoFramework may naturally lead us to use Django's Object Relational Mapper. However, we need dynamic properties: an easy way for the administrator to add/remove fields to each of our data structures.

In this regard :
 * we can use helper models to hold these dynamic properties
 * or/and tweak Django models to (sort of) transparently support these properties
 * or we can completely bypass the Django model layer and create our own model implementation from scratch, but still use the rest of Django's features, which appears to be [http://www.djangoproject.com/documentation/faq/#do-i-have-to-use-your-model-database-layer ""Django compliant""]"	task	closed	major	Version 0.3	Miscellaneous		fixed