Legacy view usage

Prior to migration tate.org.uk comprised a Drupal back-end with a Django front-end.

The original legacy Django 'views' are obsolete and have been removed.

However, there remains a handful of views in frontend/pages/views.py that are still in use, as detailed below:

ResearchText

Some collection pages feature content, e.g The 'Artist biography' tab text, that is derived from a separate, research-related resource. The details of this content are provided by the legacy API data underpinning collection pages, under 'resources'.

However, the actual resource text is only 'pointed to' by the API data. It still needs fetching. This is achieved by means of a frontend request passing the relevant details to the ResearchText view, which in response, provides the appropriate HTML fragment of research text.

LegacyRedirect

This view redirects legacy URLs to their Wagtail equivalent.

ShopCards

Some collection pages feature a shop products strip containing product details ultimately derived from the Salesforce API.

The mechanisms behind this are a little convoluted but essentially, the frontend makes a request to the backend to get the strip HTML shown on the page. This request hits the ShopCards view.

EventPlan

This view provides the csv file-derived lists of events, featured in the Visee site, for example, at https://visee.tate.org.uk/tate-modern/event-plan

Note: the above views all extend the base class TateBaseView - as does TessituraSubscription in frontend/pages/views_subscription.py