aboutcode-org
Drill down from package to package details
When a package is in DejaCode and has been furthered scanned, or is in the purldb I would like to drill down aka. navigate to its scan details either in ScanCode.io or the PurlDB. In particular I would like to see details about license detection results (and scores), license clarity scores and navigate to the resource details
The challenge here is providing the DejaCode (app1) user a way to reach the ScanCode.io UI (app2) while not having a user account there. Some solutions may include using "JSON Web Token" like approach to provide temporary user access to the ScanCode.io app, limited to a single Project context.
@tdruez I reckon the difficulty, but you are making a specific assumption that we would open the web pages of the SCIO instance separately.
Instead what about these:
- the SCIO web pages could be fetched remotely an integrated in the web pages of DejaCode,
- or the API from SCIO could be called by DJCD to retrieve the data that matters and display that in DejaCode
This is going to be critical to help curate and review scans in details. @DennisClark what do you think?
I think that the @tdruez suggestion "Some solutions may include using "JSON Web Token" like approach to provide temporary user access to the ScanCode.io app, limited to a single Project context." actually makes a lot of sense, rather than introducing a lot of redundant info/details in DejaCode. That's my initial reaction anyway, since I'm not very clear on DejaCode retrieving "the data that matters".
on the other hand, regarding "the data that matters", there are some data bits that we need to consider for DejaCode, as described in these issues (and others too probably):
- https://github.com/nexB/dejacode/issues/11
- https://github.com/nexB/dejacode/issues/41
the SCIO web pages could be fetched remotely an integrated in the web pages of DejaCode,
Not that simple as the page is not only a plain HTML file but has many external dependencies. Also all the links and navigation would have to be somehow rewrited, sounds like a mess.
or the API from SCIO could be called by DJCD to retrieve the data that matters and display that in DejaCode
Depending on which data we want to display, that may results in a lot of code duplication. If we are limiting the scope to only Package details, that may be ok. But it looks like we need multiple views: "In particular I would like to see details about license detection results (and scores), license clarity scores and navigate to the resource details"