factsmission / twee-fi-aggregator

3 stars 2 forks source link

Data interfacing with datacommons #6

Open MartinoMensio opened 4 years ago

MartinoMensio commented 4 years ago

I was wondering if, with the huge quantity of claimReview available at DataCommons it would be possible to filter the ones whose itemReviewed.firstAppearance / itemReviewed.appearance is a Tweet. Or would it be better that the fact-checker themselves create a Solid account where they have the reviews stored?

retog commented 4 years ago

That sound likean intersting approach to provide the aggregation needed for the twee-fi client. I think the reviewers would still need a solid account for publishing, but could we then trigger google's aggregation to DataCommons?

MartinoMensio commented 4 years ago

So you see it more as twee-fi pushing data to DataCommons instead of pulling the ClaimReviews?

As far as I've understood, in order to push to Google Fact-Check Tools (and therefore the DataCommons feed), the steps are the following:

  1. be authorised for the website (would be the twee-fi website property) through Google Search Console: https://toolbox.google.com/factcheck/about#fcmt-creators
  2. Use the API to create / update (to keep in sync when the reviews are modified): https://developers.google.com/fact-check/tools/api/reference/rest/v1alpha1/pages/create . The fields of the existent ClaimReview have just to be put in the request body.

I played a bit with the MarkupToop, which is a simpler interface to create the reviews on Google Fact-Check Tools (instead of using the APIs), and after some days I saw my ClaimReview in the Datacommons Feeds. So the process should be quite straightforward.