search

CityOfNewYork / CROL-Overview

City Record Online parsing libraries and supporting files
26 stars 14 forks source link

Create Consistent Parsing Error Messages #32

Closed cds-amal closed 9 years ago

cds-amal commented 9 years ago

For each record that fails to be parsed create an output that has:

  1. RequestID
  2. StartDate
  3. EndDate
  4. DueDate

@Mikael Should any other fields be included?

mikaelmh commented 9 years ago

This sounds good. This adds additional information that allows us to further pinpoint the issue. Will the attempted parsed field (eg. "AdditionalDescription") also be included in the output??

On Wed, Apr 1, 2015 at 5:15 AM, kiddle notifications@github.com wrote:

For each record that fails to be parsed create an output that has:

  1. RequestID
  2. StartDate
  3. EndDate
  4. DueDate

@Mikael Should any other fields be included?

Reply to this email directly or view it on GitHub: https://github.com/CityOfNewYork/CROL-PDF/issues/32

cds-amal commented 9 years ago

This will be addressed by our current workflow of developing json schema and data parser to document "what we have".