Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-31T00:23:11Z

Fameeta: /* Project Description */

==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 and 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==
The existing Expertiza system has an automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory has 18 files which provides features such as spell checker, plagiarism check and the review tone analysis. 
'''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 have converted automated_metareview directory into a gem so that it can be used with other review systems. 
Our goal was to remove the automated_metareview directory from existing Expertiza system and include all those features in the Gem.Thus we can use the gem to include its functionality like review analysis etc.

==Motivation==
The Automated metareview functionality is not used in the existing Expertiza system. If this feature is converted into a gem, then it can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==

===Steps to create Gem===

We have turned the automated_metareview folder into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': Code from the automated_metareview package is placed in this folder. It contains all the 18 files.

'''automated_metareview.rb''' : This file is loaded when require’automated_metareview’ is run. This file is in charge of setting up your gem’s code and API.

'''automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' 
You can build a gem from gemspec using the following command:
gem build automated_metareview.gemspec
Install the generated gem locally to test it out.
gem install automated_metareview-0.0.2

[[File:Build.jpg]]

'''Push gem''' 
In order to make this gem available to everyone, we need to push the gem using : 
gem push automated_metareview-0.0.2.gem

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems: 
gem list -r automated_metareview

[[File:List.jpg]]

===Steps to install and use Gem===

