3 ms·
> To avoid listening to all recordings myself, used Google Cloud Speech-to-Text to transcribe the recordings, and then used the transcriptions ... That's a lot
by h2odragon 5y ago
> To avoid listening to all recordings myself, used Google Cloud Speech-to-Text to transcribe the recordings, and then used the transcriptions
... That's a lot of trust to place in google. Do all this work to gather data, then throw it away and analyze what google did to the data instead.
- iamgopal 5y agoThe amount of way google could have data, this is just peanuts.
- turminal 5y agoAll your data are belong to us!
- deleted 5y ago[deleted]
- JCBird1012 5y agoTo be fair, most of the original recordings (with caveats listed there) were linked at the bottom, so I presume that the author still has them around - that's hardly "throwing" them away. I don't think the goal of using Google speech-to-text was to solely use the transcriptions for the rest of the project, but you've gotta find some way to sift through those recordings and pull out the interesting bits. I think that was the right choice providing additional context and picking out the good stuff. Imagine having to listen to ~28 hours of recordings (60 sec * 1724 answered calls) when there's a service that can easily turn those recordings into a more easily consumable format, and then you can go back and listen to the neat stuff.
- h2odragon 5y agoExcellent points. Still, it puts a lot of trust in the service, the analysis is of their results not the original data. Furthermore, it feels like cheating, dammit. We dialed half of an area code in a full a week back when, and didn't even have the luxury of recording equipment.