Hi, I'm an employee at Orchestr8 and we make natural language processing software.
We have created this module for the Tagging module that will suggest tags based on the content of the post using our technology.
To enable the module's access to the web-based REST service, you need an apikey that is free at alchemyapi.com.
The module is attached. Let me know if there are any improvements we can make to it.
Thanks!
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | tagging_alchemy_suggest.zip | 6.77 KB | shaun_roach |
| tagging_alchemy_suggest.zip | 6.78 KB | shaun_roach |
Comments
Comment #1
eugenmayer commentedAlchemyAPI_ParseEntityResponse / AlchemyAPI_ParseKeywordResponse
please make those two methods namespace-aware, so tagging_alchemy_suggest_*
---
dependencies[] = taxonomy
Not needed, when you depend on tagging. I would not double this :)
--
General: Thank you very much for the contribution, very nice work!
Comment #2
shaun_roach commentedGreat, I made the changes you suggested and the new files are attached.
Thanks for reviewing this.
Shaun
Comment #3
eugenmayer commentedLooks great - scope for the 2.2 release. Thank you a lot
Comment #4
eugenmayer commentedwill be in 2.2.
Be sure to look at the coding styles, big parts of the code were pretty messy :/
Comment #5
eugenmayer commentedreleased in 2.2
Comment #6
eugenmayer commentedreleased in 2.2
Comment #7
shaun_roach commentedSorry about the messy code, I'll look at the coding styles now.
Comment #8
eugenmayer commentedComment #9
mikerasmussen commentedI keep getting "AlchemyAPI needs key to work. see README" but I have put the key in the .txt file, and even tried inserting it directly in the code. Thoughts?
Comment #10
eugenmayer commentedOpen a new issue please.