qcri-social / AIDR

Artificial Intelligence for Digital Response
http://aidr.qcri.org/
GNU Affero General Public License v3.0
98 stars 37 forks source link

No items available in crisis type drop down #10

Closed ajgbangug closed 10 years ago

ajgbangug commented 10 years ago

I'm using version 1.1 of AIDR and I'm not able to create a collection because I can't enter a crisis type as there are no choices appearing. Here is a screenshot.

screen shot 2014-09-04 at 5 21 14 pm

imran15 commented 10 years ago

Crisis types come from aidr-tagger database using an API of aidr-tagger-api. You need to pupolate aidr-tagger schema using this script (https://github.com/qcri-social/AIDR/blob/master/aidr-tagger/src/main/scripts/populate_db_crisistypes.sql) and deploy aidr-tagger-api.

ajgbangug commented 10 years ago

Thanks for the tip! I did what you said and I tried calling the AIDR tagger API manually to get all the crisis types but I'm getting this exception.

com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'crisiscoll0_.isTrashed' in 'field list'

koushiksinha commented 10 years ago

Hi AJ,

A new column "isTrashed" in the aidr_predict.crisis table was added. You would need to run the updatedb script in the tagger/resources/scripts folder to update your DB. 2 more columns of note: i) removal of sourceip from the aidr_predict.document table and addition of publiclyListed column to aidr_fetch_manager.AIDR_COLLECTION table. Also, there have been some more changes in the DB schemas.

On Thu, Sep 4, 2014 at 1:37 PM, AJ Bangug notifications@github.com wrote:

Thanks for the tip! I did what you said and I tried calling the AIDR tagger API manually to get all the crisis types but I'm getting this exception.

com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'crisiscoll0_.isTrashed' in 'field list'

— Reply to this email directly or view it on GitHub https://github.com/qcri-social/AIDR/issues/10#issuecomment-54449898.

ajgbangug commented 10 years ago

Ok got it. I'm currently using the tags/v1.1.0 version of AIDR. Would updating the db break something due to compatilibility? Or is it ok if I just go ahead with the changes?