Re: Django for in-house data

On 9/12/2013 8:14am, Lachlan Musicman wrote:
> To be fair, I think the best measure is the technical literacy of your
> users. The Admin interface is powerful, but they could also
> accidentally screw everything up.

I agree that the Admin is not for general use. What I was thinking about
was the speed of getting it up and getting feedback for building what
might be required/desired. In other words, an interim prototype.

Your point about technical literacy bears thinking about. Wouldn't you
say all users can screw things up whether they are technically literate
or not?

Maybe group permissions in the admin can deliver read-only access to the
data? Perhaps a small number of technically literate users can be given
r/w permission for a restricted number of tables?

Doing that might or might not fit the scenario but it is worth considering.

Mike

>
> Views (can) remove that opportunity
>
> L.
>
> On 9 December 2013 08:06, Mike Dewhirst <miked@dewhirst.com.au> wrote:
>> On 8/12/2013 9:15pm, giuliano.bertoletti@gmail.com wrote:
>>>
>>> Hello,
>>> I'm using Django to have people in my company access our database. Since
>>> the application is not meant for public use, I was wondering how to best
>>> struture it.
>>> The admin framework seems to be well suited for manipulating tables via
>>> web, while views (in my understanding) seem better for
>>> presenting contents with limited database manipulation.
>>> Since my app is not meant for public use, I'm wondering if it's worth
>>> the effort to build views to mimic most of the admin features (are there
>>> shortcuts?)
>>> On the other hand, I'm not very happy to give everyone in my company
>>> admin access simply to use the already built web interface.
>>> Any suggestions?
>>
>>
>> I would go with the Admin interface and a sample of the database as a
>> prototype for user feedback. It will be much faster than building a fully
>> feathered application.
>>
>> You can decide later if you want to stop there and rely on the admin or
>> press on and build your own user interface.
>>
>> Mike
>>
>>
>>> Thanks.
>>> Giuliano.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Django users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to django-users+unsubscribe@googlegroups.com.
>>> To post to this group, send email to django-users@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/django-users.
>>> To view this discussion on the web visit
>>>
>>> https://groups.google.com/d/msgid/django-users/1ab0c4ce-7e52-4764-bb7b-d653f0bef474%40googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-users+unsubscribe@googlegroups.com.
>> To post to this group, send email to django-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/django-users.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/52A4DF4C.1070209%40dewhirst.com.au.
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/52A57CB5.6070300%40dewhirst.com.au.
For more options, visit https://groups.google.com/groups/opt_out.