Thanks for all the info, very useful! A few follow up question then.
In future DHIS is looking at JSON as the main import/export API format?
So if I wanted to be able to import metadata from another system in the
long term, JSON is the way to go?
What is the best way to test the generated code is
We don't follow or express schema for dxf. Particularly the metadata has
been too dynamic. ( The link is very old and not maintained. )
Morten did introduce a schemas endpoint to the API (eg see
https://play.dhis2.org/demo/api/schemas/dataElement) which provides the
structure and types of the m
Maybe ADX would be relevant?
http://dhis2.github.io/dhis2-docs/2.21/en/developer/html/ch01s13.html
http://www.ihe.net/uploadedFiles/Documents/QRPH/IHE_QRPH_Suppl_ADX.pdf
Knut
On Fri, Feb 26, 2016 at 10:56 AM, Jason Pickering <
jason.p.picker...@gmail.com> wrote:
> Hi Samuel,
> We do not really
Hi Samuel,
We do not really maintain up-to-date schemas as such. The best resource
which is available for a given version is the /api/schemas end point, which
gives detailed information about each object.
In terms of the data format, you can have a look here (
https://github.com/dhis2/dhis2-docs/t
Hi,
I am looking at writing a DHIS2 import/export subsystem for a metadata
registry I help administer and am having trouble finding the DHIS2/DXF
schemas to make sure I am writing proper XML.
Can someone point me towards these?
Cheers,
Samuel Spencer
Aristotle Metadata Registry - Community Mana
5 matches
Mail list logo