Therefore, ensure that you are logged in with the correct account, not, for example, with a private ATLAS.ti account. Once activated, the license is bound to this account and cannot be transferred to another account. To activate the license, type/paste the license key you received when you purchased it and confirm that you want to activate it. When you have your organization account and your license key, you can activate it. If you already have an account and have opted to be automatically logged in, you may need to log out first and then register the new organizational account. To create the organization account, go to my. and register as a new user. Use a strong password, as anybody with access to this account can otherwise block the end-users from accessing ATLAS.ti. Name the account something descriptive, as the end-users will see this name. Create and use a generic email address, such as or Ensure you receive emails from this account, as the email address must be verified. You may change jobs, and your colleagues will not be able to access the account anymore. Here are some tips for creating an organizational account:ĭo not use your personal email address. This is true for both administrators and end-users.Īn organization account is no different than a regular ATLAS.ti account, except that the intent of the account is to manage and share the organization's ATLAS.ti licenses with end-users in the organization. See Working with ATLAS.ti Libraries.ĭocument libraries CANNOT be shared.To use ATLAS.ti 23 and ATLAS.ti Web, you need an ATLAS.ti account. The location of where ATLAS.ti stores project related data can be determined by each user. If document editing is necessary, this needs to be done by the project administrator in the Master project! If they do, the edited documents cannot be merged, and you end up with duplicates. Otherwise, the documents are duplicated or multiplied during the process of merging. If all team members should work on the same documents, it is essential that only the project administrator is setting up the project adding all documents. A good time for doing this is after merging and before creating the new Master file. If new documents need to be added to the project, this needs to be done by the project administrator. The project administrator exports the new Master file and distributes it to all team members. The project administrator merges all subprojects, and creates a new Master file. To combine the work of all team members, each team member creates a project bundle file and sends it to the project administrator. This means creating a project bundle fileĪll team members import the project bundle file and begin their work. The project administrator saves the project and exports it. The project administrator adds documents to the project and possibly a list of codes. The project administrator sets up a Master project. If document editing is necessary, this needs to be done by the project administrator in the Master project! Workflow If team members edit the same documents, these cannot be merged instead they are duplicated. When working on a team project, team members must not edit documents (unless everyone works in different documents).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |