Usage Scenarios

QuiRC 2 for Drupal 6 - Usage Scenarios - Proposed Usage

QuiRC is meant to be installed on an internet server and then used to perform qualitative research. Installing the QuiRC module is left to another discussion. QuiRC supports two kinds of coding projects, Individual Coding and Group Coding. We assume for the purposes of this discussion that four coders and one administrator are working on a project. The administrator will be referred to as 'root' and is also the root user on the drupal site. The coders are named 'Dave', 'Sam', 'Harry',and 'Tom'. They are working on a project concerning laughter and humor in the workplace. The administrator, root, has decided that they will use QuiRC for individual and group coding. This means there will be two QuiRC projects on the Drupal site, which they have decided they will call 'Workplace Humor - I' and 'Workplace Humor - G'.

The first thing the researchers have to do is to go to various workplaces and collect information. For this entire project they will conduct five interviews and transcribe them. It is not important weather the documents are in the text or Word format. The documents must have either the .txt or the .doc extension. The five documents will be uploaded to QuiRC where the researchers will do individual coding in the 'Workplace Humor - I' project. As a result of this coding several key codewords will be determined. Then a second project will be created. This is the 'Workplace Humor - G' project. The five documents will be uploaded again and the new codewords will be locked in by the administrator. Coding will begin again with the second project. When it is determined that coding is complete, the administrator will 'close' the project and the results of the project can be analyzed.

I. Preparing QuiRC

1.) Create four roles for the QuiRC system. You can call them anything you like, but we have called them 'quirc super admin', 'quirc coder', 'quirc uploader', and 'quirc project admin'. You can do this as the root user by logging in as root, and then going to the Administer page. From there select User Management, and then Roles.

2.) Associate the four roles with the basic QuiRC permissions. Log in as root, then go to 'Administer', 'User Management', and finally 'Permissions'. This will take you to a screen where you can associate the roles with the permissions. The permissions are called 'Access QuiRC Admin', 'Access QuiRC Coder', 'Access QuiRC Upload', and 'QuiRC Super Admin'.

3.) Setup Antiword and enable uploads. As root user you can access the 'QuiRC Settup' page under the 'Administer' menu. Go to this page and determine how you will setup uploads on your system. Most people will want to enable Antiword. Enabling Antiword is not covered here, but even if you don't enable Antiword, you will want to enable document uploading. If you do you will be able to upload text documents with the '.txt' extension. If you also install and enable Antiword you will be able to upload Word documents with the '.doc' extension. For this example we are going to assume that Antiword is installed. Note: The root user or a user with the 'QuiRC Super Admin' permissions can access this page and setup Antiword.

4.) All the users who use the QuiRC module must be regular users on the drupal site. Root is obviously already a user, but Dave, Sam, Harry, and Tom must be users as well. Log in as the root user and go to each user's profile and give them roles as 'quirc coder'. The root user already has the permissions of the 'quirc project admin'. For the purposes of this explanation, give Tom the role of 'quirc uploader' and 'quirc project admin' as well.

II. Individual Coding

1.) The root user must create the first project. The root user logs in and goes to the 'QuiRC Pages' menu. There they choose the 'Create/Delete Projects' page. At the top of the page is a form for creating new projects. Root types 'Workplace Humor - I' in the field labeled 'New Project Name:'. Then Root makes sure that the 'Set Individual Coding' checkbox is checked. Then root clicks the 'Setup New Project' button.

2.) Users must be added to the project. Root goes to the 'QuiRC Pages' menu and chooses the 'User/Project Relations' page. There is a single form on this page. At the top of the form is a dropdown list showing all users with at least one QuiRC role. Root chooses 'Tom' from the dropdown list.

3.) A project must be selected for the operation. The root user selects 'Workplace Humor - I' from the scrolling list of available QuiRC projects.

4.) You must select weather you want to add a user to a project or remove a user from a project. Root selects 'Add Group Connection' from the two buttons in the 'Add or Delete Group Connection' section of the form.

5.) Each user must be added to the project separately. The root user or an administrative user associated with the project can do this. In this case the root user simply repeats the actions in steps 2 through 4 for Dave and Sam. For this part of the example Harry will not be one of the coders.

6.) Documents must be added to the project. All the transcribed documents are given to Tom.

7.) Tom logs on. He goes to the 'QuiRC Pages' menu and chooses the 'Upload/Delete Documents' page. There are two forms on this page. In the top form Tom chooses the project 'Workplace Humor - I' from the list of available QuiRC projects.

