Editing Activities with Cloud Editor and OpenField Console - Best Practice

When the Cloud Editor is enabled for your OpenField account, you will be able to edit Activities on both OpenField Cloud and OpenField Console.

Click here for more information on how to use the Cloud Editor

Changes made to activities via the Cloud Editor can be synced down to OpenField Console and vice versa.

To ensure a smooth and efficient experience, this article outlines some recommended 'best practices' and expected outcomes when editing activities on either the Console or the Cloud.

Recommended Activity Editing Best Practices

Catapult strongly encourages following the below 'best practices' to ensure a smooth and efficient experience when editing your activities and subsequently reviewing or reporting on your athletes' data:

• Edit activities on the Cloud as much as possible, to save time compared to editing activities on Console and syncing changes to the Cloud for reporting!
   
• Ensure only one user is editing the same activity at a time, on either the Console or Cloud, to ensure there are no editing conflicts or surprise changes!
   
• Perform a sync on OpenField Console after you've finished editing an Activity on either Console or Cloud, to ensure both the Console and Cloud show the most up-to-date information for your activities!
   
  • Rebake an activity in Console that has been edited on Cloud, if you want to load and review this activity in the Console, to ensure the most up to date data is presented in Console Widgets and Console exports!

How do Activity Edits sync up and down from Console to Cloud

Changes made to activities via the Cloud Editor can be synced down to OpenField Console and vice versa.

Why can't I see a Fast or Full Sync button anymore?

When the Cloud Editor is enabled for your OpenField account, the Fast Sync button will no longer be available, and will be replaced with a Sync button, that acts the same as a Full Sync.

This is to ensure all data files are uploaded to the Cloud as part of a Sync, which is needed when an activity is reprocessed on the Cloud whenever the activity is edited in the Cloud Editor.



It is strongly recommended that OpenField Console is synced after an activity is edited on either the Console or the Cloud, to ensure that when the activity is viewed on either platform the activity is as up-to-date as possible, and to avoid any activity editing conflicts.

What if I make edits to the same activity on Cloud and Console at the same time?

In the event the same activity is edited on the Console and Cloud before the Console is synced, you can expect to see some of the below outcomes after the Console is next synced:

• If the same 'entities' (such as Periods, Rotations, Annotations, Athletes in Period) are edited on both Console and Cloud, the edits performed on Cloud will overwrite the edits made on Console.
   
• If different 'entities' are added or edited on both Console and Cloud, the edits made to each entity will be saved and synced up/down to both Console and Cloud.

The sample workflow and activity below displays how renaming (editing) the same period results in the edits made in Cloud to overwrite edits made in Console:

1. An Activity has a single period and Console has been Synced:
   
   
    
2. The activity can be viewed in Cloud Editor with the same period information:
   
   
    
3. The activity's period is edited in the Console and is renamed to 'Console Edited Period'.
   Before Syncing the activity's Period is edited in the Cloud Editor and is renamed to 'Cloud Edited Period':
   
   
   
   
    
4. The Console is synced, and once the sync is complete the Cloud is refreshed. 
    
5. The edits made in the Cloud overwrite the edits made in Console, so the period is named 'Cloud Edited Period', when the activity is viewed in the Cloud and Console: