Open dannymandel opened 5 days ago
Now that we switched over to linking to the iSamples Detail page instead of the original link, things blow up on SESAR test records (which unfortunately are the first records returned when you initially load the search results):
e.g. this detail page:
https://central.isample.xyz/isamples_central/thingpage/IGSN:IESER000J
Can be followed from this search results page:
https://central.isample.xyz/isamples_central/ui/#/?view=FSr13i8m34JHktXTeiHsRATdu19HMz98g20HLeYxusvOZfxqvmEtkcm3PhZsru09xe-ZzV5UDvWlYKkm90L9KCH4dUlugmREYKMGA4P4amdshRVTQnWZ1oNMKaGL9V5fTUr7Ep45Ouwc4arOCqtmx6FPFOenM2PXhqdINDJSQlC_ygdu_G40
We have some code in place that raises an exception during indexing if we hit these test records, we should look at catching that for the detail page.
Now that we switched over to linking to the iSamples Detail page instead of the original link, things blow up on SESAR test records (which unfortunately are the first records returned when you initially load the search results):
e.g. this detail page:
https://central.isample.xyz/isamples_central/thingpage/IGSN:IESER000J
Can be followed from this search results page:
https://central.isample.xyz/isamples_central/ui/#/?view=FSr13i8m34JHktXTeiHsRATdu19HMz98g20HLeYxusvOZfxqvmEtkcm3PhZsru09xe-ZzV5UDvWlYKkm90L9KCH4dUlugmREYKMGA4P4amdshRVTQnWZ1oNMKaGL9V5fTUr7Ep45Ouwc4arOCqtmx6FPFOenM2PXhqdINDJSQlC_ygdu_G40