Timebound XDS queries done right

As the author of the metadata document to be published shortly, I have also participated in some intense and disturbing discussions over time consultation on XDS / XCA should be performed. I say this deeply because this discussion includes nearly a dozen best minds on the XAD query and metadata model. Concerned because the discussion shows that the simple concept of time-based consultation on XDS / XCA is not understood. It’s confusing because we’ve discovered it many times. If it’s time to re-understand this understanding, it should be harder for others.

I’ve made mistakes
I wrote an article about our first attempt. I liked it. This is not a mistake. However, this leads to false positive and negative negatives that can be avoided. View the basics to accomplish the work when sharing documents.

When we introduced the metadata guidelines we sent for public comment, we turned against logic, so we made a very serious mistake.

Returning to the logic I often in my article, we see two improvements in our solution this week.

A change that adds the query parameter change space is useful because although we want everyone to be synchronized time, many of these times depend on human data, to start and stop. If you add a smart field, the hours you are looking for will start a little earlier and a little bit longer.

Another change is to use two parameters to check the service time of others to remove document entries that are just one of the time services included (start or stop, not the same). If something stops what you care about, it’s clearly not what you’re looking for or not. The same applies to something that did not start after the time you were looking for.

When we came to the final conclusion, it became clear that our readers probably did not understand it. Its part can be technical, because this booklet (and the blogger) has very little audience. We also feel we did earlier, and we made changes to the technical framework. We had, but we just mentioned CreationTime, one point in time. The hours of service are the …

serviceStartTime – serviceStopTime
If there is a timer area for event services where you are interested, you will be asked for service start times and the Stop Data component of the service, to find documents indicating that they fit into the your timer. , Hours of service are set for the date range or treatment cycle. This is different from the time you created the document. This is the time created by the document. Query results return any document whose service time is in this range. It’s important to know that these parameters work together to set a time span.

If you are interested in a certain time interval (Start -> Stop).

ServiceStartTimeFrom and serviceStopTimeTo show they need to limit this time to a small return to handle the bad time:

The service time start from the parameter should be set to the question a few minutes before the time if you are interested in becoming the time interval for the start of the service.
The serviceStopTimeTo parameter in the query should be ready a few minutes after the time you are interested in the date range where the service can be stopped.
If the service time or one of them is missing in DocumentEntry, it will be included in the results of the previous query. Therefore, we must look for ways to eliminate these false positives.

Some DocumentEntries have service start time, but no service downtime. It is common in cases of serious treatment, radiation and other cases where the termination of the service or termination is not possible. Therefore, you should include a query parameter that removes DocumentEntries that the start time is known between the time you are interested in:

Service parameterStartTimeTo must be set within minutes to query before it is covered by service time
Some DocumentEntries have a shutdown time but no start time. This is not the case, but this happens when there is no special start time for the note.

Leave a Reply

Your email address will not be published. Required fields are marked *