As of recently we have a VM set up to be our "Official Metadata" server. It lives at https://69.91.227.32/openmrs. (At some point this should move to Kenya, and get a real hostname.)
We will create the final "official" versions of all our metadata there. I.e. things like Visit Types, and Forms. The key point is that we'll generate all of our metadata sharing packages from this server, and only this server.
That means you shouldn't do anything on this server unless the item you create or edit is ready to deploy to production. If you need a login (Steven, George, Patrick, Jan) I believe that Jim or I can create one for you.
I've just created the first piece of info. Does it look right?
Showing posts with label metadatasharing. Show all posts
Showing posts with label metadatasharing. Show all posts
Monday, June 18, 2012
Official Metadata Server
Labels:
metadatasharing,
screenshots
Location:
Seattle, WA, USA
Sunday, May 20, 2012
Metadata Sharing with OpenMRS 1.9
I included some use of the Metadata Sharing module in my end-to-end demonstration last week, but it was partly cheating because I only included Encounter Types and Visit Types in the package, and didn't include Concepts, which haven't yet been shown to work with OpenMRS 1.9.
Hey, one thing at a time.
So I just made a MDS package out of the "Vitals" HTML Form that I used for the screenshots in my last blog post. This includes concepts in it for testing purposes. (Though in practice we'll be writing our forms against MVP/CIEL dictionary codes, so our forms won't actually need to include concepts when we push them to production. We'll be pushing out the updated MVP/CIEL dictionary to our production installations some other way.)
Trying to import that package I ran into two bugs (but only two!):
Hey, one thing at a time.
So I just made a MDS package out of the "Vitals" HTML Form that I used for the screenshots in my last blog post. This includes concepts in it for testing purposes. (Though in practice we'll be writing our forms against MVP/CIEL dictionary codes, so our forms won't actually need to include concepts when we push them to production. We'll be pushing out the updated MVP/CIEL dictionary to our production installations some other way.)
Trying to import that package I ran into two bugs (but only two!):
- META-226 - getDeproxiedClass does not work right in OpenMRS 1.9
- META-227 - Starting in OpenMRS 1.9 you are not allowed to modify ConceptDatatypes, so we need to stop exporting/importing them
After fixing the first bug, and putting in a quick-hack workaround for the second, I was able to successfully import the MDS package.
I'm glad it was that straightforward, and we're closer than I thought to being able to use MDS with OpenMRS 1.9 for our use case. (To be fair, the database I exported from didn't have any concept mappings on the exported concepts, and I'm pretty sure those would break with a third, more significant, bug. But also to be fair, as long as we can hand-wave and say that we'll be able to update the MVP/CIEL dictionary "some other way", we won't need to deal with this.)
Labels:
dev-notes,
metadatasharing,
progress
Location:
Seattle, WA
Wednesday, May 16, 2012
Proposing an OpenMRS Sprint
A few days ago I mentioned a project I wish I could work on. Today I came across another one that I'd love to work on, and is important to the project in the long-run, but not before our end-of-June deliverable.
In this case, it would be great if we could have our main servers automatically get updated versions of the MVP/CIEL dictionary. (We can do this manually now, but it requires messing around with sql dumps in an annoying way.)
So, I'm proposing it as an OpenMRS sprint. Hopefully others will be able to collaborate when the time comes!
In this case, it would be great if we could have our main servers automatically get updated versions of the MVP/CIEL dictionary. (We can do this manually now, but it requires messing around with sql dumps in an annoying way.)
So, I'm proposing it as an OpenMRS sprint. Hopefully others will be able to collaborate when the time comes!
Monday, May 14, 2012
A day of staring at the debugger...
Today I sat down to see how well the Metadata Sharing module works with OpenMRS 1.9. We really wan to use OpenMRS 1.9 (to take advantage of the new data model for Visits) and we also want to use MDS (to help us package up new versions of our application content), but they don't fully work together yet.
In the long run we want to use MDS to publish versioned packages containing the metadata and content that makes our application work. I figure we'll have a package for core stuff like Encounter Types, Visit Types, etc, one package for the master list of Locations, and another that contains forms, concepts, and reports. Offhand I think it will be easier to manage changes that way, rather than with a single "everything" package, but time will tell on that front.
Anyway, I was able to get my first example of loading a metadata package when a module starts up (using a placeholder package with a few Encounter Types and Visit Types). You can see the code here. At some point someone in Kenya with domain knowledge is going to have to build the proper first version.
Tomorrow's goals:
- rename the Distribution module, since Burke didn't like that name) and release it to the OpenMRS module repository.
- end-to-end test of everything we've built so far:
- start with an empty standalone installation
- installing our zip-of-omods (resulting in a running application)
- installing version 2 of our zip-of-omods (resulting in an updated application)
Below the fold are a couple of dev issues that took me time to figure out, and I want to document for posterity...
Labels:
debugging,
dev-notes,
metadatasharing
Location:
Seattle, WA
Subscribe to:
Posts (Atom)
