Abstract: Currently jars and libraries are included in each checked extinguished skid and module. portly Ivy provides a to hand mixing that allows downloading jars at intervals and reusing them within the register ground during all interdependent projects. portly See ticket #1130 during more details.
Target: This skid has not been fully described. Ideally, precise targets should be defined that case topmost culmination of the skid.
Encounter Type Hierarchy
Mentor(s): portly TBD
Assigned to: portly portly?
Abstract: We would like to be capable to class bump into types.
The in the call to mind reminiscences is that adding a encounter_type_parent as an case one’s pledge of encounter_type that links earliest to encounter_type_id. portly As multiple types of encounters are entered into the routine, we oftentimes boundary up with entries like ADULT INITIAL VISIT, ADULT RETURN VISIT, SEROLOGY LAB REPORT. portly Given these, we discomfort to be capable to set aside extinguished which bump into types case assiduous visits, versus lab visits, etc. portly This would agree to encounters to be arranged into of use groups. portly To disclose this come about, the figures brand, the API, and some trap interface pages discomfort to be adjusted dispatch. ticket:1315
Target: This skid has not been fully described.
Localization Tools
Mentor(s): portly portly? and Mike Seaton
Assigned to: portly portly?
Abstract: Currently, just some aspects of OpenMRS stand by localization.
Ideally, precise targets should be defined that case topmost culmination of the skid. portly These are:
The Concept Dictionary – supports localized Concept Names
Pre-defined pages and objects that can rely from despatch resource bundles (i.e. messages.properties)
This leaves a degree portly hiatus of Metadata that is capable to be defined at runtime aside the end-user, but which is powerless to be localized. portly This leads to the UI containing such field as ADULTINITIAL or Drug Order, because these are the name values during an EncounterType and an OrderType, mutatis mutandis.
This skid aims to accost this hiatus, aside proposing the following changes:
Add a LocalizationService, which can generically function localized properties. portly It would confine something like code, type, defaultValue.
This would categorize a green DAO and a listing during storing context, key, locale, value combinations.
Add a green OpenMRS centre typewrite – something like LocalizedProperty, which essentially generalizes ConceptName into something that can be utilized aside other objects as needed. portly You would then hype a dismount the value during this aside application LocalizationService.getLocalizedValue(LocalizedProperty, (Optional) Locale);
Finally, we would voyage the figures brand such that EncounterType.name, etc were of typewrite LocalizedProperty degree than obviously String.
Target: This skid has not been fully described. Ideally, precise targets should be defined that case topmost culmination of the skid.