6 E-device Questionnaire

6.1 E-device Questionnaire Outline

An Electronic Field Data-Entry Device (“e-Device”) Questionnaire was distributed to IEP survey leads in July of 2022. The goals of this questionnaire were: 1. To get an understanding of the current level of use of electronic field data entry devices among IEP survey staff; 2. To seek information from expert e-device users about both hardware and software considerations, and 3. To the learn specific roadblocks for those who are hesitant to consider shifting to electronic data entry methods.

Three groups were targeted for this questionnaire:

  1. Experienced e-device users (internal IEP and external agencies),
  2. IEP Survey Staff who are researching e-devices for field application,
  3. IEP Survey Staff who don’t believe electronic field data collection will work for their application.

6.2 Questionnaire Respondents

The IEP e-device questionnaire was run for approximately a month and received 24 responses (Figure 6.1. A link to the original questionnaire and to the compiled questionnaire responses is included in the Appendix See IEP E-device Survey.

The distribution of responses to the e-device questionnaire by agency association. Most of these respondents were CDFW staff, but USFWS and DWR responses were also represented.  Two external agencies (NEON and ICF) were specifically asked to participate after the questionnaire responses pointed to these expert resources.

Figure 6.1: The distribution of responses to the e-device questionnaire by agency association. Most of these respondents were CDFW staff, but USFWS and DWR responses were also represented. Two external agencies (NEON and ICF) were specifically asked to participate after the questionnaire responses pointed to these expert resources.

Among the 24 respondents, half of these were IEP associates and external contacts that are already using e-device applications for their survey data collections. Five (20%) of the respondents were IEP associates who were currently seeking e-device solutions for their survey data collections. Two of the respondents indicated that they have already determined that electronic data entry would not work for their IEP survey application, and 5 respondents did not answer the question about their e-device use experience/status. An experienced e-device user resource list has been initiated, including contact names, software type, and type of survey application; this list will be expanded as possible (Appendix D) Expert Network.

6.3 Most Common Software Applications Used

Table 6.1: Most common e-device software applications used by the IEP members who responded to the e-device questionnaire.
Application Agency Type of Application/Data Collected
ESRI Survey123 ICF, NEON fish & zooplankton surveys, water quality
Pendragon DWR, CDFW fish & zooplankton surveys, water quality
Fulcrum ICF, NEON field data collection, botanical & wildlife surveys
Adobe PDF Forms ICF, DWR field data collection
.NET customized DWR, USGS, CDFW MOPED water quality, SVMAQ water quality & discharge
iFormbuilder ICF
Zoho ICF
Access, Excel ICF, USFWS tributary monitoring
ESRI Collector, ESRI Field Maps USFWS, CDFW, UC geolocation of FAV, positional accuracy, spawning ground surveys

6.4 Key questions/concerns about using e-devices (derived from the e-device questionnaire)

A series of key questions were extracted from the questionnaire responses, and were further developed in the first several working group meetings. These questions outline most difficult hurdles that questionnaire leads address when adopting electronic data entry technology for shipboard surveys.

  • Forms:
    Do I need to know a programming language to develop a data entry form?
    Can the forms builder be used to represent a highly nested sampling design?
    Can I review fish length data as a list? Can I edit my data ‘on-the-fly’?
    Can I take photos and link to the record at various levels of a nested sampling design?

  • Data Export Formats and Transfers:
    What is the format of the exported data?
    Can the exported data be integrated with an existing Access or SQL database?
    What procedures are needed for uploading to the database (for each output type)?
    Can I make a back-up of the data locally when an internet connection is not available?

  • Reading external data inputs:
    Can I incorporate data from an external sensor into the app? GPS, Fish boards, Bar Codes?

  • IT Security and Version Control:
    Does the app have network security certificates; has the security been vetted?
    Are there version control options for data pushed to cloud repositories from the field?

  • Hardware:
    Can a handheld device truly be weatherproof?
    How can we keep these devices from dropping overboard during fishing and processing activities?

  • QA/QC:
    What features of the data entry software are critical for supporting quality assurance and quality control routines.