Someone wiped this OpenMRS installation at some point before June 21. I don’t have any insight into why or who. (Maybe it was tied to this, or tied to getting to Platform 2.0?) In any case this is bad, because this was supposed to be our server of record for metadata that we include in the reference application.
Poking around, the only relevant database dump I see is in Rafal’s home directory
openmrs_db_20160412.sql which we might consider restoring. (Ellen has a dump from October, but I’m guessing these packages were deleted before that.)
@raff, what do you think is the best way to reconstruct the MDS packages we had on this machine? It seems like we are using 7 packages, as defined here, and I think they’re probably small, since we’re not including concepts.
One option (tedious, but doable) is (1) import all MDS packages that are in the referencemetadata module, to get the metadata onto this server; (2) look at the header.xml in each of the zip files, and manually create new packages having the relevant items, (3) manually edit the records created in the metadatasharing_exported_packages table so they have the right UUIDs and versions.
Another idea is to stop using metadata sharing for all these things, and instead use the metadatadeploy module. I wouldn’t have prioritized making this change, but if we already have to do tedious work to recover, this would be a better use of time.
(@raff, @dkayiwa, @wyclif, @ball, someone experienced like you is going to have to lead this, it’s not something we can expect @taremwatadeo to do in his first time as release manager! Who can commit to doing this?)
Aside: I have changed the admin user’s password to something none of us will remember, to force people to use their own accounts to do things on this server. We want the metadata that people created on this server to be traceable…