@Snehal1894 could we look into the possibility of manually curating the database that is underlying cLIMS ?
e.g.
stop cLIMS, get a fresh dump (maybe manually)
use that dump to create a local copy of the database
modify the database - e.g. add missing md5sum in bulk, populate etag, etc - without manually enetring that through cLIMS interface
generate a dump of the modified database
upload it to production cLIMS and restart it - will Django swallow it ? what could go wrong (timestamps, modification, migration - any of that mysterious stuff )?
@Snehal1894 could we look into the possibility of manually curating the database that is underlying cLIMS ? e.g.
md5sum
in bulk, populateetag
, etc - without manually enetring that through cLIMS interface