PIN / Lock Code - Details
- Why Use A PIN?
- For competitive events, it is common to want to keep the course confidential until the scheduled date/time for the event.
- This can be achieved by putting a "PIN" / lock-code on the event.
- For events with a PIN, the user can "Select" the event to download it onto their phone, and when they tap "Go to Start" they will be prompted for a confidential 4-digit code before the course is displayed.
- As the course can also be displayed, by selecting this event in the result list (RouteGadget), the same PIN is required to display runners tracks (either in MapRun or via the Web).
- Types of PINs
- A PIN can either have a time/date associated with it or not.
- Simple PIN without a Time/Date
- If you have an "event'" for testing, or checking control sites, or that you would like to keep confidential indefinitely, then use a simple PIN that does not have a date.
- For example:
- If you have a course at a school that will be used each term with different students, you may want to keep the event confidential indefinitely. For each group of students to use the course, provide them with the PIN on the day.
- or If you are wanting to check the accuracy of flags put out for a "traditional" orienteering event, you might just use a simple PIN so that anyone browsing through events, will not be able to inspect the course. You will probably simply delete the event after you have done your checking.
- For example:
- If you have an "event'" for testing, or checking control sites, or that you would like to keep confidential indefinitely, then use a simple PIN that does not have a date.
- A PIN with a Time/Date (Expiry)
- For an event in a typical Club schedule of events, the PIN is normally set with a Time/Date of the one hour after the scheduled start block
- So, if your event is for starts between 4pm and 5pm on Saturday, it is common to set the PIN time/date to be 5pm on Saturday's date
- This means that for runners starting in the event from say 4pm:
- The organiser will provide the 4-digit code to allow them to access the event and start (typically when they are handed the printed map)
- This could be for a Mass Start at 4pm (which may slip back to say 4:10pm for example) where the PIN is announced to a group, or
- For individual starts, where the PIN is provided to individuals at the start line.
- Typically, with MapRun, runners are encouraged to run a course in their own time after the scheduled event:
- Either as a re-run for training, or
- For the first time, if they were not able to run at the scheduled time/date.
- Events are typically not un-published/removed, but remain available. So by adding a time/date to a PIN, this EXPIRES the PIN, at the time, meaning that after that time/date, the PIN will NOT be prompted for, and the event will operate the same as if no PIN had been attached to the event.
- In the example above:
- After 5pm on Saturday:
- Runners will be able to open the event and run in it without having to know a PIN,
- The results will show runners tracks (on the map and course) either in MapRun or on the Web without needing a PIN
- If someone wants to look at the tracks for runners in "last-week's event" they will not need to remember the PIN for that event as the PIN will have expired. (ie not be required).
- After 5pm on Saturday:
- Having a PIN with a Time/Date does NOT mean that the event is only available from that time. It does NOT mean that a runner with the PIN can't run anytime before the PIN expiry time/date:
- next week's event may be published, and an organiser with the PIN can take an early run to check the course
- the start time could be brought forward without any problem or some runners could run early, They just need to know the PIN to enable this.
- It does NOT mean that the course is only "available" from a particular time/date. Any runs at any times before and after the time/date on the PIN are equally valid results and will be automatically included in the results for the event. Organisers can delete any particular result ... eg say test runs.
- Summary
- PIN with Time/Date (Expiry)
- This allows events to be published to the server and downloaded onto phones before the event, in such a way that they remain confidential until a 4-digit PIN is provided.
- It means that after the scheduled time, the event becomes open for use without a PIN
- It also means that the PIN is NOT required to access runners tracks in results (after the expiry of the PIN)
- PIN without a Time/Date
- This allows an event to not be public at any time either within the MapRun App or on the Web in the list of events in RouteGadget or the results
- This is ideal for testing, or training, or where an event will be used repeatedly for groups (eg schools)
- PIN with Time/Date (Expiry)
- FAQ's
- Does having a Time/Date on a PIN mean that the Event is only available to run from that time?
- NO. An event that has been published to the server can be run at any time. Up until the specified time/date, the PIN needs to be entered and after that time no PIN is required
- Do Events need to have a PIN?
- NO. Events can be published without a PIN. This is typically the case for "Permanent Courses" or where confidentially is not considered to be a key issue.
- Why not set the PIN expiry to the scheduled time of the event?
- In the example above, this is to say, why not set the PIN to expire at 4pm.
- If it is a Mass Start event scheduled for 4pm, sometimes delays can occur eg handing out maps, providing instructions, waiting for latecomers etc. If the actual Mass Start ends up being at 4:10pm, the course will be available to runners for 10 mins before the start. (Which may not be a big issue, but it is not what was intended.)
- If it is an individual start event, it is best to have all runners in the start window, start under the same arrangements. If the PIN expired at 4pm, early runners would need to be provided with the PIN, but a runner starting at 4:10pm would have 10 mins of open access to the course before their run, and a runner at 4:30pm would have 30 mins etc.
- Can the Organiser determine the actual PIN code (ie the actual 4-digit number) for their event?
- NO. The PIN is determined automatically based on the name of the event. This is mainly so that the PIN does not have to be stored and downloaded to phones with the files for the event. Both the server and the MapRun App can determine what the PIN is for the event, by using the same coded algorithm.
- Does having a Time/Date on a PIN mean that the Event is only available to run from that time?