10. The month_options method

This method takes the same inputs as “date_time_options” and returns almost the same outputs, except for where a performance list would be returned where it only returns a list of months which contain valid performances. The intended use is that this call is made first, with the result being used to allow the user to select a month before selcting their performance. This increases the speed with which a performance may be selected by reducing the data that needs to be transferred.

10.1. Required inputs

These are the same as for “date_time_options” and that section may be used as a reference.

10.1.1. Example input


10.2. Output data

No crypto_block is produced at the output, as the intent is to provie data which will be used for a real subsequent call to “date_time_options”. For the most part, the output is identical to that for “date_time_options” with the exception of the contents of the elements conatined within a using_perf_list element. Instead of individual performances, instead “month” elements will be output. Each element describes a single month containing valid performances. The year is held in “year_number” and a numeric value for the month in “month_number”. Textual descriptions of the name of the month in the current language, in both short and long form, are to be found in the “short_month_name” and “long_month_name” elements. Finally two elements are provided to give the first and last date of the month. These are “earliest_date” and “latest_date”, and may be fed directly into date_time_options to restrict the data it returns.

10.2.1. Example output





10.3. Potential failure codes

This call may respond with any failure codes returned by “date_time_options” with the same meanings.