Step 1: We need the API for opencog and then integrate it into the rest of the system.
We have a working container for all of the functions:
gcr.io/collectiwise/flask-oc@sha256:24be2ed9ad1bb11e846894c3a1c7bcd51e1cb317313932c13bf53b8d632f603c
In the script that sets up the entire system, the above container should replace the container that we had before for opencog.
In the main function, each of those functions is tested and the order in which they are called and tested is important! I envision the main function as a basis for a test of the API.
Step 2: integrate this API with the rest of the system, including the React frontend.
Step 3: Integrate with the newest Jira.
I’m happy to do any of the non-Django python programming that’s needed!
Maybe Neville can fix the Solr stuff that still needs fixing?
Stage 6:
Step 1: We need the API for opencog and then integrate it into the rest of the system.
We have a working container for all of the functions: gcr.io/collectiwise/flask-oc@sha256:24be2ed9ad1bb11e846894c3a1c7bcd51e1cb317313932c13bf53b8d632f603c
In the script that sets up the entire system, the above container should replace the container that we had before for opencog.
The functions that should be exposed through the Django API are found here: https://github.com/CollectiWise/owlab/issues/3#issuecomment-570684234
Those are defined in this file, which is also found on the container; along with all of the dependencies: https://bitbucket.org/collectiwise/flask-oc/src/master/py2scheme.py
In the main function, each of those functions is tested and the order in which they are called and tested is important! I envision the main function as a basis for a test of the API.
Step 2: integrate this API with the rest of the system, including the React frontend.
Step 3: Integrate with the newest Jira.
I’m happy to do any of the non-Django python programming that’s needed!
Maybe Neville can fix the Solr stuff that still needs fixing?