8.) Tom clicks the 'Browse' button. This will open up a window on Tom's computer that allows him to choose one of the transcribed documents from his file system. When Tom has found one of the documents he selects it and clicks 'open' or 'select' on the window. The path to that document will show up in the 'Document to Upload' box on the QuiRC uploads page.

9.) Tom clicks the 'Upload Document' button to complete the upload.

10.) Each document must be added to the project separately. Tom repeats the steps in this section marked 8 and 9 for each document.

11.) With all the users and documents added to the project, and the project type set to 'Individual Coding', the project 'stage' can be set. Tom selects the 'Set/Unset Project Stages' page from the 'QuiRC Pages' menu.

12.) Tom chooses the 'Workplace Humor - I' project from the list of projects.

13.) Tom chooses the desired 'stage' from the three choices. The choices are 'Start', 'Active', and 'Closed'. Tom chooses 'Active'.

14.) Tom clicks the 'Confirm Stage Settings' checkbox.

15.) Tom clicks the 'Set Project Stage' button. The 'stage' is set. Coding can commence.

16.) Dave and Sam must be notified that coding can begin.

17.) Dave, Sam, and Tom code the five documents remotely from their individual computers independently of each other. Dave, Sam, and Tom will each come up with codewords for the five documents and use the coder page to highlight the documents according to their independent codewords.

17.a.) At any point Tom or any administrator on the project can view lists of everyone's codewords by clicking the 'View Highlights' button on the bottom of the coder page. These lists can be printed.

17.b.) Dave, Sam, and Tom can also print out copies of the individual documents with all their coding for a particular codeword by clicking the codeword they are interested in and then clicking the 'Printer Friendly View' on the coder page.

18.) When Dave, Sam, and Tom decide that the project is finished Tom can close the project. Tom selects the 'Set/Unset Project Stages' page from the 'QuiRC Pages' menu.

19.) Tom chooses the 'Workplace Humor - I' project from the list of projects.

20.) Tom chooses 'Closed' from the three choices on the page.

21.) Tom clicks the 'Confirm Stage Settings' checkbox. Then Tom clicks the 'Set Project Stage' button. No more coding can take place. All users on the project can still visit the project and review their coding, and printouts can be made as before, but new coding cannot be done. Note: The administrator can change the stage back to the 'active' stage, but can only change to the start stage if all coding is erased from the project.

22.) Dave, Sam, and Tom can review the project, and if they decide to go on to the more restrictive 'Group Coding Project', can derive their new codewords at this point. Group Coding Projects are like Individual Coding Projects in many ways but there is only one set of codewords that all coders must adhere to. They cannot create their own themes.

III. Group Coding

1.) Since Tom is an administrator he can create his own projects. Tom logs in and goes to the 'QuiRC Pages' menu. There he chooses the 'Create/Delete Projects' page. At the top of the page is a form for creating new projects. Tom types 'Workplace Humor -G' in the field labeled 'New Project Name:', then makes sure that the 'Set Group Coding' checkbox is checked. Tom clicks the 'Setup New Project' button. He is automatically added to the project at creation.

2.) Users must be added to the project. Tom goes to the 'QuiRC Pages' menu and chooses the 'User/Project Relations' page. There is a single form on this page. At the top of the form is a dropdown list showing all users with at least one QuiRC role. Root chooses 'Dave' from the dropdown list.

3.) A project must be selected for the operation. Tom selects 'Workplace Humor - G' from the scrolling list of available QuiRC projects.

4.) You must select weather you want to add a user to a project or remove a user from a project. Tom selects 'Add Group Connection' from the two buttons in the 'Add or Delete Group Connection' section of the form.

5.) Each user must be added to the project separately. The root user or an administrative user associated with the project can do this. In this case Tom simply repeats the actions in steps 2 through 4 for Sam and Dave. For the purpose of this example we will add another user named 'Harry' to the project. Harry is just a coder.

6.) Documents must be added to the project as before.

7.) Tom goes to the 'QuiRC Pages' menu and chooses the 'Upload/Delete Documents' page. There are two forms on this page. In the top form Tom chooses the project 'Workplace Humor - G' from the list of available QuiRC projects.

8.) Tom clicks the 'Browse' button. This will open up a window on Tom's computer that allows him to choose one of the transcribed documents from his file system. When Tom has found one of the documents he selects it and clicks 'open' or 'select' on the window. The path to that document will show up in the 'Document to Upload' box on the QuiRC uploads page.

