CSC/ECE 517 Fall 2016/ E1700 Integrate Google doc editor/viewer

Expertiza Background

Expertiza is an educational web application created and maintained by the joint efforts of the students and the faculty at NCSU. It’s an open source project developed on Ruby on Rails platform and it’s code is available on Github. Using Expertiza students can bid for a particular project topic and the faculty assigns the same to different groups. Students can track their grades for previous projects and make new submissions for current projects. It also allows students to review each other’s work and improve their work upon this feedback.

Project Description

Currently the instructor creates rubrics for an assignment through questionnaires which students use to review other students' submissions. The only way reviewers can suggest some more changes to the author is by using the 'additional comments' section in the review form which is not very helpful. In this project we will be looking towards improving this functionality by adding an extra medium through which multiple reviewers can collectively comment on the author's work and collaborate their answers in a constructive way. This will be achieved by displaying alert messages to the authors and the reviewers who will use the newly created Google document links embedded into Expertiza. Every project will have a Google doc link for itself which the reviewers can access and make further comments about the project. Once on the Google doc, the reviewer's comments will be posted anonymously, the reviewer's comment will be anonymous to both, other fellow reviewers as well as the author. This feature will help the author to better understand where is his work exactly lacking and how exactly should the changes be worked upon based on the comments received. The reviewers will just need the Google doc link to post comments and it wouldn't be required to login into Expertiza or any google account for using this feature.

Key Points To Consider

• The alert message should only pop up when the faculty as indicated to do so
• The Google doc link needs to be added on the submissions page by the author of the project
• The settings for the Google doc should be set to "anyone with link can comment" by the author
• A peer reviewer needs be directed not login to any Google account to comment on the doc, and all peer reviewer comments shall be anonymous
• Multiple commenting at a specific instance is taken care of by the google document settings and it will be placed one below the other.

Approach

Generally, we can always create a Google document, slide presentation, or spreadsheet using Google Drive and then embed that document anywhere in our application using iFrame as a dynamic rich content editor. The rich content editor is used in features that support the editor (Announcements, Quizzes or Collaborative Reviewing in our case). Any time you make changes to the Google document (like comments), it will be automatically updated in the application's content editor.

The first phase of our project aimed at embedding a google a document which enables the project author to automatically generate a google document with specified permissions for the reviews such that when a reviewer makes a comment it appears without his identity. We succeeded in authorizing the user to the google documents by using the google-client-API (aouth + signet) credentials and the API console also showed positive results for the "request" sent over to the client and created a google document but to access that particular binary file we had to set the permission rights of the service account for which the google document is created which is different from the credentials account. We also tried hard coding and giving all access rights to anyone who wanted to open the file but it seems practically impossible to get those rights.

The second half of the project aimed at creating a flash box which directs the author to set the comment rights on the review google document as decided by the professor subject to the condition and complexity of the project. This will happen on the go and the author is notified to "enable commenting rights only" only if the faculty checks the option for that particular project. On the other side whenever the reviewers click on the google document link attached to the project for reviewing or commenting on a project they will get a notification alert to log out of all google accounts in order to assure the anonymity of the reviewer. This is done because google documents does not support complete anonymity. In this the assumption is that the google doc is created in the same manner as the other hyperlinks are added. Additionally whenever the the which will be already created by the author

Creating Google document, Setting Up its Link

• First and foremost a provision (button) for creating a Google document is added to the Your Work page of Assignments.
• When the authors would select this button before submitting their assignment, a new Google doc is created.
• The document's Sharing criteria is set using google docs API such that the authors of the team can edit the document.
• Sharing criteria is also set such that anyone else having the link to this document can only comment.
• The authors would then copy paste their content, to be reviewed, on to the document.

The expected display on the google documents

• Now the file sharable link must be pasted while submitting an Assignment in expertiza as shown below.
• The new Google doc link will be saved with other hyperlinks in the 'submitted_hyperlinks' column of 'teams' table.

The list of hyperlinks a project author would ideally have

