Hi Derek, yes, your previous answer already contained information what the database schema could be.
This schema is not related to my application at all. At least I think so. This would be generic and reusable. I think there is a better solution than starting plumbing this for myself. Maybe it is better if we would use one of the many navigation apps for our project. https://www.djangopackages.com/grids/g/navigation/ Maybe one of those already stores the relevant data in the database .... I will post here, if I found a solution. Regards, Thomas Güttler Am Donnerstag, 30. April 2015 18:29:30 UTC+2 schrieb Derek: > > Hi Thomas > > I do not I understand your question; I made a suggestion previously for > what fields you might need in this 'metadata' model, and you can add or > change as needed. I do not know what your project looks like, so I cannot > comment on what the rest of your database should contain. > > Derek > > On Thursday, 30 April 2015 13:26:25 UTC+2, guettli wrote: >> >> Hi Derek, >> >> yes, your idea looks good. >> >> Next question would be: How to lay out the database structure (models)? >> >> Regards, >> Thomas >> >> Am Dienstag, 28. April 2015 16:04:35 UTC+2 schrieb Derek: >>> >>> A quick "brain storm"... >>> >>> One idea could be to keep all the metadata for your views - their full >>> name; abbreviated name; aliases (alternate names); URL; keywords; and >>> categories etc. in a single table. You could then use this table to >>> generate *multiple* possible ways for a user to "find" the view they need. >>> >>> For example - you could present a list of categories (and >>> sub-categories, and sub-sub-categories) which could be presented in a >>> expandable list (jQuery-style). >>> >>> You could create a tag-cloud and allow a user to 'expand' a single tag >>> into related-views. >>> >>> You could allow a user to create their own tags for searching and >>> display (in a many-to-many table linked to user). >>> >>> You could allow a user to "favourite" some of the views and allow the >>> user to easily see (list/sort/search) those. >>> >>> And, of course, a simple search button could be created to allow an >>> 'incremental' display (auto-complete Google-style) of all possible matches >>> from all fields in your table... >>> >>> I am sure there are other ways you could think of to generate navigation >>> options, including fancy graphic ones! >>> >>> You would have to 'admin' this table of course, but the data in it could >>> be changed dynamically (e.g. adding more categories and aliases) without >>> affecting the logic of your app. >>> >>> [Hey - this could even make a cool app on its own!] >>> >>> Hope these ideas help.... my project is a just a boring menu-driven one. >>> >>> Derek >>> >>> >>> On Tuesday, 28 April 2015 11:27:47 UTC+2, guettli wrote: >>>> >>>> We have a complex intranet application. >>>> >>>> It has many view. >>>> >>>> The problem: How to find the view a user wants to use? >>>> >>>> A huge sitemap HTML does not help. >>>> >>>> Is there a way to search the matching view? >>>> >>>> Maybe even with auto complete? >>>> >>>> >>>> -- 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+unsubscr...@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/afb9bf35-4c10-4f39-aa4a-629177245102%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
