I ran a load_inventory Project with 25 Devel codebase JSON Scans created with SCTK 32.3.0 (SCIO v34.9.3). These are small repos so it will be a lot of extra work to use 25 separate projects.
The key problem is that SCIO appears to be truncating/ignoring the first segment of the Resource path that is visible in the JSON data. For example path = python-lambdas/lambda_function.py from the JSON input is reported as just: lambda_function.py in the SCIO data.
In the case where the name for the first segment of the path from SCTK matches the name for JSON input file (repo) level it would be sufficient to just keep that full path, but there are likely other cases where we need to prepend the input Scan file name to the path.
Without the full path we will likely have the UberJAR problem that we will only keep report one Resource for common files like LICENSE or README that appear in many repos for a Devel Codebase.
I ran a load_inventory Project with 25 Devel codebase JSON Scans created with SCTK 32.3.0 (SCIO v34.9.3). These are small repos so it will be a lot of extra work to use 25 separate projects.
The key problem is that SCIO appears to be truncating/ignoring the first segment of the Resource path that is visible in the JSON data. For example path = python-lambdas/lambda_function.py from the JSON input is reported as just: lambda_function.py in the SCIO data.
In the case where the name for the first segment of the path from SCTK matches the name for JSON input file (repo) level it would be sufficient to just keep that full path, but there are likely other cases where we need to prepend the input Scan file name to the path.
Without the full path we will likely have the UberJAR problem that we will only keep report one Resource for common files like LICENSE or README that appear in many repos for a Devel Codebase.