Datascope

Datascope

Datascope is a digital forms and surveys platform for field data collection. Teams use it to replace paper forms with mobile-friendly digital checklists, inspections, audits, and surveys — capturing structured data with photos, GPS coordinates, and signatures from the field.

Data Model

• Forms → Answers: Forms are the templates; answers are submitted responses with responder identity, timestamps, and optional attachments (photos, signatures). Use flat answer exports for analytics tables; use metadata-enriched exports when you need question types, section labels, and subform indices.
• Metadata Lists → List Items: Lists are reusable dropdown/choice definitions (product SKUs, branch offices, equipment types). List items are the individual elements within a list. Lists come in three types: standard, percent, and price. These are NOT form submissions — they are lookup tables that populate form fields.
• Locations: Physical sites or geographic points associated with forms (warehouses, branches, inspection sites). Each location has name, address, GPS coordinates, and parent company info. Used for geo-tagging and site-based filtering of form submissions.
• Notifications: Alert records tied to form events. Each notification has a type (PDF or Excel), URL to the generated file, form reference, and timestamp.
• Files: Generated PDF or Excel exports from form submissions. Similar to notifications but specifically for file downloads.
• Task Assignments: Scheduled form inspections assigned to specific users at specific locations with deadlines. Track completion status, timing, and on-time performance.
• Tickets (Findings): Issues discovered during form inspections with priority (low/medium/high/critical), status (open/in_progress/paused/closed), assignees, and linked form answers.

Pagination

Large answer feeds, metadata lists, notifications, and assignments page with offset/limit; default window sizes differ by dataset (answers/notifications skew larger per page than task assignments).

Date windows

Answers and ticket queries cap how far back you can span in one call (order ~90 days). Wider studies need multiple windows.

Gotchas

• Answers vs metadata lists: Answers are live submissions; metadata lists are reusable choice tables—never treat a list export as field responses.
• Locations are NOT forms: Locations are sites where capture happens, not form blueprints.
• Payload shapes: A few read tools return bare arrays; most wrap objects—inspect the first row before assuming structure.
• Ticket dates use DD-MM-YYYY; assignment dates use YYYY-MM-DD.
• Task assign user_id is an email-shaped identifier, not a numeric worker id.