> The job description is to have a dashboard full of information, 


It might be an OK solution to use the admin changelist (list feature of the 
admin) and render graphics using admin actions with an intermediate 
page<https://docs.djangoproject.com/en/dev/ref/contrib/admin/actions/#actions-that-provide-intermediate-pages>and
 using 
filter and search <https://docs.djangoproject.com/en/dev/ref/contrib/admin/>. 
Given you know how to override templates and find you way through the admin 
classes and AdminModel configuration. 
 

> this information could be coming from external sites or our own sensors.
>

If you don't of Django models for your data, then you can make it work 
using django-roa <https://github.com/liberation/django-sneak> (I don't know 
if works with 1.4.1) or 
django-sneak<https://github.com/liberation/django-sneak>(should work with 
1.4.1, contact me if you want help if you go this route) 
and follow the above technic.

Django-reporting <http://Django-Reporting%20might%20also%20be%20usefull>might 
also be useful, but I don't know actually if it is the solution to 
your problem.

Anyway, if you don't feel like to integrate/use this applications which 
might be a bit difficult for a beginner. You can start from scratch CBV 
route <https://docs.djangoproject.com/en/dev/topics/class-based-views/> or 
function views and build a customisable dashboard yourself, I don't have 
all I need to be more precise.

I don't think the admin is the solution, it's not flexible enough but still 
a good solution for a POC application.
 

> This is what strucked me about the admin_tools interface this ability to 
> add, remove and change the layout with relative ease.
>
Yes but it's specific to admin tools I think, someone more competent might 
be of better advice, but I think that admin tools is not the application 
you are looking for. Or ask the maintenair directly through github they 
might be able to answer you :)

I suspect that users will have to be registered so it won't be open to the 
> public to just "sign up" but management have changed their mind before on 
> these type of issues.
>
I don't think this is your primary issue right now, getting the dashboard, 
graphs and data navigation up and running should be. If you go the admin 
way and the management decide that the data should be public, you can 
provide a Django user with default password, lock the change password 
feature and make the credentials available publicly.

If you feel it would be better to go for a cms
>
I say it might be, try to contact their respective maintainer or mailling 
lists.
 

> Or just use the current admin interface as is that would be great as I 
> have very little time allocated to this project being a typical government 
> organisation. 
>
Like everybody ;)
 

> That said I have tasked myself to learn the ways of Django as such I'm 
> feeling a bit overwhelmed on the practices, code structure and the best way 
> forward.
>
You problem doesn't seem to be in the Django CMS-like vein of problems, yet 
it's it's doable, but can't give a precise answer without more information.

Contact me directly if you want.

Good luck


Amirouche

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/FIGB0RvmQ1sJ.
To post to this group, send email to [email protected].
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.

Reply via email to