The Basic Meeting List Toolbox

Change Parameters

Try The New Semantic Workshop!

Parameters for the “switcher=GetChanges” Value

The change record retrieval functionality is extremely powerful. Every time a change is made to a meeting, Service body or format, a record is made of the event. In the case of meetings, we only save the last X number of changes, to prevent the database from becoming too huge. In the default implementation of the Root Server, X is set to 5 (the last five changes made).

This switcher value only returns meeting changes. It selects these changes based on the following parameters:

start_date
SYNTAX:

start_date=<em>&lt;YYYY-MM-DD&gt;

(The ‘Y-m-d’ PHP date() function format, also known as the ISO 8601 format. Example: ‘2011-06-11’ is June 11th, 2011)

If this is specified, then the changes returned will be from this date (starting at 12 AM), forward.
end_date
SYNTAX:

end_date=<em>&lt;YYYY-MM-DD&gt;

If this is specified, then the changes returned will be until this date (ending at 12 AM of the next day). You can specify both of these, to provide a “window of time.”
meeting_id
SYNTAX:

meeting_id=<em>&lt;Meeting ID&gt;

(This must be the integer id_bigint of the BMLT root server, for a specific meeting.

If specified, then the changes affecting one meeting will be returned. Remember that the BMLT root server “prunes” meeting changes, so you may not be able to get more than the maximum number of changes (the default is five changes). Only one meeting ID can be supplied.
service_body_id
SYNTAX:

service_body_id=<em>&lt;Service Body ID&gt;</em>

(This must be the integer id_bigint of the BMLT root server, for a specific Service body.)

If specified, then the changes affecting all the meetings associated with a Service body will be returned. Remember that the BMLT root server “prunes” meeting changes, so you may not be able to get more than the maximum number of changes per meeting (the default is five changes). Only one Service body ID can be supplied. Additionally, if the Service body “contains” other Service bodies (like an RSC “contains” ASCs), then the “child” Service bodies will be included in the response.