| Table of Contents | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Assigned to: Unlicensed userSriHarsha Pamu
Mentor: Unlicensed userraff
| Info |
|---|
Metadata Sharing Server has been renamed to Metadata Repository. |
Background
The Metadata Sharing Module lets an administrator export a set of metadata (concepts, forms, locations, etc.) and publish it to a URL so that other OpenMRS implementations can import it and subsribe to future updates. In this model each OpenMRS server acts like a subscription server for clients. Clients download and import metadata from the given URL on the subscription server.
...
- Implement the Metadata Sharing Server.
- Allow for uploading metadata packages from a file and the Metadata Sharing Module.
- List and search for metadata packages (based on indexed package headers).
- Gather usage statistics and suggest the most popular packages first.
- Authenticate OpenMRS installations while uploading packages and verify package publishing server information.
- Modify the Metadata Sharing Module.
- Allow for uploading metadata packages to the Metadata Sharing Server.
- Add information about a publishing server (where it comes from) to a package.
- Allow to import a selected version of a metadata package.
- Search for metadata packages on the Metadata Sharing Server.
Contacts
Do not hesitate to contact us, if you are interested in the project.
...
- Technologies
It should be possible to easily deploy the MDS server application on both Linux or Windows. The JVM is a preferred deployment environment, but it is not strictly required. Technologies used must be free and preferably open-source. The goal is to be able to deploy the MDS Server under mds.openmrs.org or any other server. - Authentication
Each OpenMRS server has a unique implementation ID that should be used together with a password for the authentication process. We will only authenticate servers that want to upload metadata to the central repository. Importing should be possible for everyone without additional authentication. The authentication is thought as a way to confirm that the package comes from the given server so that someone who imports it can be sure that it is from a trusted source. We might allow for uploading a package without authentication, but it should be marked as not trusted. The authentication of subscribers is not planned in the first phase. - Versioning
It should be possible to upload new versions of a package. A new version can be published only by someone who originally uploaded a package. It should be possible to import any version of the given package. Publishers should be able to unpublish any version of a package that was once published.
...
Joe: Allow private packages and select a password for those?
Rafal: Not in the first pass. We'd like our users to be open(-source).