Import Restrictions (Director)

Restrictions or scheduling requests can be imported with the teams import template.  The following restriction columns are available for import and will automatically create the restriction in the system for you.  Each column has a certain format and must be followed to work correctly.  We will notify if an error is made with a restriction format and notify the row that has the issue.

Date/Time Restrictions (DateTimeRestrictions)

This column is for teams that have a date/time scheduling request, maybe a team can only play in the morning or on a certain day.  The restriction can exclude or include (except for a specific date).  The following rules are listed below:

Schedule

If a team can play during a certain date/time then start the restriction off with one of the following operators below.

• after (after {time}, after {time} on {date}, after {time} {date})
• before (before {time}, before {time} on {date}, before {time} {date})
• between (between {starttime} ("&" or "and" or "-") {endtime} on {date})

Don't Schedule

If a team can't play during a certain date/time then start the restriction off with one of the following operators below.  

• not after (not after {time}, not after {time} on {date}, not after {time} {date})  
• not before (not before {time}, not before {time} on {date}, not before {time} {date})  
• not between (not between {starttime} ("&" or "and" or "-") {endtime} on {date})  
• not on (not on {date})

Rules

• Multiple Date/Time Restrictions in a row are separated by a comma (see row 7).
• AM or PM is required for times.
• The Between operator can use the following to separate the start and end time: and, &, - (see row 3,8,9)
• Not On operator can only be used with a Date (see row 5,6)
• If the Year is not provided with a Date then the Current Year is used (see row 6).
• If the day of the week (sat,sun,mon,tue,wed,thu,fri) is used for the Date, then the following day of the week from the current import date is used (Importing on Thursday will use that weekend's Saturday for the word sat, see row 2,4,5,7)

Edge Case

If you want a team to play between two times and use the between operator, it stores that retriction inverted, excluding before the start time and after the end time.  This works fine unless you have another restriction in conjuction with this that might be an after or before operator. These will be ignored since the between operator excluded everything before and after it.  In the future we will store these as an inclusion, but right now we save our date/time restrictions with when a team CAN'T play.  

Matchup Restrictions (MatchupRestrictions)

This column is for teams that can't play against each other in a match-up but can play at the same time.  This is more for teams from the same organization but different coaches.  When auto creating match-ups this restriction will also be taken into account.  Read the Team Restrictions section below for the format of this column.

Team Restrictions (TeamRestrictions)

This column is for teams that don't want to play at the same time, maybe they have the same coach.  The full division name is required along with the optional team name if the names are exactly the same in both divisions.  It's not necessary to put this restriction in for both teams as it will create a bi-directional restriction but is recommended for human readability.  The following rules are listed below.

• Format: (minimum)|TeamName or DivisionName (only if team names are the same)
• Multiple Team Restrictions in a row are separated by a comma (see row 2,3,6). 
• If the Team Name is the same in the reference, the Division Name is only needed (see row 4)
• If the Team Name is different in the reference, the Division Name and Team Name are required, separated by a pipe character (|) (see row 1,5)
• Restrictions are not needed on both teams but is recommended.

Game / Venue Restrictions (GameRestrictions,VenueRestrictions)

This column can set the minimum, maximum or range of games for a team for an entire event or specific date and also at a certain location.

• ({minimum}(-{maximum})) (on {date}) (at {venue}) (on {court,field,rink}))
• ({minimum} or more) (on {date}) (at {venue}) (on {court,field,rink}))
• ({maximum} or less) (on {date}) (at {venue}) (on {court,field,rink}))

Rules

• Multiple Game/Venue Restrictions in a row are separated by a comma (see row 6).
• Minimum formats include 1 or more, 1-, 1-2
• Maximum formats include 1 or less, -1, 1-2
• Date format must have on before it
• Venue name must have at before it
• Court, field or rink can be included after on and requires a venue before it
• If the Year is not provided with a Date then the Current Year is used (see row 6).
• If the day of the week (sat,sun,mon,tue,wed,thu,fri) is used for the Date, then the following day of the week from the current import date is used (Importing on Thursday will use that weekend's Saturday for the word sat, see row 2,4,5,7)

Exhibition Restriction (ExhibitionRestriction)

This column is for teams that will have all their games marked as an exhibition, meaning their games won't count against pool standings.  This option is good for teams who may only play one day in a shootout and must be last in the pool.  This column only requires a boolean value which can be Yes, Y, True, or 1, otherwise leave blank.