Re: Schedules Direct AU and NZ data offering

On Sat, Aug 27, 2016 at 10:19 PM, Kevin Groeneveld
<[email protected]> wrote:

> One thing I did notice is that some programs don't seem to include an
> entityType field which I have never seen before.  This triggers a perl
> warning in my grabber but doesn't stop it from working.  I should maybe
> handle this case more explicitly.

As the Schedules Direct JSON data definition specifies
"entityType: string. Mandatory" that sounds like another
(source) data issue(*).  I (privately) reported another case
of a mandatory field (the md5) not existing in an example
that was identified/fixed almost as soon as I reported it
(maybe before I reported it?), which was apparently due
to some race conditions in data creation.

The joys of data in-gestation from disparate sources.


(*) I would assert that if a mandatory field is missing
that a program is allowed to behave "differently", and
claim "It is not my fault!".  Of course, handling bad data
is always a plus, but you can only test and handle so
many cases of challenged source data.

------------------------------------------------------------------------------