Managing your work
This topic lists points to bear in mind when creating and working on projects that you want to share with other users. For more information, see the UNICOM Intelligence Interviewer - Server Admin User Guide.
▪When you create a new project you can use the Permissions tab to specify which roles (user groups) can access the project. If you forget to do this or you need to change your choices, ask your UNICOM Intelligence Interviewer administrator to do it for you.
▪Files are created and updated in your user folder. If you want the files to become available to other users you must check them in to the shared folder. There is no need to do this every time you change or create a file so, for example, you can build a questionnaire using Build, test it, refine it and then retest without checking anything in. When you have finished building the questionnaire (or the first version of it) you should check it in then.
▪Some activities check in copies of files from your Users folder to the Shared folder. Nevertheless, it is good practise always to check in all files that you want to make public when you have finished with them.
▪The first time you work on a project, the project becomes locked by you. This means that although other users can access the project’s files for reading, they cannot change them. Typically, all UNICOM Intelligence Interviewer activities are unavailable to other users of a project if the project is locked by you.
▪Projects are not unlocked automatically. You must unlock a project when you have finished working on it, after you have checked in the latest files.
▪Do not unlock a project before you have checked in all its files as this may mean that other people who use the project will use old versions of the files which do not have your latest changes in them.
▪Do not keep a project locked longer than you need to, as this prevents others from editing the files.
Note Some users may have permission to unlock projects that have been locked by other people. If you have this permission, always be very careful when unlocking other peoples’ projects, especially of you are going to run activities that alter the project’s files. If you can, it is a good idea to check with the user before unlocking the project, particularly if you suspect that the user may be working on the project and may not have checked in the latest versions of the project files. If you have to unlock a project to work on it, always let the project’s owner know what you have done.
See also