Solve KeyError Issues

[AyanSinhaMahapatra]

Solves issue - #3
Adds schema assertion, only allowing Scancode 3.2.2 and extracts other info
from path and saves to file. Also handles keyerror arising from packages
with zero license detections. Modifies .ipynb files to reflect changes.

Signed-off-by: Ayan Sinha Mahapatra ayansmahapatra@gmail.com

[AyanSinhaMahapatra]

So These KeyErrors came from two issues,

1. A lot of these scans (the database dump provided by @MaJuRG) was performed by older scancode versions, so they have very different schema, resulting in KeyErrors. Counts of Different Schema which were there out of 4099 package scans -

2.10.2.json     191
2.2.1.json        1
2.9.1.json       10
2.9.2.json      171
3.1.2.json        1
3.2.2.json     3725

Out of all these only, the 3.2.2 is kept, others dropped, as @pombredanne suggested in Gitter chat.

that's OK to ignore any scancode version before 3.0.x ... this is too old

2. Some packages don't have any license information in any of the files, so this not accounted for, and was creating some KeyErrors, as all rows were deleted in DataFrames.

Also, all .ipynb files have been updated, and can be run in Google Colab.

[steven-esser]

@AyanSinhaMahapatra I think this is ready to merge, no?

[AyanSinhaMahapatra]

@MaJuRG Yes!