adding new documents and document groups.adding a memo with information for the team.HousekeepingĪfter merging all projects, the project administrator may need to perform some housekeeping work, such as: Please follow the recommended workflow described under Team Work. ![]() You can however not merge duplicated documents. Issues around duplicated codes you can solve yourself by merging those codes (see below Housekeeping). This will result in duplicated documents and codes after merging. All entries in the column Import are shown in bold as this is what will used in the merged project.Ī common mistake is that team members set up their own projects, adding documents and codes. The project administrator has decided to keep the changes from the import project and selected Override. In the example below the code color for a number of codes and two code labels are different in the Master and Import project. As project administrator, you will have to decide whether to accept these changes or not. If all team members have been coding different documents, merge conflicts are unlikely to occur.Ī conflict could arise, for instance, if someone changed the code colour, comment or code name. Override: the version in the Master project will be overridden, and the changes made in the Import project 'win'.Keep: the Master project 'wins', and the changes made in the Import project are ignored.If there are conflicts between the Master project, and the project that you import, you can solve the conflict in two ways: If there are no conflicts, you can proceed with merging the two projects by clicking Merge. If the comment of the Import project should be kept, you need to select the option Override. If the comment of the Master project should be kept, you need to select the option Keep. In the case of an unsolvable conflict - code C in the Master project has a comment, and code C in the Import project also has a comment - the user can define which of the two conflicting entities will win. If there is a code C in the Master project that has no comment, and a code C in the Import project that has a comment, the merged procedure will add this comment to the merged project. Groups are AdditiveĪ Group B with documents ) in the merged project. If the meaning of both codes is the same, and you want to keep one sunshine code only, you can merge the two codes manually. If you merge Tom's and Anne's project, the merged project will contain two codes: sunshine and sunshine (2). Therefore, they will have a different ID. Thus, the name of an entity is not the decisive factor.įor example: If a user Tom has created a code with the name sunshine, and a user Anne also has created a code with the same sunshine in her project, these two codes are not identical as they have been created on different computers and in different project. If the ID is not the same, they are added. If they have the same ID, they are unified. When merging projects, ATLAS.ti compares the IDs of the various entities. When an entity is created in ATLAS.ti - regardless if it is a document, a code, a quotation, a memo, a network, a group, or a comment - this entity receives a unique ID, comparable to a fingerprint. ![]() You can only merge ATLAS.ti desktop and ATLAS.ti Web projects if the projects contain different documents and codes! Identical Entities Explained
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |