Chris's Wiki :: blog/python/DjangoAdminNote Commentshttps://utcc.utoronto.ca/~cks/space/blog/python/DjangoAdminNote?atomcommentsDWiki2011-01-20T16:50:34ZRecent comments in Chris's Wiki :: blog/python/DjangoAdminNote.By Chris Siebenmann on /blog/python/DjangoAdminNotetag:CSpace:blog/python/DjangoAdminNote:66b0a13b2048260efd5d520c2b269c85d5e1140dChris Siebenmann<div class="wikitext"><p>Whoops, I should have footnoted the 'core systems staff' bit. Locally
we divide sysadmins into <a href="https://utcc.utoronto.ca/~cks/space/blog/sysadmin/CSDeptSupportModel">Points of Contact</a> and 'core' sysadmins who support the
common infrastructure. Since this is account creation for our departmental
computing infrastructure, only core sysadmins will be doing things like
adding new sponsors or available home directories.</p>
<p>In reading a bit about the Django admin interface, the big sticking point
is giving (Django) users access to only some records from a schema table.
The current Django 1.2 permissions stuff explicitly documents that it can't
do fine-grained access control like that, and we need it; users that are
sponsors can only approve account requests that list them as sponsors.</p>
<p>(The other sticking point is that various different people should be able
to edit different fields in an account request.)</p>
</div>2011-01-20T16:50:34ZFrom 91.109.240.108 on /blog/python/DjangoAdminNotetag:CSpace:blog/python/DjangoAdminNote:8a28610cba184511b2b45b1e5a5ecaff24db0ca5From 91.109.240.108<div class="wikitext"><p>Core systems staff?</p>
<p>My clients use the Django Admin on a daily basis. A smattering of jQuery and some tweaked templates can do wonders.</p>
<p>The only hardcore work I've needed done on the Django admin is to support fields that appear or disappear depending on another drop-down choice.</p>
</div>2011-01-20T14:50:51Z