Ticket #885 (closed issue: wontfix)

Opened 13 years ago

Last modified 13 years ago

[M] How to handle missing browse records

Reported by: selatham Owned by: lawrence
Priority: critical Milestone: Replace Metadata Gateway
Component: discovery Version:
Keywords: Cc: rkl

Description

For instance BODC supplies a mixture of discovery records some of which do not have corresponding Browse records e.g. the EDMED derived information. BODC are flagged as 'NDG' DataProviders? so their identifiers look like NDG ones. Therefore browse attempts to find a Browse record and a 404 error message appears. 

Not Found

The requested URL /view/grid.bodc.nerc.ac.uk__NDG-B1__EDMED1048003 was not found on this server.

Potentially, Browse records can be missing for any 'NDG' DP for a number of reasons. How can we handle this gracefully?

Change History

comment:1 Changed 13 years ago by lawrence

  • Cc rkl added
  • Status changed from new to closed
  • Resolution set to wontfix

This can only be handled by either doing service binding properly (not now), or by NDG providers ensuring that they at least have a stub record for all datasets that they put up for discovery, or by, redirecting to discovery records (could be done, but would confuse the user).

I'm closing the ticket, it's not fixable on a sensible timescale other than by the NDG data providers.

Note: See TracTickets for help on using tickets.