In order to use the gem please follow the below steps: 
1. Run the following command to install the gem
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:
In order to use automated_metareview feature of testing whether a phrase /word is suggestive or not, we can use SentenceState methods to test it :

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix==
===Setup Issues===
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>
1.[http://guides.rubygems.org/make-your-own-gem/ Make your own gem] 
2.[http://repository.lib.ncsu.edu/ir/handle/1840.16/8813 Automated Assessment of Reviews - Lakshmi Ramachandran ]

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-31T00:22:28Z

Fameeta: /* Project Description */

==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 and 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==
The existing Expertiza system has an automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory has 18 files which provides features such as spell checker, plagiarism check and the review tone analysis. 
'''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 have converted automated_metareview directory into a gem so that it can be used with other review systems. 
Our goal was to remove the automated_metareview directory from existing Expertiza system and include all those features in the Gem.Thus we can use the gem to use its functionality like review analysis etc.

==Motivation==
The Automated metareview functionality is not used in the existing Expertiza system. If this feature is converted into a gem, then it can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==

===Steps to create Gem===

We have turned the automated_metareview folder into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': Code from the automated_metareview package is placed in this folder. It contains all the 18 files.

'''automated_metareview.rb''' : This file is loaded when require’automated_metareview’ is run. This file is in charge of setting up your gem’s code and API.

'''automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' 
You can build a gem from gemspec using the following command:
gem build automated_metareview.gemspec
Install the generated gem locally to test it out.
gem install automated_metareview-0.0.2

[[File:Build.jpg]]

'''Push gem''' 
In order to make this gem available to everyone, we need to push the gem using : 
gem push automated_metareview-0.0.2.gem

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems: 
gem list -r automated_metareview

[[File:List.jpg]]

===Steps to install and use Gem===

In order to use the gem please follow the below steps: 
1. Run the following command to install the gem
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:
In order to use automated_metareview feature of testing whether a phrase /word is suggestive or not, we can use SentenceState methods to test it :

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix==
===Setup Issues===
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>
1.[http://guides.rubygems.org/make-your-own-gem/ Make your own gem] 
2.[http://repository.lib.ncsu.edu/ir/handle/1840.16/8813 Automated Assessment of Reviews - Lakshmi Ramachandran ]

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-31T00:19:07Z

Fameeta: /* Setup Issues */

==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 and 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==
The existing Expertiza system has an automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory has 18 files which provides features such as spell checker, plagiarism check and the review tone analysis. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The Automated metareview functionality is not used in the existing Expertiza system. If this feature is converted into a gem, then it can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==

===Steps to create Gem===

We have turned the automated_metareview folder into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': Code from the automated_metareview package is placed in this folder. It contains all the 18 files.

'''automated_metareview.rb''' : This file is loaded when require’automated_metareview’ is run. This file is in charge of setting up your gem’s code and API.

'''automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' 
You can build a gem from gemspec using the following command:
gem build automated_metareview.gemspec
Install the generated gem locally to test it out.
gem install automated_metareview-0.0.2

[[File:Build.jpg]]

'''Push gem''' 
In order to make this gem available to everyone, we need to push the gem using : 
gem push automated_metareview-0.0.2.gem

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems: 
gem list -r automated_metareview

[[File:List.jpg]]

===Steps to install and use Gem===

In order to use the gem please follow the below steps: 
1. Run the following command to install the gem
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:
In order to use automated_metareview feature of testing whether a phrase /word is suggestive or not, we can use SentenceState methods to test it :

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix==
===Setup Issues===
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>
1.[http://guides.rubygems.org/make-your-own-gem/ Make your own gem] 
2.[http://repository.lib.ncsu.edu/ir/handle/1840.16/8813 Automated Assessment of Reviews - Lakshmi Ramachandran ]

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-31T00:18:46Z

Fameeta: /* Appendix: Setup Issues */

==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 and 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==
The existing Expertiza system has an automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory has 18 files which provides features such as spell checker, plagiarism check and the review tone analysis. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The Automated metareview functionality is not used in the existing Expertiza system. If this feature is converted into a gem, then it can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==

===Steps to create Gem===

We have turned the automated_metareview folder into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': Code from the automated_metareview package is placed in this folder. It contains all the 18 files.

'''automated_metareview.rb''' : This file is loaded when require’automated_metareview’ is run. This file is in charge of setting up your gem’s code and API.

'''automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' 
You can build a gem from gemspec using the following command:
gem build automated_metareview.gemspec
Install the generated gem locally to test it out.
gem install automated_metareview-0.0.2

[[File:Build.jpg]]

'''Push gem''' 
In order to make this gem available to everyone, we need to push the gem using : 
gem push automated_metareview-0.0.2.gem

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems: 
gem list -r automated_metareview

[[File:List.jpg]]

===Steps to install and use Gem===

In order to use the gem please follow the below steps: 
1. Run the following command to install the gem
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:
In order to use automated_metareview feature of testing whether a phrase /word is suggestive or not, we can use SentenceState methods to test it :

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix==
=Setup Issues=
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>
1.[http://guides.rubygems.org/make-your-own-gem/ Make your own gem] 
2.[http://repository.lib.ncsu.edu/ir/handle/1840.16/8813 Automated Assessment of Reviews - Lakshmi Ramachandran ]

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T22:35:56Z

Fameeta: /* References */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==

===Steps to create Gem===

We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' 
You can build a gem from gemspec using the following command:
gem build automated_metareview.gemspec
Install the generated gem locally to test it out.
gem install automated_metareview-0.0.2

[[File:Build.jpg]]

'''Push gem''' 
In order to make this gem available to everyone, we need to push the gem using : 
gem push automated_metareview-0.0.2.gem

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems: 
gem list -r automated_metareview

[[File:List.jpg]]

===Steps to install and use Gem===

In order to use the gem please follow the below steps: 
1. Run the following command to install the gem
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:
In order to use automated_metareview feature of testing whether a phrase /word is suggestive or not, we can use SentenceState methods to test it :

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>
1.[http://guides.rubygems.org/make-your-own-gem/ Make your own gem]

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T22:30:17Z

Fameeta: /* Steps to install and use Gem */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==

===Steps to create Gem===

We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' 
You can build a gem from gemspec using the following command:
gem build automated_metareview.gemspec
Install the generated gem locally to test it out.
gem install automated_metareview-0.0.2

[[File:Build.jpg]]

'''Push gem''' 
In order to make this gem available to everyone, we need to push the gem using : 
gem push automated_metareview-0.0.2.gem

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems: 
gem list -r automated_metareview

[[File:List.jpg]]

===Steps to install and use Gem===

In order to use the gem please follow the below steps: 
1. Run the following command to install the gem
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:
In order to use automated_metareview feature of testing whether a phrase /word is suggestive or not, we can use SentenceState methods to test it :

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T22:26:47Z

Fameeta: /* Steps to create Gem */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==

===Steps to create Gem===

We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' 
You can build a gem from gemspec using the following command:
gem build automated_metareview.gemspec
Install the generated gem locally to test it out.
gem install automated_metareview-0.0.2

[[File:Build.jpg]]

'''Push gem''' 
In order to make this gem available to everyone, we need to push the gem using : 
gem push automated_metareview-0.0.2.gem

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems: 
gem list -r automated_metareview

[[File:List.jpg]]

===Steps to install and use Gem===

In order to use the gem please follow the below steps: 
1. Run the following command to install the gem
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T22:26:10Z

Fameeta: /* Steps to create Gem */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==

===Steps to create Gem===

We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' 
You can build a gem from gemspec using the following command:
gem build automated_metareview.gemspec
Install the generated gem locally to test it out.
gem install automated_metareview-0.0.2

[[File:Build.jpg]]

'''Push gem''' 
In order to make this gem available to everyone, we need to push the gem using : 
gem push automated_metareview-0.0.2.gem

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems:
gem list -r automated_metareview

[[File:List.jpg]]

===Steps to install and use Gem===

In order to use the gem please follow the below steps: 
1. Run the following command to install the gem
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T22:23:51Z

Fameeta: /* Steps to create Gem */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==

===Steps to create Gem===

We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' 
You can build a gem from gemspec using the following command:
gem build automated_metareview.gemspec
Install the generated gem locally to test it out.
gem install automated_metareview-0.0.2

[[File:Build.jpg]]

'''Push gem''' 
In order to make this gem available to everyone, we need to push the gem using : 
gem push automated_metareview-0.0.2.gem

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems:

[[File:List.jpg]]

===Steps to install and use Gem===

In order to use the gem please follow the below steps: 
1. Run the following command to install the gem
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T22:21:00Z

Fameeta: /* Steps to create Gem */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==

===Steps to create Gem===

We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:'''
You can build a gem from gemspec using the following command:
gem build automated_metareview.gemspec
Install the generated gem locally to test it out.
gem install automated_metareview-0.0.2

[[File:Build.jpg]]

'''Push gem'''

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems:

[[File:List.jpg]]

===Steps to install and use Gem===

In order to use the gem please follow the below steps: 
1. Run the following command to install the gem
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>

File:Use.jpg

2013-10-30T22:17:42Z

Fameeta: uploaded a new version of "File:Use.jpg"

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T22:15:54Z

Fameeta: /* Steps to install and use Gem */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==

===Steps to create Gem===

We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.

[[File:Build.jpg]]

'''Push gem'''

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems:

[[File:List.jpg]]

===Steps to install and use Gem===

In order to use the gem please follow the below steps: 
1. Run the following command to install the gem
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T22:13:22Z

Fameeta: /* Steps to install and use Gem */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==

===Steps to create Gem===

We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.

[[File:Build.jpg]]

'''Push gem'''

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems:

[[File:List.jpg]]

===Steps to install and use Gem===

In order to use the gem please follow the below steps: 
1. Run the following command to install the gem
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T22:12:42Z

Fameeta: /* Steps to create Gem */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==

===Steps to create Gem===

We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.

[[File:Build.jpg]]

'''Push gem'''

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems:

[[File:List.jpg]]

=Steps to install and use Gem=

In order to use the gem please follow the below steps: 
1. Run the following command to install the gem
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T22:12:08Z

Fameeta:

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==

=Steps to create Gem=

We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.

[[File:Build.jpg]]

'''Push gem'''

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems:

[[File:List.jpg]]

=Steps to install and use Gem=

In order to use the gem please follow the below steps: 
1. Run the following command to install the gem
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>

File:Build.jpg

2013-10-30T19:36:19Z

Fameeta: uploaded a new version of "File:Build.jpg"

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T19:31:02Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.

[[File:Build.jpg]]

'''Push gem'''

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems:

[[File:List.jpg]]

In order to use the gem please follow the below steps: 
1. Run the following command to install the gem
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T19:30:06Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.

[[File:Build.jpg]]

'''Push gem'''

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems:

[[File:List.jpg]]

In order to use the gem please follow the following steps: 
1.
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T19:29:16Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.

[[File:Build.jpg]]

'''Push gem'''

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems:

[[File:List.jpg]]

In order to use the gem please follow the following steps: 
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T19:28:23Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.

[[File:Build.jpg]]

'''Push gem'''

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems:

[[File:List.jpg]]

In order to use the gem please follow the following steps: 
1. 
gem install automated_metareview-0.0.2

OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

==References==
<references/>

File:List.jpg

2013-10-30T19:26:43Z

Fameeta: uploaded a new version of "File:List.jpg"

File:Push.jpg

2013-10-30T19:26:12Z

Fameeta: uploaded a new version of "File:Push.jpg"

File:Push.jpg

2013-10-30T19:25:29Z

Fameeta: uploaded a new version of "File:Push.jpg"

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T19:21:23Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.

[[File:Build.jpg]]

'''Push gem'''

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems:

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1.
gem install automated_metareview-0.0.2

OR
Add following line in gemfile
gem ‘automated_metareview-0.0.2’
Run following command:
bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview-0.0.2’

Example:

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T19:19:14Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.

[[File:Build.jpg]]

'''Push gem'''

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems:

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1.
gem install automated_metareview-0.0.2

OR
Add following line in gemfile
gem ‘automated_metareview’
Run following command:
bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T19:16:19Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.

[[File:Build.jpg]]

'''Push gem'''

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems:

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1.
gem install automated_metareview-0.0.2
OR
Add following line in gemfile
gem ‘automated_metareview’
Run following command:
bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T19:11:56Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.

[[File:Build.jpg]]

'''Push gem'''

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR

You can check in the list of available gems:

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1.
gem install automated_metareview-0.0.2
OR
Add line
gem ‘automated_metareview’ in gemfile.
bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T19:10:38Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.

[[File:Build.jpg]]

'''Push gem'''

[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]

OR
You can check in the list of available gems:
[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T19:09:07Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

File:Structure.jpg

2013-10-30T19:08:03Z

Fameeta: uploaded a new version of "File:Structure.jpg"

File:Structure.jpg

2013-10-30T19:01:15Z

Fameeta: uploaded a new version of "File:Structure.jpg"

File:Structure.jpg

2013-10-30T19:00:38Z

Fameeta: uploaded a new version of "File:Structure.jpg"

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T18:59:57Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

File:Structure.jpg

2013-10-30T18:59:43Z

Fameeta: uploaded a new version of "File:Structure.jpg"

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T18:57:34Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]
[[File:Structure.jpg|thumbnail|alt=Structure.|This text is displayed.|200px|right]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T18:55:24Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]
[[File:Structure.jpg|thumb|alt=Structure.|This text is displayed.|200px|right]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T18:55:04Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|50px|alt=Structure]]
[[File:Structure.jpg|thumb|alt=Structure.|This text is displayed.|70px|right]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T18:54:44Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|left|50px|alt=Structure]]
[[File:Structure.jpg|thumb|alt=Structure.|This text is displayed.|70px|right]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T18:53:21Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|left|50px|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T18:52:57Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T18:52:32Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:structure.jpg|right|50px|alt=Structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T18:51:58Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|right|50px|alt=Structure.]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which there are a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc. 
6. No concrete documentation about the working of the meta review functionality is available due to which a lot of time was required to get the feature running.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T18:49:57Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|right|50px|alt=Structure|structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which thereare a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T18:49:16Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|frame|50px|alt=Structure|structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which thereare a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T18:49:00Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|frame|100px|alt=Structure|structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which thereare a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T18:47:31Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|frame|alt=Structure|structure|WidthxHeightpx=100px]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which thereare a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T18:44:10Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|frame|alt=Structure|structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which thereare a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T18:42:47Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|frame|alt=Structure|structure]]

'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.

'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Create Gemspec : Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.
[[File:Gemspec.jpg]]

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which thereare a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T18:42:22Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|frame|alt=Structure|structure]]
'''Lib''': code of automated_metareview package is placed in this folder. It contains all the 18 files.
'''Automated_metareview.rb''' : This file gets loaded when require’automated_metareview’ is run. That one file is in charge of setting up your gem’s code and API.

'''Create Gemspec : Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.
[[File:Gemspec.jpg]]

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which thereare a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc.

CSC/ECE 517 Fall 2013/oss E812 amp

2013-10-30T18:41:16Z

Fameeta: /* Design */

==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==
Existing Expertiza system had automated_metareview.rb class which was using the text processing functionality from automated_metareview directory. "automated_metareview" directory had 18 files which included features like spell checker, plagiarism check and the review tone. 
'''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. 
Our goal was to remove the automated_metareview directory from existing Expertiza system. Include all those features in the Gem, and then import the functionality from the Gem file.

==Motivation==
The features of Automated metareview were integrated in the existing Expertiza system. If these features were converted into a gem, then these can be used in other review systems, wherein the reviewer will get an automated feedback about the review and he/she can change the review based on the results of automated metreview results. Thus by creating a gem file, other systems can install the gem and get access to all features of automated metareview, thereby increasing reusability.

==Design==
We have turned the automated_metareview feature into a gem called “automated_metareview” which could be used in other review systems.
Here is the basic structure of our gem:

[[File:Structure.jpg|frame|alt=Structure|structure]]

'''Create Gemspec : Automated_metareview.gemspec''' : This file gives details of the gem, author, version and other details.
[[File:Gemspec.jpg]]

'''Build and Install Gem:''' You can build a gem from gemspec. Then you can install the generated gem locally to test it out.
[[File:Build.jpg]]

'''Push gem''' :
[[File:Push.jpg]]

This gem is now available for installation by anyone. This can be viewed in [http://rubygems.org/gems/automated_metareview http://rubygems.org/gems/automated_metareview]
OR

[[File:List.jpg]]

In order to use the gem please follow the following steps:
1. gem install automated_metareview-0.0.2
OR
Add line gem ‘automated_metareview’ in gemfile. Do bundle install.
2. Add following line in the code where you want to use the gem:
require ‘automated_metareview’

[[File:Use.jpg]]

==Future Work==
The current implementation has a few method calls very specific to Expertiza. We can change these methods so that they can be used in any other system. We generalized a few methods, so that it can be used in systems similar to Expertiza. But we can generalize it more such that we can seperate functionalities like Spell checker , plagiarism check in separate gem file.

==Appendix: Setup Issues==
1. There were a lot of problems with the master branch of expertiza. 
2. There were many missing routes. 
3. We faced a number of problems installing Aspell dictionary on windows. 
4. There are a number of steps which need to be followed to activate the metareview feature. 
5. The automated meta review feature is partly implemented using java due to which thereare a number of dependencies. To overcome these dependencies we need to install multiple jar files such as joda-time.jar,stanford-segmenter.jar etc.