|Uuid||Void/Retire||Identifier type||Name||Description||Prefix||Suffix||First identifier base||Min length||Max length||Base character set||_version:1||_order:6000|
|90563743-a6c8-4c23-8244-f50361f2a997||df255fa5-eb77-414d-89e5-5f068ba63a54||Location Prefixed Identifier Source||Location Prefixed Identifier Source||provider:idgen.locationBasedPrefixProvider||100000||6||0123456789ACDEFGHJKLMNPRTUVWXY|
While working on one of our Java projects on macOS it was required to do a search and replace in all Java files containing a string sequence. In our case it was required to change every JavaDoc "
@since 2.3.0" into "
@since 2.1.5, 2.3.0".
sed is the tool for this, and since BSD's implementation differs from GNU sed, we opted to stick to GNU sed which is available on Homebrew:
brew install gnu-sed
Then the magic combining
find src/ -name '*.java' | xargs gsed -i -e "s/@since 2.3.0/@since 2.1.5, 2.3.0/g"
Strangely we could do for so long without a dedicated OpenMRS Initializer domain for locations. Until now we were simply bringing in locations metadata through OpenMRS MDS packages. MDS packages are always a convenient fallback mechanism when the desired OpenMRS Initializer domain is not (yet) available.
It was on our to do list for some time to finally address the case of locations. It is now done, please check the README about it here.
Let us look at a sample use on a Bahmni distribution of one of our clients that supports a small community health clinic in Haiti. Starting from an existing default Bahmni setup we want to end up with just two locations:
'Clinic' is the login location for providers at the clinic itself, whereas 'Community' is an ad-hoc location for providers performing community surveys while offline using Bahmni Connect. We had to deal with the
One of our Bahmni instances was not able to trigger any Bahmni Reports because - somehow - a report that could never be completed was stuck as 'Processing'. That piece of information could be seen in the 'Reports Queue' under 'My Reports':
It was clear that this report was not really processing and that the information was lingering, yet blocking the scheduling of any new report with an error 500:
The server encountered an internal error that prevented it from fulfilling this request.
Restarting Bahmni Reports didn't do anything to it: