Software Engineer
CurrentWork on document capture and routing server software. Customers include banks, law firms and hospitals. Implement code to enable the server to deliver documents to Dropbox, Box, GoogleDrive, FTP Sites, Sharepoint 2010/2013/365 and IBM FileNet. This expands the number of destinations our server is capable of delivering to, which allows us to meet the needs of more customers. FileNet in particular can be configured many ways. I had to work closely with the customer requesting this integration in order to provide all the features requested. At the same time, I had to make the solution general enough to be used and re-sold to other potential customers. Many new cloud based document management systems expose REST APIs to allow applications to store documents. In order to support delivery to these systems (such as Net Documents and OneDrive) I’ve needed to research the APIs and implement C# callable wrappers. Integral to this is learning how to implement OAUTH authentication for each service. A server application must implement authentication in such a way that a user needs only login once and the server can there-after use the services’ REST API without requiring further user interaction. In 2012, the United States court system stopped accepting normal PDFs for electronic document filings and would only take a form of PDF called PDFA. I researched the PDFA standard and used the Datalogics library to ensure that our server could create documents that conformed to this standard. Our numerous law firm customers could then submit documents to the court automatically. It was learned that PACER, the courts’ electronic document receiving system, was rejecting our (and other companies) PDFA documents. I worked with the court system of Pennsylvania to understand the problem. Without access to the code base, I determined that the problem lay in PACER, which had a number of bugs in the code used to verify the PDFA documents submitted to it.