Deletion and Archiving
Over time, the number of Events, results and tracks on the MapRun server will continued to grow and require management. This page describes the current and proposed arrangements. (On this page "MapRun" means MapRunF, MapRun6 and MapRunG).
Events
When an Administrator publishes an event, two main components are created on the MapRun server:
- Event Files: The Map and Course files are copied to the folders in which the MapRun App looks for events, and
- RouteGadget: A RouteGadget event is setup to process and display the results and tracks.
Results and Tracks
After a participant completes in an event and uploads their result to the MapRun server:
In addition to the files mentioned above, the MapRun server uses a PostgreSQL database of Events and Results (but not Tracks).
No deletion or archival of this database is planned.
This database provides for analysis and reporting and an increasing range of operational functions.
Date Ranges
MapRun6 introduced "Date Ranges" (From and To Dates). Admins can set date ranges for Events for:
The intention is for the MapRun server to automatically delete old events and associated results **. That is, Events where participation is no longer allowed and results and tracks are no longer displayed. The default dates (unless changed by the Admin publishing the event, or edited subsequently) are: Date of Publishing plus 12 months for participation, and Date of Publishing plus 24 months for results and track display. The deletion option used is the first option described below but also includes the deletion of results.
This means that the events and results in MapRun would generally be those for events over the last 2 years (except where Admins have set longer ranges on particular events).
**Note: CombinedResults files are currently NOT deleted, meaning that the basic LeaderBoard display of results remains indefinitely (See the section below "Personal History of Runs in MapRun" to see how to access old LeaderBoard results).
Event Deletion
There are two Event deletion options in the MapRun Console. These can be used to remove events that are in error or are no longer required:
Archiving of Results and Tracks
The single-line result files (.csv) and track (.gpx), saved in a folder of individual results, are archived to archive storage typically after 6 months. The implications of this are:
Personal History of Runs in MapRun
A participants personal history of runs as shown when:
Combined results in the _Old folder are available via this link: http://www.p.fne.com.au/rg/cgi-bin/SelectResultFileForSplitsBrowserFilteredOld1.cgi?HideCombinedResults=yes
Archiving of RouteGadget Files (FUTURE)
RouteGadget's storage for an event can be quite large, being its internal representation of the map, course, results and tracks.
It may become desirable to archive some older RouteGadget Events, before the Event is deleted automatically as mentioned in the "Date Ranges" section above. The implications of this are:
Admins can use the "Restore RouteGadget Event from Archive" function to restore this Event (at least temporarily until the Archival function runs again - expected to be Monthly.) If the event is intended to be ongoing, longer than the Archival period, one option is, to delete the old event, and create a fresh event using the same files. (Refresh results to recompute the full set of results).
Refreshing results in an event where the RouteGadget files have been archived results in an error (ie fails). Therefore if it is required to Refresh results in an event that has been archived, use the "Restore RouteGadget Event from Archive" first.
Summary
The typical lifecycle of an Event is as shown below. This assumes the Admin has not changed the default dates for an event.
Events
When an Administrator publishes an event, two main components are created on the MapRun server:
- Event Files: The Map and Course files are copied to the folders in which the MapRun App looks for events, and
- RouteGadget: A RouteGadget event is setup to process and display the results and tracks.
Results and Tracks
After a participant completes in an event and uploads their result to the MapRun server:
- A single-line result file (.csv) and their track (.gpx) are saved in a folder of "individual" results
- The server then matches these files to the relevant event and:
- updates the "combined" results file for the event (standard OE-format Orienteering results file) as used by the LeaderBoard display of results, and
- triggers RouteGadget to process the files and add the result into the RouteGadget (and Splitzbrowser) system and also adds the runners route to the routes that can be displayed.
- Note that RouteGadget keeps a copy of the results and tracks in its own internal format.
In addition to the files mentioned above, the MapRun server uses a PostgreSQL database of Events and Results (but not Tracks).
No deletion or archival of this database is planned.
This database provides for analysis and reporting and an increasing range of operational functions.
Date Ranges
MapRun6 introduced "Date Ranges" (From and To Dates). Admins can set date ranges for Events for:
- When the event can be participated in. This is checked on “Go to Start” so it applies even to copies of the event which have previously been downloaded onto the phone. Date ranges cannot be retrospectively implemented into MapRunF, and so these will only be fully applicable once all users are using MapRun6.
- When the results table will be displayed.
- When the tracks will be displayed.
The intention is for the MapRun server to automatically delete old events and associated results **. That is, Events where participation is no longer allowed and results and tracks are no longer displayed. The default dates (unless changed by the Admin publishing the event, or edited subsequently) are: Date of Publishing plus 12 months for participation, and Date of Publishing plus 24 months for results and track display. The deletion option used is the first option described below but also includes the deletion of results.
This means that the events and results in MapRun would generally be those for events over the last 2 years (except where Admins have set longer ranges on particular events).
**Note: CombinedResults files are currently NOT deleted, meaning that the basic LeaderBoard display of results remains indefinitely (See the section below "Personal History of Runs in MapRun" to see how to access old LeaderBoard results).
Event Deletion
There are two Event deletion options in the MapRun Console. These can be used to remove events that are in error or are no longer required:
- The first, gives a list of the RouteGadget Events, allows the Admin to select one and then removes this event from RouteGadget and also deletes the source files (Map, Course) from the Event Folders that the MapRun App accesses. Results and tracks are not deleted.
- This affects:
- Availability of the Event to be participated in: The MapRun App will no longer find this as an event in the event folders, so no new runs in the event are possible (except, if a runner has previously selected the event and therefore will have a copy of the event in MapRun on their phone, and could still run in it ... unless they are prevented by the "Participation Date Range" set for the event (see more on this above)).
- Results Display: The "combined" results file mentioned above remains un-touched and so the LeaderBoard is still available, however as the RouteGadget event has been removed, no tracks can be displayed.
- This affects:
- The second, just removes the source files (Map, Course) from the Event Folders that the MapRun App accesses. This option presents a list of Events within your folders and does not rely upon RouteGadget at all. Results and tracks are not deleted.
- This affects:
- Availability of the Event to be used: This is the same as for the first option above.
- Results Display is NOT affected.
- This affects:
Archiving of Results and Tracks
The single-line result files (.csv) and track (.gpx), saved in a folder of individual results, are archived to archive storage typically after 6 months. The implications of this are:
- New results and tracks are still added to the combined results and RouteGadget in the normal way.
- The Leaderboard, RouteGadget and a participant's personal history of runs are unaffected.
- HOWEVER, Administrators need to be aware:
- If they do a "Refresh" of results for the event, this goes back to the individual result files and completely re-creates the results for the event. This will NOT see any results that have been archived.
- A "Refresh" is most likely required by the need to edit a result (as for an edit to display in the results, requires the results for the event to be re-computed (via a "Refresh")
- If a complete set of results is desired in such a case:
- Use the Admin function to "Restore Results from Archive" for this event, and then do a "Refresh"
- Also, see below, if the RouteGadget event files have been archived, it is necessary to restore them before the "Refresh" function will work.
- Note that result files and RouteGadget event files restored in this way will be archived again the next time the archival process runs. (Unless the date range on the event is changed).
- If they do a "Refresh" of results for the event, this goes back to the individual result files and completely re-creates the results for the event. This will NOT see any results that have been archived.
Personal History of Runs in MapRun
A participants personal history of runs as shown when:
- clicking on the runner's name in the LeaderBoard or
- in the extract for mail merge of personal results
Combined results in the _Old folder are available via this link: http://www.p.fne.com.au/rg/cgi-bin/SelectResultFileForSplitsBrowserFilteredOld1.cgi?HideCombinedResults=yes
Archiving of RouteGadget Files (FUTURE)
RouteGadget's storage for an event can be quite large, being its internal representation of the map, course, results and tracks.
It may become desirable to archive some older RouteGadget Events, before the Event is deleted automatically as mentioned in the "Date Ranges" section above. The implications of this are:
- The ability to participate in the event is unaffected (unless prevented by the allowed Date Range for participation)
- The Leaderboard is unaffected, but tracks will not be displayed (as the RouteGadget event has been removed.
Admins can use the "Restore RouteGadget Event from Archive" function to restore this Event (at least temporarily until the Archival function runs again - expected to be Monthly.) If the event is intended to be ongoing, longer than the Archival period, one option is, to delete the old event, and create a fresh event using the same files. (Refresh results to recompute the full set of results).
Refreshing results in an event where the RouteGadget files have been archived results in an error (ie fails). Therefore if it is required to Refresh results in an event that has been archived, use the "Restore RouteGadget Event from Archive" first.
Summary
The typical lifecycle of an Event is as shown below. This assumes the Admin has not changed the default dates for an event.
Please report any issues via email to: [email protected]