Skip to content

Don't use InvestigationContainer for DOI page

Axel Bocciarelli requested to merge split-doi-page into master

The InvestigationContainer is used by three pages:

  • DOIPage (/public/<doi-prefix>/<doi-suffix>)
  • DatasetsPage - i.e. the "Datasets" tab (/investigation/<id>/datasets)
  • EventsPage - i.e. the "Logbook" tab (/investigation/<id>/events)

This leads to a number of problems with the breadcrumbs and data fetching. For instance, the datasets are loaded when the user lands directly on an EventsPage, and the breadcrumbs don't appear when the user lands directly on a DatasetsPage. The code is also unnecessarily complex, since each page ends up doing its own thing.

My aim is therefore to remove InvestigationContainer completely, and to instead render the LogbookContainer and DatasetTable components directly from the three pages as required.

This MR makes a start on this by rendering DatasetTable directly from DOIPage and removing any DOI-related code from InvestigationContainer.

Merge request reports