Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Purpose

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 

Mailing List

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.

 Summer 2013 Project Planning

Module Repository Round One Requirements

  • Must support these fields on a module:
    • 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
    • Fuzzy/partial search by name, module id, etc (e.g. "sharing" --> MDS, "uifr" -> "UI Framework (module id: uiframework)")
  • Works with legacy OpenMRS installs (install from application)
    • from Manage Modules page,
      • check for updates
      • install updated version
      • search / add new module from repo
  • deliverable: what it will take for this to be done, or actually implementing it
    • probably an alpha release (as a mid-summer progress update) won't have to have this function working
    • end of summer: at least a detailed plan on how to make it work
  • Access old/previous versions


Module Repository Next Steps

  • OpenMRS ID compatibility is a plus
  • Download statistics
  • Screenshots
  • RSS feed (of what content?)
  • Module logos
  • 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?

Questions (what is meant by):

  • Being able to see our modules (anyone should be able to submit modules)
    • could refer to the fact that there are barriers in the current module repo
    • OpenMRS ID + form submission ==> module in repo

Code

Resources

  • No labels