The short story is all of these should be doable in the admin, and most will also be quite simple.
The long story is below. Note, however, that some of my suggestions are based on the old admin rather than newforms-admin, but from what I have seen of newforms-admin, it should be fairly similar in concept. My original (and current production) site was built by modifying the admin and I faced and overcame issues like the ones you suggested without too much trouble. If you can trust the users, it is scaffolding that you can often easily build upon. > 1) Add a duplicate this record button to start a new 'Add [model]' > page but pre filled in with data from an existing record. Yes. To provide the "Add From This" link, one option can be to modify the submit_line.html template, another is to add a link to a change list from the admin index page and use a change list to select the source. For pre-filling data, this was rather painful with the 0.91 admin pages - I called a subclassed django "change" method when I was working on this, and overrode the admin url - but you might be able to avoid some problems with newforms-admin, if you are lucky. > 2) Add some light reporting views. I imagine these would be just like > a public view but limited and linked to from the admin somehow -- so > I'd need admin authentication and a link in the admin? Yes. Very simple, just create your own admin index page & insert it before your admin inclusion, add the reporting views, and make sure your views are decorated with staff_member_required. > 3) If I can do #2, that opens up a lot of things for the other items on my > list. Great! > 4) When adding a new record to a model, hook in an AJAX call to check > if the item already exists in the table and indicate if it does. > (There's a single column that is the key for this.) If you really need to (the admin page will check for violations of some constraints (like unique, primary_key, etc)). You would use the "js" option to add the ajax hook. > 5) And advanced search for their main model. This is posible via #2 > but it would be interesting if this could be abstracted a bit and be > re-used. I'm kind of thinking of a way to specify which fields should > be included in the advanced search and automatically generate a form > and process the form submit to search those fields? Not looking at > full-text search at all, but simple things like `title` contains > 'django', `bestseller` is true, `binding` is 'Hard Cover', things like > that. Yes using both search_fields and list_filter, No as a single form-like search interface. You can use search fields on any number of text & char fields, and boolean, foreign key and date fields for the list filter. It is pretty slick as is, so you should check it out and see if it will solve the user's needs before you write anything additional. Your example above would use: search_fields = ['title'] list_filter = ['bestseller', 'binding'] The user would select "Bestseller: Yes" and "Binding: Hard Cover" on the right side of the screen, and type the title name in the search field. One caveat: the above example assumes 'binding' is a Foreign Key. If it is a choice field, it won't work. > 6) From the admin create a 3-step wizard to build, generate, and send > a newsletter. Probably another item that depends on #2. Yes, again very simple. You just need to link to it in the admin index page. My suggestion with "wizard" forms is that you tie the "next" page url directly into the urls.py page (i.e. don't have hrefs scattered throughout your views), and keep everything under one common url (e.g. /makenl/build/, /makenl/gen/, /makenl/send/) HTH, -rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
