1. P4 Tagging Software and MRR Data Model Preview John Tenney, Nicole Tancreto and Craig White Pacific States Marine Fisheries Commission A Presentation for the 2015 PIT Tag Workshop

2. Overview P4: Next-Generation Tagging Software Compatible P3 Replacement Beta version later this year Enhanced MRR Data Model

3. What is the MRR Data Model? MRR: Mark, Recapture, Recovery Events Mark: fish tagged and released Recapture: subsequent handling/release of tagged fish Recovery: report mortality of tagged fish Data Model: fields, relationships and validation Regional Standards Consistent data spanning 27 years Goal: enhance data model + maintain data consistency and integrity

4. Background: P3 Tag Session and Tagging File Header Detail

5. Tagging File Format and Support Continue support for legacy tagging file Upload via P3 and Email Enhanced MRR data model not supported Import into P4 P4: new file format and upload features Improve feedback Specifications to be published

6. Proposed MRR Field Enhancements Event Type Values: Mark, Recapture, Recovery, (other) Related Conditional Comment Flags optional (RE, M) Tag Date => Event Date; Tag Site => Event Site Event Date and Release Date include time zone offset Dates entered in local time Converted to PST in PTAGIS Coordinator ID now Tag Data [Project ID] Identify individual or long term research project Data can transition between contacts over time History of contacts maintained

7. Proposed MRR Field Enhancements Optional Lat/Long Coordinate for Release Location Complimentary with River KM (RKM) Associate codes of other tag types CWT, Acoustic, Genetic, Radio Other Requested Fields BPA FWP Project Number Life Stage Gender Spawn Year Tag Type Project/User Defined

8. Advantages of P4 using Enhanced MRR Data Model Compatible with existing data collection and reporting P4 Tag Session can contain > 9,999 records Multiple MRR events for same tag e.g. Mark + Recapture records for 3D9.1BF1234568 MRR Events spanning multiple days and locations Each MRR event record owns a copy of header fields Global (header) fields in Tag Session limited to: Project ID, Session Message and Session Note

9. P4 Application Fundamentals

10. P4 Configuration Features

11. P4 Validation Code Management

12. P4 Configuration Features

13. P4 Configuration Tools

14. P4 Configuration Profile: Devices

15. P4 Configuration Profile: Device Test Terminal

16. P4 Configuration Profile: Devices

17. P4 Configuration Profile: Validation Constraints

18. P4 Configuration Profile: Sound Alerts

19. P4 Templates

20. Editing a Template: Customized Data Entry Layout

21. Editing a Template: Default Values

23. P4 Tag Actions

24. Editing a Tag Action

25. Other P4 Configuration Features

26. P4 Data Entry Features

28. P4 Data Entry Example

29. P4 Session Information

30. P4 Default Values

31. P4 Data Entry View

32. P4 Data Management

33. P4 Data Management Features

34. Conclusion Feedback is vital to success of P4 Recommend Online Forums at www.ptagis.orgwww.ptagis.org Identify workgroup to evaluate P4 beta Live training events TBD Feature Rollout

35. Background: Tagging Software Survey Summary

36. Tagging Software Survey Summary

43. Tagging Survey Summary of Feedback: Workflow issues: 30% Consolidate tag data files: 25% Project-Defined fields 17% Spatial Needs: 15% Tablet Support: 15% No Changes Needed: 9% Measurement Changes: 7% Backwards Compatibility: 5% Exporting Format: 5% Device/Communication Needs: 5% Data Model Changes: 3%