Documents / Report
This white paper, sponsored by the All-domain Anomaly Resolution Office and hosted with Associated Universities, Inc. and Florida State University, synthesizes a workshop held August 5 and 6, 2025, that brought together 40 participants. The workshop examined how to collect, standardize, link and analyze UAP narrative reports. It calls for standard metadata templates, human oversight of AI tools, triage of reports, preservation of historical records, better public reporting portals and further workshops.
6 analysis with the data collected, as well as potential improvement of the form. The discussion led to the following overarching suggestions that are broadly informative for online UAP reporting tools. 1. Intake flow and structure: • Begin with a free-text box (and optional audio upload) where the witness provides their account in their own words. Use AI-assisted extraction to propose structured fields, which the witness can then confirm or correct. • Frame questions around what was perceived (angular size, shape, movement, sound, effects) rather than presumed properties (exact distance, solid object dimensions). 2. Additions to the form: • Ask witnesses to explain how they estimated size, distance, or speed (i.e. context prompts). • Capture whether this has happened before and, if so, how often. • Instead of “mass sighting: yes/no”, include approximate numbers of witnesses. • Include a field for whether the object seemed to react to observer presence. • Add examples of technological effects (e.g., radio static, car failure) and basic prompts about feelings or aftereffects that could be informative (e.g., “Did you discuss this with others? Would you want professional/peer support?”). • Automatically ingest and display photo metadata (camera model, timestamp, location), giving users the option to redact sensitive fields. 3. Standardization and cleaning: • Accept location information including city/address/zip/lat–long, with simple guidance and drop-downs, and normalize on the back end. • Enforce a single-entry format for dates and times (calendar widget or drop-downs). • Allow multiple inputs for units (imperial/metric) but convert and store consistently. • Include structured numeric fields for object count and multiple objects, with adaptive follow-up to describe each object separately. 4. Taxonomical considerations: • Provide a concise taxonomy of common shapes (disk, sphere, triangle, cigar, “other”) but allow free-text for unusual forms. • Update descriptive references for cultural familiarity (using objects such as coins or debit card to estimate size) and internationalize/translate forms for broader accessibility. 5. Integration and linkage: • Include a field to indicate whether the event was reported elsewhere (NUFORC, MUFON, FAA, etc.).
Report, from the aaro collection. The PDF is mirrored here; the original link is above. 17 pages are in the text index: search them above, or from the library's search.