We understand that there have been several small changes and inconsistencies between the xml, flat format and the structure guide for outbound tickets and that is has been causing delays in testing. For that we apologize.
Last night, the development team went through, line by line, and resolved any remaining inconsistencies between formats and outputs.
NOTE: There is an inconsistency with the 'seconds' output between the xml and readable text format (showing zeroes) that will be resolved on Monday, Oct. 22)
NOTE: It is possible that there may be one additional field added to the output before launch
(Original Ticket Number). This is dependent on the solution for Corrections, and whether they can keep the same ticket number. Not yet resolved.
Attached below are
WC Data Structure Guide: an Excel document that defines each line of output for both the text (readable) format and the xml format.
Readable Text body email: Sample of the readable text that will be in the body of the email. (NOTE: This text should appear in the body of all outbound ticket emails after Monday, Oct. 22)
onecall.xsd: The schema for programming xml tickets into parsing systems. NOTE: Once we are in production environment, this file will be accessed for each ticket from a link within the xml file itself. (-<onecall:OneCallReferral xsi:schemaLocation="https://www.pelicancorp.com/onecall/bydp.xsd" xmlns:onecall="http://www.pelicancorp.com/onecall" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink">)
This file is provided for system configuration, but ticket management systems should resolve the xml schema directly from the link once we are live, therefore ensuring that the most current schema is always available.
20184200087.xml: Sample of an xml ticket output
20184200087.gif: Sample image file that will be attached to all outbound tickets - screenshot of the dig site polygon drawn by the User.
20184200087.gml: Sample gml file that will be attached to all outbound tickets. This is a geo-data file containing the actual polygon drawn by the User. It is meant to be pulled into mapping software to lay the polygon over member facility maps for comparison/screening purposes. This file is spatially accurate, based on your map projection information. Members using the gml file will have to provide BYPD with preferred projection.
20184200087.pdf: Sample of PDF attachment to be sent with all outbound ticket formats.
NOTE: the statement/advisory sections of the PDF are not final, but the ticket output fields are.