Recurrence Format Sample Clauses

Recurrence Format. In this section we provide specifics regarding how to interact with one of the most important and commonly used methods, named INSERT_PERSON_CALENDAR and UPDATE_PERSON_CALENDAR that create a new calendar/agenda item for the elderly or update an existing one. In order for the Agenda Service to handle recurrence events, we utilized the calendar component that stores the rules of recurrences. A periodically executed component, called the Agenda Daemon, translate those recurrences to agenda items. In other words, the insertion of new events are stored to the calendar table (PERSON_CALENDAR) and the retrieval from the agenda table (PERSON_AGENDA). Therefore, one calendar item can produce multiple agenda items depending on its recurrence. In more detail, for each calendar item, the daemon generates all occurrences for one year at the time until the number of occurrences or the recurrence date is reached. In the following table, is presented a more detailed description of the PERSON_CALENDAR table. Field Name Type Nullable Default Value Constraints REMINDER_TIME int No 0 N/A This represents the notification reminder time in minutes. Note that negative values represent that the notification will be triggered before the event while positive values (highly improbable) represent that the notification will be triggered after the event. WEEK_DAY_PATTE RN int No 127 Between 1 and 127 This represents a coding scheme that has been devised for easily entering a week days pattern. More specifically, we have coded each day with a number (following a binary approach) as follows: • 1=Monday • 2=Tuesday • 4=Wednesday • 8=Thursday • 16=Friday • 32=Saturday • 64=Sunday For example, if the calendar item should be repeated every Wednesday, Thursdays and Sunday then the field should be set to 76 (i.e., 4=Wednesday + 8=Thursday + 64=Sunday). All days are represented by the total sum of all days which is 127. DAY_FREQUENCY int Yes Larger or equal to 1 This represents the daily frequency of the calendar item, i.e. 1 represents every day, 2 represents every second day, 3 represents every third day, etc. EXACT_DAY int Yes NULL or between 1 and 31 This represents a calendar item that occurs a specific day of the month, e.g., 4th day of the month. OCCURRENCE_NO int Yes NULL or >=0 This represents a specific occurrence. We have coded this as follows: 1 represents the first occurrence, 2 represents the second occurrence, 3 represents the third occurrence, etc. Additionally, we have coded the...
Sample 1
AutoNDA by SimpleDocs

Related to Recurrence Format

  • Protocol The attached Protocol shall be an integral part of this Agreement.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Metrics Institutional Metrics System-Wide Metrics

  • RDDS query RTT Refers to the collective of “WHOIS query RTT” and “Web-­‐based-­‐ WHOIS query RTT”.

  • Measuring EPP parameters Every 5 minutes, EPP probes will select one “IP address” of the EPP servers of the TLD being monitored and make an “EPP test”; every time they should alternate between the 3 different types of commands and between the commands inside each category. If an “EPP test” result is undefined/unanswered, the EPP service will be considered as unavailable from that probe until it is time to make a new test.

  • EPP query-­‐command RTT Refers to the RTT of the sequence of packets that includes the sending of a query command plus the reception of the EPP response for only one EPP query command. It does not include packets needed for the start or close of either the EPP or the TCP session. EPP query commands are those described in section 2.9.2 of EPP RFC 5730. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

  • Net Cash Flow The term “Net Cash Flow” shall mean all cash and cash equivalents from all sources on hand as of the last day of the measurement period prior to any distributions to the Partners, and after the payment of all then due expenses of operating and managing the Restaurants, and after payment of all debts and liabilities and after any prepayments of any debts and liabilities that the General Partner, in its reasonable and good faith discretion, elects to cause to be made, and after the establishment of any reserves reasonably deemed necessary by the General Partner for (i) the repayment of any due debts or liabilities, including debts owed to the General Partner; (ii) the working capital requirements; (iii) capital improvements and replacement of furniture, fixtures or equipment; and (iv) any contingent or unforeseen liabilities. In determining Net Cash Flow of each Restaurant there shall be deducted the Supervision Fee and the Accounting Fee as provided in Section 4.7, the Advertising Payment and the Insurance Payment as provided in Section 4.8, and the OSRS Charges as provided in Section 4.2.

  • Measuring DNS parameters Every minute, every DNS probe will make an UDP or TCP “DNS test” to each of the public-­‐DNS registered “IP addresses” of the name servers of the domain name being monitored. If a “DNS test” result is undefined/unanswered, the tested IP will be considered unavailable from that probe until it is time to make a new test.

  • Signaling protocol The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. Where available, CenturyLink signaling services to link its Signaling Transfer Points (STPs) for CLEC switches which connect to CenturyLink’s STPs via “A” links or for CLEC’s STPs to connect to CenturyLink’s STPs via “D” links which are dedicated to the transport of signaling for local Interconnection, may be ordered from the CenturyLink Tariff.

  • Mobile Application If Red Hat offers products and services through applications available on your wireless or other mobile Device (such as a mobile phone) (the "Mobile Application Services"), these Mobile Application Services are governed by the applicable additional terms governing such Mobile Application Service. Red Hat does not charge for these Mobile Application Services unless otherwise provided in the applicable additional terms. However, your wireless carrier's standard messaging rates and other messaging, data and other rates and charges will apply to certain Mobile Application Services. You should check with your carrier to find out what plans your carrier offers and how much the plans cost. In addition, the use or availability of certain Mobile Application Services may be prohibited or restricted by your wireless carrier, and not all Mobile Application Services may work with all wireless carriers or Devices. Therefore, you should check with your wireless carrier to find out if the Mobile Application Services are available for your wireless Device, and what restrictions, if any, may be applicable to your use of such Mobile Application Services.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!