Hi, Oh, there are two main data inputs both queried from the SW heritage REST API:
1. If a file is there: FOSSology passes a hash of the file to the API server and then the server responds if the file is there 2. Some metadata about the file: in this case we have picked license information from SW Heritage's own license scanning. It is redundant, if you did the fossology scan on your server already. but we felt it could be extended in future with more metadata once the API is offering this (for example, we would find inetresting in which project(s) or URL locations the file was found) Redundant: the SW Heritage license results are processed in the FOSSology as an agent, so it is similar to having nomos and monk reporting license findings ... Will have a look at the wiki to clarify it. Kind regards, Michael > On 16. Jun 2020, at 18:20, Matija Šuklje <mat...@suklje.name> wrote: > > Die 16. 06. 20 et hora 11:15 Matija Šuklje scripsit: >> Especially thanks to Shaheem for working on this! > > I apologise, I misread the GSoC page. Thank you Sandip for working on this! > Of > course, kudos to Shaheem and Michael for mentoring. > > Now that I managed to run it, it seems it works, but I can’t figure out where > it gets the data from (from SwHeritage’s own FOSSology scanning?). I couldn’t > find any useful documentation unfortunately either… > > > cheers, > Matija > -- > gsm: tel:+386.41.849.552 > www: https://matija.suklje.name > xmpp: matija.suk...@gabbler.org > sip: matija_suk...@ippi.fr > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#3373): https://lists.fossology.org/g/fossology/message/3373 Mute This Topic: https://lists.fossology.org/mt/74912707/21656 Group Owner: fossology+ow...@lists.fossology.org Unsubscribe: https://lists.fossology.org/g/fossology/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
