Entity and Sentiment Analysis with the Natural Language API Reviews

Subhan A. · Reviewed over 1 year ago

Bilal M. · Reviewed over 1 year ago

Dilnaz S. · Reviewed over 1 year ago

Damir I. · Reviewed over 1 year ago

Sagar S. · Reviewed over 1 year ago

Mohsin A. · Reviewed over 1 year ago

Muhammad Ahmad M. · Reviewed over 1 year ago

Alansary E. · Reviewed over 1 year ago

sajitha S. · Reviewed over 1 year ago

Kyle K. · Reviewed over 1 year ago

Aman B. · Reviewed over 1 year ago

Dhrumit D. · Reviewed over 1 year ago

Reason for a 1-Star Rating for the Lab: Inconsistent API Behavior: The API key worked initially, but subsequent requests returned 403 "PERMISSION_DENIED" errors. The lab instructions do not clarify that API keys may not work for this request, leading to wasted time troubleshooting. Lack of Proper Documentation on Authentication: The lab should explicitly mention that Google Cloud APIs sometimes require OAuth authentication instead of API keys. A fallback authentication method (such as using gcloud auth application-default login) should be included in the instructions. Training Environment Issues: It’s unclear if rate limits, session restrictions, or other security policies are affecting the API key. The lab does not mention if temporary training accounts have API limitations, causing confusion. Time Wasted Due to Missing Context: Without a proper explanation of API authentication options, users are left to debug API errors instead of learning the intended concepts. Suggested Fixes: ✔ Clearly state in the lab that some APIs require OAuth authentication instead of an API key. ✔ Provide a troubleshooting section for common API issues, including "Method doesn't allow unregistered callers" errors. ✔ Mention Google Cloud's API quota restrictions for training environments and how to work around them.

Nicholas R. · Reviewed over 1 year ago

Reason for a 1-Star Rating for the Lab: Inconsistent API Behavior: The API key worked initially, but subsequent requests returned 403 "PERMISSION_DENIED" errors. The lab instructions do not clarify that API keys may not work for this request, leading to wasted time troubleshooting. Lack of Proper Documentation on Authentication: The lab should explicitly mention that Google Cloud APIs sometimes require OAuth authentication instead of API keys. A fallback authentication method (such as using gcloud auth application-default login) should be included in the instructions. Training Environment Issues: It’s unclear if rate limits, session restrictions, or other security policies are affecting the API key. The lab does not mention if temporary training accounts have API limitations, causing confusion. Time Wasted Due to Missing Context: Without a proper explanation of API authentication options, users are left to debug API errors instead of learning the intended concepts. Suggested Fixes: ✔ Clearly state in the lab that some APIs require OAuth authentication instead of an API key. ✔ Provide a troubleshooting section for common API issues, including "Method doesn't allow unregistered callers" errors. ✔ Mention Google Cloud's API quota restrictions for training environments and how to work around them.

Nicholas R. · Reviewed over 1 year ago

Sameer P. · Reviewed over 1 year ago

Rammohan D. · Reviewed over 1 year ago

たかおみ G. · Reviewed over 1 year ago

really great

Jason R. · Reviewed over 1 year ago

Shivam Y. · Reviewed over 1 year ago

Aaron T. · Reviewed over 1 year ago

Dhanvada, L. · Reviewed over 1 year ago

Peter F. · Reviewed over 1 year ago

Parth M. · Reviewed over 1 year ago

Vaibhav J. · Reviewed over 1 year ago

Gustavo N. · Reviewed over 1 year ago