Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: No Action
    • Affects Version/s: wd22
    • Fix Version/s: wd24
    • Component/s: schema
    • Labels:
      None
    • Environment:

      Toby Considine

    • Resolution:
      Hide

      The EiConstraint service has been completely rewritten as the EiAvail service, using PR03 ws-calendar and emix structures.

      This comment has been overtaken by events.

      Close, no action.

      Show
      The EiConstraint service has been completely rewritten as the EiAvail service, using PR03 ws-calendar and emix structures. This comment has been overtaken by events. Close, no action.

      Description

      We have the Schedules from EMIX Constraints:

      availabiltySchedule
      unavailabilitySchedule

      We also have the EI ConstraintBehavior, which is hints at how to deal with times when there is an incompatibility between the temporal constraints of the schedule and the requirements of the event.

      Currently, the availability schedules are in the array of constraints. Should they instead be paired in some other object with the eiConstraintBehavior? This appears to be what the eiConstraintSchedule does. In refactoring [eiEvents] several constraints were eliminated, a couple new ones were added to EMIX constraints, and the event now has an array of constraints, unspecified.
      Should it be an Array of eiConstraintSchedule(s) with any single constraint modifiable by the eiConstraintBehavior? Should only some constraints be expressable in eiConstraintSchedule(s)?

        Attachments

          Activity

            People

            • Assignee:
              william.cox William Cox (Inactive)
              Reporter:
              toby.considine Toby Considine (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: