CSC/ECE 517 Fall 2013/oss E812 amp: Difference between revisions
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
We had the following code already implemented.<br/> | We had the following code already implemented.<br/> | ||
Class: automated_metareview.rb (188 lines) and 18 files in the automated_metareview directory.<br/> | Class: automated_metareview.rb (188 lines) and 18 files in the automated_metareview directory.<br/> | ||
What it does: Gives automatic feedback to a reviewer, using NLP text analysis, to help the reviewer improve the review.<br/> | '''What it does''': Gives automatic feedback to a reviewer, using NLP text analysis, to help the reviewer improve the review.<br/> | ||
What needs to be done: We had to convert automated_metareview directory into a gem so that it can be used with other review systems.<br/> | '''What needs to be done''': We had to convert automated_metareview directory into a gem so that it can be used with other review systems.<br/> | ||
==Design== | ==Design== | ||
Revision as of 16:38, 30 October 2013
Intrdouction
This article is a report about our Open Source project(Expertiza) - Turn automated_metareview folder into a gem . It explains the design considerations, steps followed, issues faced while setting up Expertiza. It explains how our team manages to create a new Gem file, and test it on the existing Expertiza system.
Project Description
We had the following code already implemented.
Class: automated_metareview.rb (188 lines) and 18 files in the automated_metareview directory.
What it does: Gives automatic feedback to a reviewer, using NLP text analysis, to help the reviewer improve the review.
What needs to be done: We had to convert automated_metareview directory into a gem so that it can be used with other review systems.