9.) Tom clicks the 'Upload Document' button to complete the upload.

10.) Each document must be added to the project separately. Tom repeats the steps in this section marked 8 and 9.

11.) With all the users and documents added to the project, and the project type set to 'Group Coding', the project 'stage' can be set. Tom selects the 'Set/Unset Project Stages' page from the 'QuiRC Pages' menu.

12.) Tom chooses the 'Workplace Humor - G' project from the list of projects.

13.) Tom chooses the desired 'stage' from the three choices. The choices are 'Start', 'Active', and 'Closed'. Tom chooses 'Active'.

14.) Tom clicks the 'Confirm Stage Settings' checkbox.

15.) Tom clicks the 'Set Project Stage' button. The 'stage' is set.

16.) Tom's last job before coding can commence is to use the coder page to input all the codewords that the group will use when coding the documents. When Tom enters them on his computer they are automatically added to the accounts of the other users. To see the new codewords they refresh their screens, so it might be better to do this before the coders log on to the project for the first time.

17.) Dave, Harry, and Sam must be notified that coding can begin. For this example Tom, though he's a member of the project, will not actually code.

18.) Dave, Sam, and Harry code the five documents remotely from their individual computers independently of each other... but using the same codewords. Dave, Sam, and Harry will each come up with highlighting for the five documents according to the codewords established for the project.

18.a.) At any point Tom or any administrator on the project can view lists of everyone's codewords by clicking the 'View Highlights' button on the bottom of the coder page. These lists can be printed.

18.b.) Dave, Sam, and Harry can also print out copies of the individual documents with all their coding for a particular codeword by clicking the codeword they are interested in and then clicking the 'Printer Friendly View' on the coder page.

18.c.) Tom can also view the 'Statistics' page. The statistics page is only available in Group Coding projects.

18.d.) Tom can also use the 'View Users' mechanism to view another coder's highlighting just as they would see it themselves.

19.) When Dave, Sam, Harry, and Tom decide that the project is finished Tom can close the project. Tom selects the 'Set/Unset Project Stages' page from the 'QuiRC Pages' menu.

20.) Tom chooses the 'Workplace Humor - G' project from the list of projects.

21.) Tom chooses 'Closed' from the three choices on the page.

22.) Tom clicks the 'Confirm Stage Settings' checkbox. Then Tom clicks the 'Set Project Stage' button. No more coding can take place. All users on the project can still visit the project and review their coding, and printouts can be made as before, but new coding cannot be done. Note: The administrator can change the stage back to the 'active' stage, but can only change to the start stage if all coding is erased from the project.

FINAL NOTES:
- The root user can create and destroy any project, as well as perform all administrative tasks, but once a regular user has been created and given administrative privileges AND added to a project, they can create projects on their own. They can also delete projects that they created as well as add users to projects. What should be the first project then? A project is provided that is always present on all QuiRC systems called the 'default' project. It can be used to test out features as well as other things. You could use it as the first project where the first group of admin users are all members. They could then go off and create their own projects and manage those projects on their own. As long as you never switched the 'default' project to the 'Active' stage, the root user could add administrative users to the system any time they wanted by adding them to the 'default' project.

- In the Group Coding example above we showed that the administrator, Tom, didn't have to code in the project once it was set up. This arrangement works some of the time, depending on your needs. As it turns out, some of the statistics on the statistics page are displayed incorrectly in this arrangement. This is the case whenever a regular user is the administrator for a group project and does not code. This applies to the 'Conformity' part of the statistics page. If the administrator in question also codes this is not a problem. This can be avoided by using the root user as the administrator for a group project. The statistics then exclude the root user automatically.

- There can be more than five documents in a project and more than three coders and one administrator. There can also be more than one user in a project that has administrative privileges. This other user can code normally and also review project results.

- In a group project it is possible to add more codewords to the project after coding has started. Codewords can also be deleted. This is not recommended, though, as it could produce confusing results for individual coders. Coders could also inadvertently make database entries that destroy the project's integrity. In any case, coders only need to refresh their pages in order to see the new arrangement of codewords in a project after they've been changed.

- Since you need to erase all codewords from a project in order to move the project's stage back to the 'start' stage, there is a form provided for administrators to do this easily. It can be found on the 'Create/Delete Projects' page below the other two forms.