Publishing the document to Web

• Open the File menu in Google doc and select Publish to the web....
• Make sure that the Automatically republish when changes are made checkbox is selected. Click the Start publishing button.
• When a confirmation prompt pops up, click the OK button.
• Click on the Embed tab to get the below screen, now copy the text in order to use it in our expertiza code.

Security Risks

As mentioned in the requirement document, there are 2 security risks associated with this project, they are:

• A situation where the peer reviewer forgets to logout would result in his/ her name being added to the history of document edits which will reveal the identity.
• Possible security violations like an user with access to the link deletes all the content on that doc.

Proposed solution to mitigate the risk:

• When a reviewer goes on the page of submitted contents, he'll be shown an alert message to logout from google accounts if there exists a google docs link in the submitted content and instructor has enabled anonymous commenting.
• The authors of the project will be shown an alert to modify the settings of their google doc to 'Anyone with the link can comment' when they submit a google doc link.

ScreenShot of google document settings

• As it can be seen, Google doc has 3 access levels and the 'can comment' option will allow the users only to add more comments on the Google doc. They won't be able to edit or delete previously entered comments.
• Doing this will ensure that no user even unintentionally will be able to delete or edit previous comments which might be of great value to the authors of that project.
• Also the anonymity is handled if the user directly comments on the document without loging in into other google accounts.

Embedding the document editor in expertiza

• Our aim is to incorporate the dynamic content editor in the Review Assignments page, so that all the users can make collaborative suggestions in the document at the time of Review.
• In order to embed this editor, the code needs to be added in the View page for student responses.
• For example, to embed the editor for Assignment Responses the above code must be incorporated in the view.html.erb file in the response View, as shown below.

• On building the code and running expertiza, we must be able to see the Google doc editor successfully embedded in the Assignment Reviews page.
• In the below image, we can see the frame where the saved Google doc is embedded. Instead of embedding the doc, we can also have a pop-up window of the doc.
• All the text in black in the below image, is the content added by the authors. Hence this cannot be edited by the reviewers.
• The text in colored font are the comments made by reviewers. The below comments have been written for illustrations sake.
• The comments in reality would be different and will be shown on the right side of the document page. (We can correlate this with comments made in MS Word document)
• The users need not login to Google in order to comment in the document. Hence, the comments made will be anonymous.
• If the users are already logged in to Google, constraints will be set such that their ID is hidden and their comments are still made anonymous.

Project File and Database additions

• The new outcome will involve accessing the data base table 'assignments' and we have made a change to the schema of the table by adding a column 'allow_anonymous_commenting' of the type 'Boolean' to indicate whether the professor has asked the project developers to have a review document created with the rights of anonymous comments.
• To incorporate the data base changes we generated a migration file in the "db" migrate named: '_add_allow_anonymous_commenting_to_assignemnnts.rb'
• The 'factories' file in the spec has a variable added with the default value set as 'FALSE'
• '_genral.html.erb' page in the edit assignments view has a 'check box' and a label added to it.
• A function is added in the 'assignments_form' model which sets the visibility to false/ true depending on the input
• The submitted_content view file '_main.html.erb' has the button to upload the google doc link.
• The 'submitted_content_controller.erb' has the code which directs the author to enable the anonymous commenting.
• Newly added Google doc hyperlinks will be saved with other assignment hyperlinks in the 'submitted_hyperlinks' column of 'teams' table.
• The iFrame tag will be added to the 'view.html.erb' file in 'response' View in order to embed the Google doc.

Testing Plan

This UI enhancement will be tested to check whether the following required functionalities are implemented successfully:

i. Any user having the doc link should only be able to comment on the Google doc
ii. Changes made in the original Google doc should be reflected in the embedded doc editor in expertiza
iii. Users need not login to comment in the Google doc
iv. All comments made must be anonymous
v. Multiple comments made at the same time should not lead to any conflicts

References

• Guide to Embedding Google doc editor
• Expertiza application
• Ruby on Rails