Difference between revisions of "Unify Monthly Data"
(→Setting the Monthly Format) |
(→Getting the Registry's Format) |
||
Line 27: | Line 27: | ||
<pre> | <pre> | ||
{ | { | ||
− | "MonthlyDataFormat": " | + | "MonthlyDataFormat": "EXCLUDE_M_CHARACTER" |
} | } | ||
</pre> | </pre> |
Revision as of 01:25, 30 October 2020
Contents
Overview
The Registry has the ability to unify monthly data so that the formats: yyyy-mm and yyyy-Mmm are considered the same on a data input. By default the Registry will treat the dates 2000-01 and 2000-M01 as different observation times. If you wish these to be represented as the same format (either with or without the "M" character) this can be enabled in the Registry. In Registry version 10.5.7 there is no User Interface for this feature and it must be enabled by invoking a Web Service.
Web Services
There are two Web Services: one for setting the way the Registry interprets monthly dates and the other for returning the current way that the Registry is set up.
Setting the Monthly Format
Issue a POST request to the URL: <registry location>/ws/secure/settings/setDataFrequencyFormat
This is a secure Web Service, so Authentication Credentials must be provided.
The Web Service takes a JSON Object which has a single field "MonthlyDataFormat". Valid values for this are: "", "INCLUDE_M_CHARACTER", "EXCLUDE_M_CHARACTER"
An example of Valid JSON:
{ "MonthlyDataFormat": "INCLUDE_M_CHARACTER" }
Getting the Registry's Format
Issue a GET request to the URL: <registry location>/ws/secure/settings/getDataFrequencyFormat
This is a secure Web Service, so Authentication Credentials must be provided.
A JSON Object will be returned which will state how the Registry has been configured. An example:
{ "MonthlyDataFormat": "EXCLUDE_M_CHARACTER" }
Examples
POST requests cannot be made from a Web Browser (whereas GET requests can). A tool such as POSTMAN