Main production Archivist db is not reflecting the front end or exported XML

CLOSER-Cohorts / archivist

Archivist is designed to be an easy to use editor that allows documention of questionnaires and data in DDI-Lifecycle

MIT License

17 stars 8 forks source link

Main production Archivist db is not reflecting the front end or exported XML #863

Open HayleyMills opened 3 months ago

HayleyMills commented 3 months ago

When updating the 'top sequences' which didn't match the prefix, I noticed that sequences which are being updated are not changing in the DB? This is on the main production and I cannot replicate on the staging. Can you check that you are seeing the same thing?

This is also the case for the prefixes and slug. On the main Archivist, I updated the prefix wchads_12_ph11mi12mx to wchads_12_ph11mi12mx_new and sequences: wchads_12_ph11mi12mx_new and Part 1_new, to test, and the db remains unchanged.

The exporter is exporting the updates correctly.

simonreed commented 2 months ago

@HayleyMills I thought I understood the problem, but now I'm not so sure. If with wchads_12_ph11mi12mx we've updated the prefix to wchads_12_ph11mi12mx and the prefix for that is now wchads_12_ph11mi12mx_new in the database then what specifically in the database isn't being updated?

As you say the front end and exported XML are showing the correct new prefix but from the image above so does the DB, what am I missing?

HayleyMills commented 2 months ago

Thanks Simon, I wasn't seeing the db matching. Unfortunately, I can't currently check whether I'm still seeing this or whether it is now correct, until I have access to the the software I use.