Closed HayleyMills closed 6 months ago
From JS- working in Main Archivist this morning on ns_04_w1 when I first loaded a construct tree I had constructs come up with a label of 'undefined' I reloaded the page and the tree populated with correctly labelled and filled in constructs.
Refreshing the alspac instrument doesn't do the same.
It's strange behaviour because these 'undefined' constraints are not in the database.
Cleared cache and it's okay now.
From CA In alspac https://closer-archivist-alspac.herokuapp.com/instruments/alspac_16_la24/build/constructs/
It doesn't look like they were constructs which were there before and have been edited (I've have checked past exports), it looks like they have just been created somehow?