11. Computer-Assisted Data Collection and Database ManagementIntroduction and ContextComputer-assisted data collection has transformed the way organizations, researchers, public institutions, and firms generate evidence. Surveys can be distributed through web and mobile platforms; experiments can record behavioral responses automatically; application programming interfaces (APIs) can provide machine-readable operational data; web-scraping systems can monitor publicly available information; and sensors can capture continuous observations from physical environments. These developments improve speed, scale, and analytical possibility, but they also introduce important methodological, ethical, and governance problems. The central issue is not simply whether data can be collected. It is whether the data are collected for a legitimate purpose, from an appropriate population, with adequate consent and security, and whether they remain interpretable and trustworthy when stored, combined, analyzed, and shared. A technically efficient collection system can still produce invalid evidence if its sampling frame is biased, its measures are poorly designed, or its database silently changes the meaning of variables. Database management is therefore part of research design rather than a purely technical activity. Decisions about identifiers, data types, missing values, access permissions, metadata, and retention affect the credibility and reproducibility of research. In doctoral business research, the researcher must be able to connect substantive theory with operational definitions, digital collection instruments, data architecture, quality control, and responsible use. Learning ObjectivesBy the end of this chapter, the reader should be able to: 1. Design ethically defensible computer-assisted surveys, experiments, API processes, web-scraping systems, and sensor-based studies. 2. Distinguish validity, reliability, representativeness, completeness, accuracy, and timeliness in digital data. 3. Construct relational and non-relational datasets for research and organizational applications. 4. Develop data dictionaries, validation rules, identifiers, metadata, and quality-control procedures. 5. Use SQL concepts to retrieve, join, aggregate, and audit research data. 6. Explain interoperability, provenance, privacy, security, and governance requirements. 7. Evaluate the effects of automation, artificial intelligence, and emerging technologies on research ethics and data quality. From Research Question to Digital EvidenceA sound collection process begins with a research question, not with a preferred software platform. A research question should be translated into constructs, observable indicators, units of analysis, sources, and time periods. For example, a study of employee burnout may define the construct theoretically, operationalize it through validated survey items, identify employees as the unit of analysis, and specify how workload, autonomy, absence, and well-being will be measured. This translation is often represented through an operationalization chain: Research construct → variable or indicator → collection instrument → stored field → analytical measure. Weakness at any stage can undermine the final inference. A database may contain millions of records, yet fail to measure the intended construct. Conversely, a small, carefully designed dataset may provide stronger evidence because its definitions, sampling strategy, and provenance are clear. Several dimensions of data quality should be distinguished: - Accuracy: the degree to which a value represents the actual phenomenon.
- Completeness: the extent to which required records or fields are present.
- Consistency: the absence of contradictory representations across tables or systems.
- Validity: the extent to which values conform to permitted definitions and formats.
- Timeliness: whether data are available at the time required for the research or decision.
- Uniqueness: whether the same entity or event has been duplicated.
- Provenance: information about where data originated and how they were transformed.
These dimensions may conflict. Real-time sensor data may be timely but noisy; administrative records may be complete but generated for a purpose unrelated to the research question; scraped data may be extensive but unstable because websites change their structure. Designing Computer-Assisted SurveysComputer-assisted surveys include web surveys, mobile questionnaires, computer-assisted telephone interviewing, computer-assisted personal interviewing, and mixed-mode instruments. Their main advantage is programmable control. The system can randomize questions, apply skip logic, prevent impossible entries, issue reminders, and timestamp responses. However, automation does not eliminate design error. It can make a flawed instrument operate more efficiently. Question wording should be evaluated for clarity, neutrality, cognitive burden, and relevance. A double-barrelled question, such as “How satisfied are you with your salary and promotion opportunities?”, combines two constructs and prevents meaningful interpretation. Leading language can influence responses, while excessive use of matrix questions may cause satisficing, in which respondents select convenient rather than considered answers. A digital survey should specify: - the target population and sampling frame;
- inclusion and exclusion criteria;
- recruitment and consent procedures;
- the purpose and expected duration;
- response scales and permitted values;
- skip patterns and randomization rules;
- procedures for incomplete or withdrawn responses;
- protection of contact information and response data; and
- retention, deletion, and reporting arrangements.
Validation rules should be proportionate. A required field can improve completeness, but forcing a response to a sensitive question may be coercive. A range rule can detect that age has been entered as 250, but it cannot establish that a reported age of 35 is truthful. For sensitive research, respondents should often have a “prefer not to answer” option, provided that this does not compromise the research design. A pilot test should examine both substantive and technical performance. Researchers should ask pilot participants to explain how they interpreted difficult questions, while also testing browser compatibility, mobile display, accessibility, time stamps, branching, duplicate submissions, and data exports. Paradata—such as completion time, break-offs, device type, and navigation patterns—may help diagnose instrument problems, but their collection should be disclosed and justified. Experiments and Computerized MeasurementComputer-assisted experiments may randomize participants into conditions, present stimuli, record reaction times, or connect behavioral tasks to surveys and organizational systems. Randomization code, allocation rules, exclusion criteria, and stopping decisions should be documented before examining outcomes where feasible. Otherwise, flexible data processing can create undisclosed researcher degrees of freedom. The researcher must distinguish an experimental manipulation from the technology used to deliver it. A software platform may randomize assignments, but the validity of the experiment still depends on allocation concealment, manipulation fidelity, treatment compliance, measurement reliability, and control of confounding influences. Automated logging is valuable only when event definitions are stable. For instance, “session start” may mean opening a webpage in one system and completing authentication in another. Ethical review should address deception, potential distress, differential treatment, withdrawal, and post-study explanation. Digital experiments involving employees require special care because organizational authority may make voluntary participation difficult. A statement that participation is optional is insufficient if supervisors can identify nonparticipants or if refusal creates workplace disadvantage. APIs as Research InstrumentsAn API is a structured interface through which one software system requests data or services from another. APIs may deliver transaction records, social-media data, financial information, geospatial observations, or organizational metrics. A responsible API workflow begins by examining documentation, authentication requirements, rate limits, permitted uses, field definitions, version history, and deletion or correction mechanisms. API data should not be treated as self-explanatory. Researchers must record the request endpoint, parameters, retrieval time, response version, pagination logic, and transformations applied. If an API returns only current values, historical states may be unrecoverable. If records are updated after retrieval, a later researcher may not reproduce the original dataset unless snapshots or response hashes have been retained appropriately. A robust API pipeline separates: 1. Acquisition: authenticating and retrieving responses. 2. Staging: preserving raw responses in an unmodified, access-controlled location. 3. Transformation: parsing, standardizing, deduplicating, and enriching records. 4. Validation: testing schemas, required fields, types, ranges, and record counts. 5. Loading: placing approved data into analytical or operational tables. 6. Monitoring: recording failures, changes in schema, missing periods, and unusual volumes. Credentials must never be embedded in public code or stored in ordinary spreadsheets. Access tokens should be managed through appropriate secret-management mechanisms, with least-privilege permissions and rotation procedures. Web-Scraping and Publicly Available InformationWeb-scraping is the automated extraction of information from websites. Public accessibility does not automatically mean unrestricted ethical or legal usability. Researchers should examine terms of service, robots exclusion signals, copyright and database rights, privacy expectations, authentication barriers, and the sensitivity of the information. A person may post information publicly for a limited social purpose without reasonably expecting large-scale profiling. Scraping design should minimize burden. Request rates should be low enough to avoid disrupting a service, and researchers should identify themselves where appropriate. Data should be limited to fields necessary for the research question. Sensitive personal information, inferred attributes, and content posted by vulnerable individuals require heightened scrutiny. Because webpage structures change, scraping requires versioned code, collection logs, source URLs, retrieval dates, parsing tests, and failure alerts. A scraper that silently shifts from collecting product prices to collecting promotional text can create a misleading longitudinal dataset. Researchers should retain sufficient provenance to explain what was collected without unnecessarily retaining personal content. Sensor-Based and Internet-of-Things DataSensors produce observations through devices such as wearables, location systems, cameras, industrial monitors, point-of-sale terminals, and environmental instruments. Sensor studies require attention to calibration, sampling frequency, measurement error, battery or connectivity interruptions, device placement, and synchronization across clocks. A sensor value is not equivalent to a fact. It is an observation generated by a device under particular conditions. A location reading may be imprecise; an inactivity measure may reflect device removal; a temperature sensor may be affected by placement. Researchers should maintain calibration records, firmware versions, device identifiers, units of measurement, and quality flags. Sensor research is especially sensitive because continuous collection can reveal routines, health conditions, workplace behavior, or associations. Consent should specify what is collected, how frequently, for how long, who can access it, and whether raw or aggregated data will be shared. Where possible, collection should occur at the lowest resolution necessary. For example, a study of office occupancy may require room-level counts rather than individual movement histories. Building the Dataset: Relational and Non-Relational DesignsA relational database organizes data into tables connected through keys. A typical research database might contain tables for participants, survey responses, experimental sessions, and events. In a normalized design, each fact is stored in an appropriate location, reducing duplication and update anomalies. A participant table may store one row per participant, while a response table stores one row per question response linked through a participant identifier. Important relational concepts include: - Primary key: a field or combination of fields that uniquely identifies a row.
- Foreign key: a field referring to a key in another table.
- Entity integrity: the requirement that primary keys be unique and non-null.
- Referential integrity: the requirement that foreign-key references correspond to valid records.
- Normalization: organizing tables to reduce unnecessary redundancy and dependency problems.
- Denormalization: intentionally combining data to improve analytical performance or usability.
A simplified SQL structure might be expressed as: ```sql CREATE TABLE participant ( participant_id INTEGER PRIMARY KEY, consent_status VARCHAR(20) NOT NULL, enrollment_date DATE NOT NULL ); CREATE TABLE response ( response_id INTEGER PRIMARY KEY, participant_id INTEGER NOT NULL, question_code VARCHAR(40) NOT NULL, response_value VARCHAR(200), FOREIGN KEY (participant_id) REFERENCES participant(participant_id) ); ``` A query joining participants with their responses might be: ```sql SELECT p.participant_id, r.question_code, r.response_value FROM participant AS p JOIN response AS r ON p.participant_id = r.participant_id WHERE p.consent_status = 'consented'; ``` SQL is not merely a retrieval language. Constraints, transactions, views, and audit queries can support governance. For example, an audit can identify response records linked to nonexistent participants, duplicate event identifiers, or dates outside the approved study period. Non-relational databases are useful when data are highly variable, large in volume, rapidly generated, or naturally represented as documents, graphs, key-value pairs, or time series. A document database may store a survey session with nested answers; a graph database may represent relationships among organizations, directors, suppliers, or customers; a time-series database may efficiently manage sensor observations. Non-relational flexibility does not remove the need for structure. Schemas may be explicit, implicit, or evolving, but field definitions, versioning, validation, and access controls remain necessary. A document that permits every record to have a different meaning is not a flexible research database; it is an ungoverned collection of ambiguities. The choice between relational and non-relational architecture should follow data characteristics, query requirements, scale, interoperability needs, and governance capacity. Data Dictionaries, Metadata, and InteroperabilityA data dictionary is a formal description of dataset fields. At minimum, it should state the field name, label, definition, data type, unit, permitted values, missing-value codes, source, transformation history, sensitivity classification, and responsible owner. A useful dictionary distinguishes “not applicable,” “not asked,” “unknown,” and “withheld,” rather than coding all four as zero or blank. Metadata also describes the dataset as a whole: purpose, population, collection period, sampling procedure, instrument version, geographic coverage, processing steps, limitations, and licensing conditions. Without metadata, a technically readable file may be scientifically unusable. Interoperability is the ability of systems to exchange and meaningfully use information. Syntactic interoperability concerns formats and technical exchange; semantic interoperability concerns whether the same terms have the same meaning. Common formats such as CSV, JSON, XML, and Parquet support exchange, but formats alone do not create meaning. Date standards, controlled vocabularies, code lists, persistent identifiers, and documented mappings are equally important. A crosswalk can show how fields from two systems correspond. However, a mapping should identify imperfect equivalence. “Customer” in one system may mean a paying account, while in another it may mean any registered user. Treating them as identical can produce erroneous joins and biased findings. Quality-Control ArchitectureQuality control should occur throughout the data life cycle rather than at the end. Preventive controls include clear schemas, required fields, range checks, referential constraints, duplicate detection, and role-based permissions. Detective controls include reconciliation reports, anomaly detection, missingness analysis, sample verification, and comparison with trusted benchmarks. Corrective controls include documented cleaning rules, reprocessing, source correction, and versioned releases. A practical quality-control plan should answer five questions: 1. What error could occur? 2. How would the error be detected? 3. Who is responsible for reviewing it? 4. What action is taken when it occurs? 5. How is the decision documented? Cleaning must be reproducible. Researchers should preserve raw data separately, execute transformations through scripts or controlled workflows, record assumptions, and produce a change log. Manual editing of a master file is particularly risky because it obscures who changed what and why. Missing data require substantive interpretation. Missingness may result from technical failure, participant refusal, skip logic, attrition, or a value that is genuinely undefined. The mechanism may be related to observed or unobserved characteristics, so simply replacing blanks with zero can create serious bias. A missingness report should examine patterns across time, groups, instruments, devices, and collection channels. Ethical and Governance ResponsibilitiesEthical data collection rests on respect for persons, beneficence, justice, transparency, and accountability. Consent should be understandable, specific enough for the proposed uses, and obtained before collection unless a justified and approved exception applies. Consent is not a universal solution: it does not legitimize excessive collection, insecure storage, discriminatory analysis, or uses incompatible with reasonable expectations. Data minimization limits collection to what is necessary. Purpose limitation prevents later use from silently expanding beyond the original justification. De-identification can reduce risk, but removing names does not guarantee anonymity. Combinations of location, time, occupation, and rare characteristics may permit re-identification. Researchers should distinguish pseudonymization, in which a linking key remains, from anonymization, in which re-identification is not reasonably feasible under the relevant conditions. Governance should allocate responsibility for data ownership, stewardship, access approval, incident response, retention, deletion, and publication. Technical safeguards include encryption in transit and at rest, authentication, least-privilege access, secure backups, logging, environment separation, and vulnerability management. Data should not be copied casually into personal devices, unmanaged cloud storage, or public repositories. Regulatory requirements vary by jurisdiction and sector. Researchers must identify applicable privacy, health, employment, consumer-protection, intellectual-property, cybersecurity, and records-management rules. Institutional ethics review, contracts, data-processing agreements, and cross-border transfer requirements may also apply. Compliance is a floor, not a substitute for ethical judgment. A Research Data Life-Cycle FrameworkA defensible workflow can be organized into seven connected stages: 1. Specify: define the question, population, constructs, risks, and lawful or ethical basis. 2. Design: select instruments, sampling methods, architecture, identifiers, and validation rules. 3. Collect: acquire data with consent, security, provenance, and monitoring. 4. Process: stage, clean, transform, link, and document data without destroying raw evidence. 5. Store and govern: apply access controls, retention rules, backups, and versioning. 6. Analyze and share: disclose limitations, protect participants, and release only appropriate materials. 7. Archive or delete: preserve what is necessary for verification and securely dispose of what is no longer justified. This life-cycle perspective prevents the common mistake of treating data management as an activity that begins after fieldwork. In reality, storage, identifiers, disclosure risk, and retention influence the design of collection itself. Illustrative Case: A Retailer’s Employee Well-Being PlatformBackgroundNorthbridge Retail, a fictional multi-site retailer, wishes to study whether scheduling predictability is associated with employee well-being and turnover intentions. The organization proposes a mobile survey, integration with scheduling records, and optional wearable data concerning sleep and activity. Situation and ProblemThe initial proposal would collect precise location, full scheduling histories, free-text comments, and continuous wearable data from all employees. Supervisors would receive individual results, and participation would be promoted through line managers. The research team recognizes that the design could create coercion, excessive surveillance, and re-identification risk. AnalysisThe research question requires measures of schedule changes, perceived control, fatigue, well-being, and turnover intention. It does not require continuous location histories or identifiable wearable streams. The employment relationship creates a power imbalance, and supervisors’ access could compromise voluntary participation. Combining schedule and survey data also creates a linkage risk, especially in small stores. Approach and SolutionThe team redesigns the study. An independent research office manages recruitment and consent. Participation is voluntary, and supervisors receive only aggregate results for groups large enough to reduce identification risk. Scheduling data are converted into necessary indicators, such as number of changes and notice period, rather than retaining every location event. Wearable participation is optional, and only weekly aggregated sleep-duration categories are collected. Each participant receives a random study identifier. The identity key is stored separately with restricted access. The mobile survey uses range and completeness checks but permits “prefer not to answer” for sensitive items. A data dictionary defines every field, while an automated pipeline records source-system version, extraction time, transformation code, and validation results. Raw data are encrypted and retained only for the approved period. The analysis plan specifies how missing responses and employees changing stores will be handled. OutcomeThe revised design produces data that are less intrusive but more closely aligned with the research question. Participants report greater confidence in the study, and managers receive interpretable aggregate findings without access to individual employee profiles. The study cannot answer every possible question about employee behavior, but it provides stronger ethical and methodological foundations for the questions it does address. Learning PointsThe case illustrates that data minimization can improve, rather than reduce, research quality. It also demonstrates that consent, database architecture, aggregation, access controls, and analysis plans must be designed together. A technically possible variable is not automatically a scientifically necessary or ethically acceptable variable. Challenges, Limitations, and Common MistakesDigital collection can amplify selection bias. People without reliable internet access, compatible devices, digital literacy, or willingness to be monitored may be underrepresented. Automated systems can also produce false precision: a timestamp with milliseconds does not make the underlying behavior accurate. Common mistakes include using convenience samples without acknowledging their limits; changing survey questions mid-study without version control; joining datasets on unstable identifiers; treating “unknown” as zero; overwriting raw files; storing credentials in code; scraping without considering expectations of privacy; assuming de-identification is irreversible; and allowing dashboards to expose small subgroups. Automation creates operational risk as well. APIs may change, sensors may fail, and scheduled jobs may run twice. A pipeline should be idempotent where possible, meaning that rerunning the same process does not create duplicate records. Monitoring should detect unusual record counts, schema changes, delays, and authentication failures. Database normalization may produce many joins and affect performance, while denormalization may create inconsistent copies. These are engineering trade-offs, not ideological choices. The appropriate design depends on workload, analytical purpose, update frequency, and governance requirements. Emerging DevelopmentsModern collection systems increasingly use edge computing, privacy-enhancing technologies, synthetic data, automated entity resolution, and machine-learning-assisted quality checks. Edge processing can reduce the transfer of sensitive raw data by converting it into lower-risk summaries near the source. Differential privacy and secure multiparty computation may support analysis while reducing exposure, although they introduce technical complexity and can affect statistical utility. Generative AI can assist with schema documentation, code drafting, anomaly explanation, and instrument review. It can also invent plausible but incorrect transformations, expose confidential data through insecure prompts, or reproduce discriminatory assumptions. AI-generated code and classifications require human review, testing, provenance, and explicit accountability. A model should not be allowed to make unreviewed decisions about participant eligibility, consent validity, or disclosure risk. Data spaces and interoperable standards are encouraging organizations to exchange data through common definitions rather than isolated files. At the same time, the expansion of connected devices and automated decision systems makes governance more important. The doctoral researcher’s role is therefore not merely to use new tools, but to evaluate whether their epistemic benefits justify their risks and whether their outputs remain interpretable and contestable. Best Practices for Doctoral Researchers and ManagersA high-quality computer-assisted data project should: - begin with a clearly bounded research purpose;
- define constructs, units, populations, and measures before selecting tools;
- document consent, lawful basis, risks, and participant communications;
- collect the minimum information necessary;
- preserve raw data while separating it from processed releases;
- use stable identifiers and maintain a secure linkage key;
- create a complete data dictionary and versioned metadata;
- validate data at entry, transfer, transformation, and analysis stages;
- test APIs, scrapers, sensors, and survey logic before deployment;
- monitor missingness, duplicates, drift, failures, and unusual values;
- apply least-privilege access, encryption, backups, and audit logs;
- make cleaning and transformation reproducible;
- disclose limitations, uncertainty, and sampling bias;
- review re-identification and group harms before sharing results; and
- establish retention, archival, incident-response, and deletion procedures.
Chapter SummaryComputer-assisted data collection expands the scale and speed of research but does not replace methodological judgment. Surveys, experiments, APIs, web-scraping systems, and sensors must be designed around research questions, valid measures, appropriate populations, and ethical safeguards. Database management is integral to research quality because identifiers, schemas, metadata, missing-value rules, access controls, and transformation histories shape what the data mean. Relational databases support structured entities, keys, constraints, and SQL operations, while non-relational systems are useful for documents, graphs, and high-volume or variable data. Both require explicit definitions and governance. Data dictionaries, provenance, interoperability, validation, quality-control plans, and reproducible pipelines protect the integrity of evidence. Ethical practice requires minimization, transparency, privacy protection, security, accountability, and sensitivity to power relationships. Emerging technologies such as edge processing, privacy-enhancing computation, and AI offer valuable capabilities but introduce new risks that require critical evaluation. Key TermsAPI: A structured interface allowing software systems to request and exchange data or services. Data dictionary: A formal description of dataset fields, definitions, types, units, codes, and permitted values. Data provenance: A record of data origin, processing history, transformations, and custodial responsibility. Data minimization: Collecting and retaining only the information necessary for a legitimate purpose. Entity integrity: The requirement that each relational-table primary key be unique and non-null. Foreign key: A field that refers to a key in another table and supports relationships between records. Interoperability: The capacity of systems to exchange and meaningfully use information. Normalization: Organizing relational data to reduce redundancy and update anomalies. Non-relational database: A database model using structures such as documents, graphs, key-value pairs, or time series rather than conventional tables alone. Paradata: Information about the process of data collection, such as completion time, device, or navigation behavior. Primary key: A unique identifier for a record in a relational table. Pseudonymization: Replacing direct identifiers with coded identifiers while retaining a separate possibility of linkage. Referential integrity: The requirement that foreign-key values correspond to valid records. Schema: The formal structure, fields, data types, and relationships of a dataset or database. Sensor data: Observations generated by instruments that measure physical, behavioral, or environmental conditions. SQL: Structured Query Language used to define, retrieve, manipulate, and audit relational data. Validation rule: A condition used to detect or prevent values that are missing, invalid, inconsistent, or outside permitted limits. Web-scraping: Automated extraction of information from websites or other online sources. Review QuestionsShort Answer Questions1. Why should computer-assisted data collection begin with a research question rather than a software platform? 2. Distinguish accuracy, validity, completeness, and timeliness as dimensions of data quality. 3. What purposes do primary keys and foreign keys serve in a relational database? 4. Why is public accessibility insufficient to establish that web-scraping is ethically acceptable? 5. What information should normally be included in a data dictionary? Long Answer Questions1. Explain how a researcher should design and pilot an ethical computer-assisted survey. 2. Compare relational and non-relational database designs, including the conditions under which each may be appropriate. 3. Describe an end-to-end API data pipeline and identify quality-control risks at each stage. 4. Discuss the ethical and methodological challenges of sensor-based research involving employees. 5. Explain how provenance, version control, validation, and reproducible cleaning contribute to research credibility. Analytical / Application Questions1. A researcher combines survey responses, payroll records, and location data using employee names and dates of birth. Analyze the methodological, privacy, and database risks and propose a safer linkage design. 2. An API pipeline suddenly retrieves 40 percent fewer records, but the software reports no error. Develop an investigation and response plan using provenance, monitoring, validation, and version control. 3. Design an ethical data architecture for a study examining whether flexible work arrangements influence employee well-being. Specify the measures, collection channels, identifiers, access controls, retention approach, and likely limitations. 22. Multiple Choice Questions with AnswersQuestion 1Which design decision most directly supports both data minimization and ethical validity in the Northbridge Retail case? A. Collecting continuous location histories from all employees B. Replacing detailed location events with necessary aggregate scheduling indicators C. Giving supervisors access to individual survey responses D. Making wearable participation compulsory Correct Answer: B. Replacing detailed location events with necessary aggregate scheduling indicators Question 2What is the principal function of a foreign key in a relational database? A. To encrypt a database table B. To identify the newest record C. To connect a record to a related record in another table D. To replace all missing values Correct Answer: C. To connect a record to a related record in another table Question 3A researcher wants to preserve reproducibility when collecting API data. Which practice is most appropriate? A. Retaining only the final cleaned spreadsheet B. Recording endpoint parameters, retrieval time, response version, and transformations C. Allowing credentials to remain in publicly shared code D. Overwriting earlier extracts whenever new data arrive Correct Answer: B. Recording endpoint parameters, retrieval time, response version, and transformations Question 4Why can a digitally recorded sensor value not automatically be treated as an objective fact? A. Sensors never produce numerical data B. Every sensor observation is affected by device conditions, calibration, and measurement error C. Sensor data cannot be stored in databases D. Sensor data are always intentionally fabricated Correct Answer: B. Every sensor observation is affected by device conditions, calibration, and measurement error Question 5Which example best illustrates semantic interoperability rather than merely syntactic interoperability? A. Two systems both export comma-separated files B. Two systems use the same network protocol C. Two systems agree that the term “customer” represents the same underlying population D. Two systems store dates in different formats Correct Answer: C. Two systems agree that the term “customer” represents the same underlying population Question 6A survey requires an answer to every sensitive question and does not offer a refusal option. What is the main ethical concern? A. The survey will necessarily have a larger sample B. The requirement may undermine voluntariness and increase pressure to disclose C. The database will automatically become non-relational D. The survey cannot use skip logic Correct Answer: B. The requirement may undermine voluntariness and increase pressure to disclose Question 7Which quality-control action is primarily preventive? A. Investigating an anomaly after publication B. Comparing final results with an external benchmark C. Applying schema constraints and permitted-value checks during data entry D. Writing a post hoc explanation of missing records Correct Answer: C. Applying schema constraints and permitted-value checks during data entry Question 8What is the main risk of treating all blank values as zero? A. It guarantees referential integrity B. It may confuse nonresponse, inapplicability, unknown values, and genuine zero values C. It improves construct validity in every study D. It prevents duplicate records Correct Answer: B. It may confuse nonresponse, inapplicability, unknown values, and genuine zero values Question 9Which practice best protects the identity key in a pseudonymized research dataset? A. Storing it in the same public file as the research data B. Publishing it with the data dictionary C. Storing it separately with restricted access D. Replacing it with participants’ names Correct Answer: C. Storing it separately with restricted access Question 10A web scraper silently begins collecting promotional text instead of product prices after a website redesign. Which control would most likely detect the problem? A. Increasing the scraping speed B. Removing retrieval dates from the logs C. Using schema and content validation tests with failure alerts D. Deleting the original source URLs Correct Answer: C. Using schema and content validation tests with failure alerts
|