The philosophy of the admin app is that it is a simple CRUD interface for trusted staff members to manage data. If you need data entry for non staff members (i.e. people you do not trust with the admin) you should create public facing forms and setup some permissions for the users to be able to use them.
As for you second question it sounds like you need two models, one for experiment_x and one for sub_experiment_x with a foreignkey to experiment_x. You could probably use inline formsets to generate the extra 8 forms. I'm not sure how you would limit the inline formsets though to exactly 8. Hope this helps. On Nov 24, 5:33 am, Andreas Kuntzagk <andreas.kuntz...@mdc-berlin.de> wrote: > Hi, > > I'm quite new to django and very new to this list. > I'm in the process of writing a small webapp for our lab. > Working with the tutorial I already put together a small model and some > admin pages. > But now I came to some stumbling blocks: > > First is a broader question: I'm wondering what belongs to an admin page > and what should be in a "normal" form. I want to keep track on some > experiments so some (authenticated) users should create experiment > entries and add comments etc. And then I have "machines" where these > experiments run. These don't change so often. So does setting these > things belong into the admin area? > > Second experiments of type x always consist of 8 parallel > subexperiments. How do I model this? These subexperiments should > (automagically) be named subexp1 to subexp8. > > Regards, Andreas -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
