You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of having a different view for year, keyword, etc, I think it would make more since to filter by the querystring. So, we could see all of the papers from eg 2014 that are tagged curcumin and antifungal with say /publications/?year=2014&keyword=curcumin&keyword=antifungal&plain=yes. Currently this particular query is not possible on the frontend. This kind of search would be well suited for a querystring instead of url parameters. Moving all of this logic into a single view would be a significant cleanup, only once would we have to state, for instance:
if 'plain' in request.GET:
return render_to_response('publications/publications.txt', {
'publications': publications
}, context_instance=RequestContext(request), content_type='text/plain; charset=UTF-8')
And, a few redundant templates could probably go away.
The text was updated successfully, but these errors were encountered:
Instead of having a different view for year, keyword, etc, I think it would make more since to filter by the querystring. So, we could see all of the papers from eg 2014 that are tagged curcumin and antifungal with say
/publications/?year=2014&keyword=curcumin&keyword=antifungal&plain=yes
. Currently this particular query is not possible on the frontend. This kind of search would be well suited for a querystring instead of url parameters. Moving all of this logic into a single view would be a significant cleanup, only once would we have to state, for instance:And, a few redundant templates could probably go away.
The text was updated successfully, but these errors were encountered: