Manually ported from Syna3C/Syna3C-Project where @shonore commented on Jun 24:
Natural Language Processing (NLP) - We need to present what NLP is to Amelia and other stakeholders. In addition, we should discuss the costs, risks, development time, and, production support efforts of using this technology.
@Revencher replied on Jun 26:
I Googled it real quick. I can see how it would be useful but wonder if it's necessary or prudent for the alpha?
If you feel it is necessary for the basic functions of this program then by all means do what you feel is necessary, unless anyone has an objection?
@maeutic responded with possible solutions on Jun 30:
CoreNLP-client (GitHub site) is a simple corenlp client to the corenlp http server using request-promise by Romain Beaumont. Extended by Christophe B. for multilingual use as corenlp-client-multilang (github site). The latter has multilingual support.
pynlp A (Pythonic) Python wrapper for Stanford CoreNLP by Sina. PyPI page.
NLTK since version 3.2.3 has a new interface to Stanford CoreNLP using the StanfordCoreNLPServer. Among other places, see instructions on using the dependency parser and the code for this module, and if you poke around the documentation, you can find equivalent interfaces to other CoreNLP components; for example here is Stanford CoreNLP NER. Much of the work for this was done by Dmitrijs Milajevs.
https://github.com/spencermountain/compromise (javascript; looks lightweight; dev links to some other NLP projects, which I've included below if applicable and not linked elsewhere)
We are going to do more research on this. Amelia is going to find open source solutions for this. The purpose of implementing this technology is to reduce duplicate events/sub-events/posts from being created and to automatically generate tags based on the information entered when a post is created or edited. Tags may be used as a filter for searches.
@shonore commented on Jul 14:
The NPL is going to be implemented on the server so it does not have to be compatible with React. We will revisit this once we flesh out the website more
Manually ported from Syna3C/Syna3C-Project where @shonore commented on Jun 24:
@Revencher replied on Jun 26:
@maeutic responded with possible solutions on Jun 30:
@shonore added on Jun 30:
@shonore commented on Jul 14: