...
Background
...
The existing OpenMRS Module Repository was created several years ago and has basic functionality to manage community-created add-on modules for OpenMRS. The goals of this project are to modernize the repository and provide additional functionality for users. (See Requirements section below.)
Team Members
- Burke Mamlin (project champion)
- Saptarshi Purkayastha
- Elliott Williams
- Ryan Yates
- Steven Githens
- Michael Downey
- You - feel free to join us!
Discuss the Modulus Project
Progress
The new Module Repository is currently under development led by Elliott Williams. Project source is at https://github.com/elliottwilliams/openmrs-contrib-modulus.
The prototype Module Repository was presented at the 2014-02-27 Regenstrief GHI Work-in-Progress meeting. View the slides from the talk.
Summer 2013 Project
The Module Repository Project was initially a goal during the summer of 2013, but was largely abandoned. Planning is archived here, and may still be useful in design of the current incarnation of the project.
...
| title | Summer 2013 Project Planning |
|---|
OpenMRS Module Repository is a repository of add-ons for the OpenMRS platform. This project page describes the deign and development plans for modulus, the module repository application itself. In 2007, Ben Wolfe created the module repository using similar technologies as OpenMRS itself (i.e., a Java web application with JSP pages for a front-end). In 2014, Elliott Williams created modulus as a replacement "Module Repository 2.0." Modulus comprises two projects:
- modulus – a RESTful Grails application that provides a REST API for managing, maintaining, searching, and reviewing modules. All of the "business" of the module repository is done here.
- modulus UI – a AngularJS-based web application that makes calls to the modulus API to provide developers & users with a module repository application
Purpose
The goal of this project is to advance the features and capabilities of the OpenMRS module repository application in support of the broader OpenMRS Community. Our vision is that any developer who wants to share a module can do so and any implementer in search of a module will be able to get their questions answered and easily download the module(s) they need.
Road Map
- Name
- Description
- Author/owner
- Support level
- Support information (info on how to get support for a given module)
- Links to source, documentation
- Version Compatibility -- OpenMRS (of course)
- Module ID
- Works with legacy OpenMRS installs (install from application)
- from Manage Modules page,
- check for updates
- install updated version
- search / add new module from repo
- from Manage Modules page,
...
...
- Access old/previous versions
...
2.0+
- OpenMRS ID compatibility
...
- Download statistics
- Screenshots
- RSS feed (
...
- new modules, updated modules, comments, reviews, etc.)
- Module
...
- icons
- Tagging
- Rating & Reviews (version-based)
- Deploy to repo as part of release process (e.g. maven)
- Module "collections" or "sets" recommended by people? (i.e. download modules from this specific list to achieve X or do Y)
- Version Compatibility
- OpenMRS (of course)
- dependent and/or "aware-of" modules
- consider first version of this as something configured by hand / entered in by module author
- would be nice to grok the pom and/or config.xml for this info
- Version compatibility with OpenMRS
- I'm on omrs 1.7, what modules can I use?
- I'm looking at MDS 1.2, can I see a table of compatible omrs versions?
- could refer to the fact that there are barriers in the current module repo
- OpenMRS ID + form submission ==> module in repo
Code
Source Code
- Modulus: https://github.com/openmrs/
...
- openmrs-contrib-modulus
- Modulus UI: https://
...
...
Resources
...
- talk.openmrs.org topic on the Module Repository
- MOD project in JIRA for issue management
See Also
- 2014-02-27 Regenstrief Global Health Informatics Work-in-Progress meeting slides from Elliott's talk
- 2014-03-27 Developers Forum introducing "Module Repository 2.0"