The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here
"Enrich Data by Webservice with HTTP Header"
In the tutorial 'RapidMiner to enrich Gender data', the API does not require authentication:
http://namesorts.com/2014/04/23/rapidminer-to-enrich-gender-data/
But (say you would like to use Mashape or some other auth method) how do you specify an API Key HTTP Header in the RapidMiner Webservice operator?
Thanks!
Elian
http://namesorts.com/2014/04/23/rapidminer-to-enrich-gender-data/
But (say you would like to use Mashape or some other auth method) how do you specify an API Key HTTP Header in the RapidMiner Webservice operator?
Thanks!
Elian
Tagged:
0
Answers
I found the same/similar question on StackExchange and I wrote a question (specific to mashape) on this forum but no answer yet..
I'm now trying to pass OAuth parameters to the Twitter API but had no luck in passing the right header format despite various different attempts
HaHaHaHa
You no longer need to worry about HTTP headers, as you can now use NamSor Onomastics Extension (from RapidMiner MarketPlace). Tutorial here
http://blog.namsor.com/2014/09/10/video-tutorial-how-to-extract-the-gender-of-personal-names-using-rapidminer/
There are currently two operators,
Gender : to infer the likely gender of a personal name;
Origin : to infer the likely origin of a personal name.
Best,
Elian