Jump to content
Margoc

Merging NVivo projects and framework matrices

Recommended Posts

Hello,

We are using framework matrices to start analysis of our data. We currently have 3 people coding and doing the matrix summaries for individual families in our study.

I set up a master folder on our network space where I save the master project and I use this version/copy to do my coding and summaries.

I set up two other folders on our network space for the other two current researchers who are also coding and doing the matrix summaries.

From my understanding of merging this is what I have been doing.

Once a week I have opened the master project and individually imported selected content (sources, coding, annotations, links, summaries), from each of their saved versions of the project. But I was not selecting users I was just importing everything. Then I was saving this new version of the merged project back into the master folder and their two separate folders. They would then continue coding, summarizing etc with this updated copy.

Today I finally noticed that the summaries that I had done were being duplicated under the existing summaries.

So I tried to just import the work of each researcher and it made duplicate matrices - eg: Family 01 and it would make Family 01 (2) but there would be nothing in the matrix.

I am not sure how to go about importing just their work from the week without it changing my summaries, their summaries or any of the matrices already existing.

 

Hope this makes sense - can anyone help?!

Thanks, Margo

 

Share this post


Link to post
Share on other sites

Hi Margo,

 

When projects are merged, the Framework Matrices that have the same name, folder location and contain the same row and column nodes are considered duplicates and hence merged. Differences in row header attributes are however, ignored. It seem that either folder location or row/column nodes are not same in the Framework Matrices. This is most likely the reason why matrices are not merging.

 

Please refer to the link below for more information on how NVivo determines that two project items are duplicates:

http://help-nv10.qsrinternational.com/desktop/deep_concepts/how_duplicate_project_items_are_handled_during_import.htm

 

I hope this information is helpful.

 

Regards,

Bhupesh

Share this post


Link to post
Share on other sites

Hello Bhupesh,

That is not what is happening. I just tried to merge a test project into a master and chose to merge duplicates and the framework matrices are the same but it created duplicates for all of them.

It seems that the NVivo we have is not following the below instructions:

How NVivo handles duplicate items during import

When you import project content you must decide how you want NVivo to handle duplicates—you can choose to merge the duplicates or create new items.

If you choose to create new items, duplicate items are imported and renamed, so that both items exist in the open project— for example, Interview with Sally would be renamed Interview with Sally (2).

If you choose to merge duplicates, the following rules apply:

Framework matrices Row header attributes The framework matrix in your project is retained.

 

I will send a help request and attach a word document with the print screen.

Margo

Share this post


Link to post
Share on other sites

Hi Margo,

 

Thank you for submitting the support request.

 

I've just sent you an email. Please reply to the email if you have further questions.

 

Regards,

Bhupesh

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×