Researchware, Inc.

Although HyperRESEARCH was originally designed to be used by one person at a time, it includes many options for sharing data that allow multiple-researcher teams to work on a study in both the coding and analysis phases.

(For information about exporting data from HyperRESEARCH to be used in other programs, see the "Exporting Study Data" topic in the "HyperRESEARCH Help..." option in the Help menu. You can export code lists, reports, theory results, and more.)

For Best Results:

We recommend that team members who are working collaboratively (combining their work into a larger HyperRESEARCH study) ensure that everyone on the team is using the same version of HyperRESEARCH based on the Version Number (e.g. HyperRESEARCH version 4.5.3, etc.). It doesn't matter whether team members are using the Windows version of HyperRESEARCH or the macOS version (the software is fully cross-platform compatible), but they should all be on the same version number.

It's also best practice to be sure to update each team member's copy of HyperRESEARCH to the latest version as new versions are released. Each new version within a version number includes improvements that enhance the software's stability and provide additional functionality. Please see our Downloads page for the latest versions and their installers: http://researchware.com/downloads/downloads-hyperresearch.html 

A Note about License Keys:

Researchware offers generous license terms, allowing individual users to install HyperRESEARCH on multiple computers (e.g. a desktop, a laptop, an office computer), OR to install and unlock HyperRESEARCH on a "per seat" basis (e.g. for a computer lab, where anyone who has access to the computers with HyperRESEARCH installed will be able to access the software.) (You can see the full "legalese" license information here: http://researchware.com/43-faqs/purchasing-faq/221-what-are-your-licensing-terms.html)

However, we ask that you make sure you (or your organization) have obtained enough license keys to cover "concurrent use." That means if you expect to have multiple people working on their separate computers at the same time, you should have enough license keys to cover that number of people. (Note that we don't send any "license police" piece after anyone, it's on the honor system. But we do need to bring in enough income to keep the lights on and our developers and tech support people continuing to work on improving your qualitative data analysis software experience.)

Sales Support for Teams:

Researchware offers volume discounts (beginning at 10% off for 2-4 copies of HyperRESEARCH purchased at the same time, with the discount increasing with the increase in the number of licenses purchased). We are also happy to work with you and your team to provide the licenses you need within the budget constraints you have.

We also offer annual site licenses for larger numbers of users. We have flexible terms for site licenses, and the annual renewal means the cost of the software can be spread across the years the site license is in effect. Site licenses include full customized tech support (directly for the users, not just for IT personnel), free customized webinars that can be scheduled to correspond with a particular class time for class participation, and so on. Contact Sales support for more information: http://www.researchware.com/contact/contact-sales-support.html

How to Work Collaboratively:

Sharing study files and source files

To distribute a study file to other researchers—either for additional coding or for analysis—you will need to send the study file along with your source files. For this reason, it’s usually best to set up your study so that all your source files are in a single folder. This makes it easier to send the source files, and less likely that a file will be missed. We recommend that you also use the Study Packager (in the Tools menu) for packaging up the study and source files into a compressed file (filename extension ".hs4z") that can easily be provided to others via email or other means of sharing files. A study package file can be opened in HyperRESEARCH via the same Study Packager Tool.

Sources in HyperRESEARCH:

When you work with a source file in HyperRESEARCH, the source is not imported or copied into your study file. Instead, HyperRESEARCH saves the name and location of the source file, along with the location of code references for that file. This approach improves memory use and performance, since source files are only opened when they’re needed.

Because of this, it’s important that all researchers who are working on a study all have the same version of the source files. If a source file is coded by one researcher, and then the study is opened by another researcher with a different version of the source file, the code references in that source file may be shifted so that the wrong text is associated with the code.

To prevent this, when you send a study file, make sure to also send the source files you’ve used. If you are sure your colleague has the same version of the source files, you don’t need to send them again, but if in doubt, send any files that you believe might not be identical on your colleague’s computer.

Workflow for sending a study:

You can distribute a study to any number of other researchers. To open the study file, the other researcher’s computer must have HyperRESEARCH installed—either the full licensed edition, or the Free Limited Edition.

The process looks like this:

1. You send the study file and source files to the other researcher. You can email the files, save the files to a USB memory stick (portable external drive) to give to another researcher, use your local network, use a file sharing or file synching service (e.g. Dropbox), or use any other method that’s convenient. Tip: the "Study Packager" tool in the Tools menu is a great way to pack your study file and associated source files into a zipped archive, which can be "unpacked" and opened via the Open Study Package feature in the Study Packager. 
2. The recipient opens the study file in HyperRESEARCH. Tip: To simply view the data or create reports, the recipient can use the Free Limited Edition of HyperRESEARCH, without purchasing a license. The Free Limited Edition is available on the Researchware website at
   http://www.researchware.com/hr/downloads.html. However, to add codes or cases beyond the Free Limited Edition’s limits, the recipient must have a HyperRESEARCH license. For more about the Free Limited Edition, see the Free Limited Edition topic in HyperRESEARCH's built-in Help documentation.
3. The recipient identifies the new location of the source files. HyperRESEARCH stores the location of sources files within the study file, and when the files are moved to another computer (possibly with a different hard disk name, different folder structure, and so on), the location has changed. Tip: The first time the recipient does something that requires accessing a source file — such as clicking a code reference when the View Source box is checked, or creating a report that includes source information — HyperRESEARCH asks where that source file is. Once the recipient has identified the file’s location, HyperRESEARCH checks whether all other sources are in located within the same folder. If they are, the HyperRESEARCH updates the location of all source files.
4. To make sure that HyperRESEARCH won’t need to ask again for the location of source files, the recipient should choose Save from the File menu to save the study file. This ensures that the new location of the source files is also saved.

Sharing code lists between studies

To share a common set of codes among members of your research team or among different studies, first create the code list in your study file, then choose Export List from the Edit Code menu at the top of the Code Book window. This command exports the entire code list, along with the code descriptions, to a text file. (Codes are separated by returns, and each code is separated from its description by a tab.)

To share a common set of codes among members of your research team or among different studies, first create the code list in your study file, then choose Export List from the Edit Code menu at the top of the Code Book window. This command exports the entire code list, along with the code descriptions, to a text file. (Codes are separated by returns, and each code is separated from its description by a tab.)

To re-use the exported list in another study file, open the study file, then choose Import List from the Edit Code menu at the top of the Code Book window. Choose the file you previously exported. The codes from that file will be added to the current study file.

In this way, you can keep a core set of codes and use them in all studies. You can also exchange code lists among researchers who are working on the same study, ensuring that everyone is working with the same list of codes.

Alternatively, you may use spreadsheet software to create a code book file you can import into HyperRESEARCH's Code Book. See "Importing Code Lists" for detailed instructions and downloadable Excel templates.

Merging study files

Teams of researchers often work on the same study, sharing the coding task among several people. Since coding a source file adds data to your study, if researchers are to share the coding, the team needs to create a file that includes all the coding everyone has done.

In HyperRESEARCH, you use the Import Studies feature to accomplish this task. Import Studies adds code references from each file you designate to a “master file”, which then includes all the coding that has been done. (You have a variety of options to deal with situations where the same code reference appears in more than one coder’s work.) One person should handle this task, merging all the work done so far into one study file, which can be redistributed to the team for more work.

1. To merge other studies into your current study file, follow these steps:
2. Collect a copy of the study file from each person who has done coding in the study. (You don’t need to collect their source files, only the study file.) It’s most convenient to put all these study files into the same folder, giving each one a different name. For example, “QDA Study - Jane.hs4” includes the study’s name and the name of the person who worked on this copy.
3. Open the study file that you want to serve as the master file.
4. Choose File Import Other Studies. The Import Studies window opens.
5. Click Add a Study File and select the first file you want to merge. (To save time, if the study files are all in the same folder, you can click Add All Study Files in Folder and select the folder.)
6. For each study file you add, a section appears to let you control how to handle duplicate cases — that is, cases that have the same name, but not necessarily the same codes. You have three options for duplicate cases:

• Append Case Names With: include the duplicate case and add a suffix to its name, so you know which file each duplicate came from. Use this option if this file’s cases are completely separate, or if you want to review any duplicates manually.
• Add Codes to Existing Case in Master Study: merge the duplicate case with the same-named case in your current study file, so there's only one case that has all the code references from both duplicates. Use this option if you’re sure that any case with the same name is just a duplicate of the one you already have, with additional coding which should be merged into a single case.
• Don't Import Cases With Duplicate Names: skip any case that’s already in your current study file. Use this option if the cases in your current study file should always be taken as the definitive version of the case.
• 
  Click the Import Study button at the bottom of the window. (The button’s name changes depending on how many studies you’ve selected to import.)

The studies are imported into your current study. Any codes, annotations, and source files that are used in cases you import are added to your current study, so it contains the complete material from all imported cases from each study file.

If you used the Append Case Names option for any of the files, review the duplicated cases to decide which one to keep, or whether to merge the duplicates together. (To manually merge two cases, select all the code references in the first case, choose Edit Cut Codes, then go to the second case and choose Edit Paste. This moves all the code references from the first case to the second case. You can then delete the empty first case.)

You can now re-distribute this updated file to your colleagues for further work, or continue with the analysis and reporting stage of the study.

Questions?

Please contact our tech support team: http://www.researchware.com/contact/get-support.html