Please find below a list of frequently asked questions.
Yes, the .Stat Suite architecture follows the CSPA principles, enabling a complete decoupling between the different components and integration through standard interfaces (SDMX APIs) to existing applications and processes an organisation has in place.
For example, the .Stat Data Explorer can be connected to an existing SDMX 2.1 endpoint. This simplified mono-tenant install provides organisations a way to easily visualise data from different SDMX sources.
Yes, there is a number of documentation pages available on Gitlab covering the various aspects of the product architecture, technologies, installation, customisation, as well as individual readme files under each service repository.
Yes, the Community defines a product roadmap every year aligned to its 5-year Strategic Directions.
The .Stat Suite roadmap has been envisaged through to 2021 and is available here.
SDMX, which stands for Statistical Data and Metadata eXchange is an international initiative that aims at standardising and modernising (“industrialising”) the mechanisms and processes for the exchange of statistical data and metadata among international organisations and their member countries.
SDMX is sponsored by seven international organisations including the Bank for International Settlements (BIS), the European Central Bank (ECB), Eurostat (Statistical Office of the European Union), the International Monetary Fund (IMF), the Organisation for Economic Cooperation and Development (OECD), the United Nations Statistical Division (UNSD), and the World Bank.
The .Stat Suite is a native SDMX solution, supporting a complete end to end flow. It can consume, manage, and export SDMX 2.1 in SDMX-JSON, SDMX-ML, and SDMX-CSV formats.
The source code is available on Gitlab with each service having its own repository and associated documentation. Please check out the developers section for more details.
Yes, the .Stat Suite is made available under the terms of the MIT licence. MIT is a permissive free software license, which has very limited restriction on reuse.
However, please note that limited technical support is available for non-Community members.
The community is fully self-financing through its members’ regular contributions, which ensures its sustainability. All members contribute financially with an initial contribution to feed the product roadmap, and on an ongoing basis to sustain support and community coordination activities.
No, the .Stat Suite is made available under the terms of the MIT licence (a permissive free software license).
Every year the community organises its annual workshop with an invitation to the first 2 days extended to interested groups and organisations who may be considering using the .Stat Suite and would like to know more about the community and learn from their experiences. If you would like be added to the mailing list then then please fill out the contact form.
Technical documentation is available on our open source project pages in Gitlab to assist in the installation and set-up of the .Stat Suite. Members of the Community have access to the core project maintainers and technical support from the community as a whole. For non-Community members without the technical capacity to install and maintain their instance of the .Stat Suite, a .Stat as a Service option is available.
A demo site of the .Stat Data Explorer is available online where you can test the latest features for yourself.
In addition, a .Stat as a Service installation option is available that can facilitate for an easy and complete deployment of the .Stat Suite to test and evaluate for your own project needs.
The Community welcomes new members from statistical based organisations of a non-commercial nature.
By becoming a member of the community means that your organisation is committing to contribute and co-invest in the core project, which in turn allows you to drive both the community and product directions, and benefit from the other community members and the core team.
An Memorandum of Understanding “MoU”, the bilateral agreement between the OECD and a new member is first agreed and then signed, and this provides the framework for the collaboration.
The community welcomes contributions from all interested parties, from just providing feedback, to a new or an extension of an existing feature. All developments follow a standard lifecycle using common industry tools for managing versioning, integration, and release of software packages.
If you are interested to contribute then please check out the developers section.