SCWB shows error for missing 'type' info when it's present in the json file

[johnmhoran]

Running the latest release on Windows 10, after running a no-flag scan (not even -i), I tried to import the .json output file and convert to .sqlite and encountered the following error message:

However, both the json and csv output files contain an instantiated type column (with file and directory values).

[steven-esser]

@johnmhoran You need to run -i at the very least in order for it to work with scancode-workbench.

Running a scancode scan with no flags currently does not include a -i info scan.

[steven-esser]

The type it is referring to is actually the file_type attribute in a scan.

Alternatively, we may be able to get away with accepting limited scans without an -i option. I do not think there is a reason to have a dependency on fileinfo information, especially as scancode-toolkit does not run it by default anyway.

[johnmhoran]

Thanks @MaJuRG . 👍

[mjherzog]

I would find it useful to be able to use the Tree and Table Views with just the Resource Path and (Resource) type data - esp. for large scan datasets. This would help with the Catch-22 case to get a very basic scan for large codebases where a --info scan may be hard to use in WB.

I would argue that the current error message is a bug since the scan in question has the type column. Updating WB to handle this type of file would be an enhancement that can be deferred a bit if it is difficult since the CSV file is easy enough to use in this context.

[steven-esser]

#387 merged with the fix. Closing this.