Improve the Demo OpenMRS Data Set

[Gurpreet]

I had posted this as a question on https://answers.openmrs.org/questions/894/more-sample-data-in-demo-openmrs but was suggested to instead put it on a mailing list for discussion -- since that forum if for more precise non-discussion close ended questions. So here goes: 

The Demo Data (http://demo.openmrs.org) does not have sample data in certain entities like Visits, Programs, HTML Forms, Cohort reports, etc. This makes it little difficult to understand relationships between some entities, or their usage. By looking at sample data, it becomes easier for a newbie to understand what "kind" of data goes where.

Should I create a JIRA issue to update the Demo DB data set with some more entities? Alternatively, we can create a new DB Data set, by running an anonymization tool on some old production data set -- if possible.

Since the demo website is one of the "first" view of OpenMRS for folks, I would highly recommend that we populate even sample HTML Forms and Cohort reports data because these feature enhance the usability and value of OpenMRS multi-fold. I understand that this may be other "module" data, but if we want to "show off" OpenMRS to the world, then having a demo site which actually shows useful features would be good. 

What do others think. I will be quite glad to help in this effort. 

Regards

Gurpreet

[Darius Jazayeri]

Hi Gurpreet,

I definitely agree with those comments, and I'd definitely like to see us put together a (contrived) demo server that includes more module data, particularly around the different form entry technologies, and reports.

-Darius

Gurpreet

--
OpenMRS Developers: http://go.openmrs.org/dev
Post: d...@openmrs.org
Unsubscribe: dev+uns...@openmrs.org
Manage your OpenMRS subscriptions at https://id.openmrs.org/
 
 

[Gurpreet Luthra]

Thats cool Darius. I can start working on this item then. This is what I was thinking could be the approach: 

a) Look at each Admin Link, and see that none of them should have "empty data", and take feedback from the community on what would form a good data set for that "entity". 

b) I can create multiple issues, one for each entity, and take them one-by-one, and keep committing them so that they start showing up in demo.openmrs.org -- while I progress. 

Does that sound good? If yes, which element would you suggest should be focussed on first?  

--
Regards

Gurpreet

(M) +91-7798987124

Join the Beach & Volunteer Space to help OpenMRS, RapidFTR and Camfed. 

We are looking for Volunteers!

[Tobin Greensweig]

I'd really like to see more demo servers listed on this page: http://openmrs.org/demo/ that correspond to different "imaginary" clinics. Much as the MDR-TB demo is setup now, we could also have a primary care clinic with all the forms and modules preconfigured etc. In time these could be replicated into standalone downloads as well. Our implementation at a basic primary clinic is available for "copying."

Tobin

Tobin

[Darius Jazayeri]

I agree with Tobin that the ideal would be to have multiple demos of different contrived/imaginary installations, with relevant example forms and data. This would be awesome for testing new core and module versions via CI, for example. So we should make a long-term push to do this. (And I think it should tie into the CI/CD discussions that are ongoing.)

As far as a quick path to having a more useful demo server, Gurpreet, I agree that it makes sense to look at adding data piece-by-piece to the demo server. Though we should also consider starting from scratch on a first imaginary installation.

If we're just adding to the existing demo database, I'd definitely start by adding some HTML forms and XForms. These might need to be custom-built against the concept dictionary that is in the demo database. (Though possible real HTML Forms can be imported via Metadata Sharing.)

If we're starting from scratch, I'd say to start with the MVP/CIEL concept dictionary, and get some real forms that have been built against that dictionary and add them in.

Other high-priority stuff:

* Program enrollments, with states, and outcomes.

* A row-per-patient report

* An aggregate report

* Drug Orders (though these will be significantly refactored in 1.10)

-Darius

[Gurpreet Luthra]

What Tobin suggested, definitely sounds wonderful for OpenMRS. I agree that it can be considered under the CD/CI initiative for testing with various instances of OpenMRS. 

I will work on improving the Demo data set, based on your inputs Darius. Will send out a different email/issue for the first step towards this. --- "What sample HTML Forms would be suitable for Demo server". 

Thanks! I have bookmarked this email for follow-up points.