Are there guidelines for entering data that will make it easier for council personnel to process ScoutNET reports?
Yes, here are some data entry tips we got from BSA: Don’t enter data with ‘Caps Lock’ on, particularly when entering names. ScoutNET expects the first letter to be capitalized and the remainder to be lower case. Of course, names like McCoy, Van Dam, and O’Connor are exceptions. Don’t punctuate any information unnecessarily, especially addresses and abbreviations. For example, instead of ‘St.’ enter ‘St’; instead of ‘Apt #22-B’ enter ‘Apt 22B’; etc. However, sometimes hyphens and slashes are needed for postal delivery (e.g., 10-234 Main St, and 103 1/2 Oak Blvd) Don’t use data fields to store data other than what is requested by the field label because it can cause processing of your recharter to fail. For example, don’t enter driver’s license number and license expiration date in the driver’s license number field. If you need to record data for which there are no system-defined data items, use the ‘remarks’ or, better, create your own data items. That can be done on the Remarks/Other t
Related Questions
- Are there guidelines for entering data that will make it easier for council personnel to process ScoutNET reports?
- What guidelines will be available for data cleansing and matching for the data load process into ESR?
- Why is so much data on LHD services and personnel needed for the COOP planning process?
