-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate standard JSON files from SCIO-DB #45
Comments
Signed-off-by: Thomas Druez <tdruez@nexb.com>
Signed-off-by: Thomas Druez <tdruez@nexb.com>
Signed-off-by: Thomas Druez <tdruez@nexb.com>
@mjherzog Those JSON results are already available and can be generated/gathered from the following places:
Notes: The JSON file content is standard ScanCode format and is fully compatible with ScanCode Workbench. The |
https://docs.djangoproject.com/en/3.1/ref/models/querysets/#prefetch-related > Note that if you use iterator() to run the query, prefetch_related() calls will be ignored since these two optimizations do not make sense together. Signed-off-by: Thomas Druez <tdruez@nexb.com>
This is the preferred method to craft outputs filename for consistency. The current date and time string is included in the filename. Signed-off-by: Thomas Druez <tdruez@nexb.com>
Signed-off-by: Thomas Druez <tdruez@nexb.com>
When you use ScanPipe to analyze a codebase and load the Scan data into the SCIO-DB, you should also be able to extract the Scan data from the SCIO-DB according to any combination of the basic ScanCode runtime parameters:
--info
--copyright
--license
--package
--email
--url
The primary output format should be standard SCTK JSON.
I am not sure what we should put in the output file header, but we would at least want to know what version of SCTK was used for the original Scan. In any case this JSON file must be compatible with ScanCode Workbench since the primary use case is to view Scan data there.
The text was updated successfully, but these errors were encountered: