Project Functions

Project operations are accessed from the pull-down menu, by pointing to a project folder icon and pressing the right mouse button (right-clicking), or by using the various keyboard shortcuts.

Project Pull-Down Menu 

Project Right-Click Menu 

You should note the following when right-clicking on a project icon:

  1. If you are in the database view, you should switch off the automatic expand option in the system properties to allow the pop-up menu to be displayed with the right-click.

  2. You need to be in the file list view to have access to the project-wide transfer functions with the right-click.

Like all other operations within the TIMS3 environment, you must have the correct set of access rights to perform the project operations. These access rights, specifically the project access rights, are defined by the TIMS3 administrator using tools provided by the TIMS3 Data Access Manager.

Creating Projects and Sub-projects

Projects and sub-projects are created using either the Projects > New command on the menu bar or the right click New > Sub-project popup menu command. In either case a project/sub-project is created under the currently selected project. When you create a project you must select the Project Security, define a project name and project storage location on the server. Projects cannot have spaces in their names, although their description can contain any descriptive text. The user will see the descriptive text as a tool tip whenever they hover the cursor over a specific project in the project tree.

Project Security defaults to Secure which is the normal type of TIMS3 project that provides check in/out secure access. Open projects allow everyone to document files stored on a common mapped drive location and access these files via the common Project Navigator interface. The difference between Open and Secure projects is that Open projects are directly accessed via the common network drive map letter, there is no check in/out with open projects. Open projects are used to bring other non-supported operating systems into the TIMS3 Document Management system, such as Novell and NFS mounted drives. Project Replica's require permission from a remote TIMS3 site to setup a Replica project. Replica projects allow a TIMS Manager to create a read-only copy of an entire project on a remote TIMS3 site.

Once the project is created the system will prompt you with the Project Properties dialog to fill in the project description and other details. It is important to leave the project Status set to Active to ensure that users can see the new project. Users will only see Active projects unless they have checked the view 'All Projects' option in their User Settings.

You will then be able to enter more information for this new project, such as the project description, manager, owner, and reference number. See the figure for more information. Note that the fields that are dimmed are the ones inherited from the master project.

TIMS v3.4 created a new concept in project definition called project type. Version 3.4 implements two project types 1) Secure and 2) Open. The use of Open projects is important for two reasons: 1) it allows existing server directory access to be mimicked inside TIMS3 for quick and easy setup to start using TIMS3 document management; 2) strategically placed Open projects interspersed within TIMS3 Secure projects can provide a way of logically organizing all Corporate data so it is easily accessible through one interface, Project Navigator. 

Replica projects, introduced in Version 3.5, provide a means of project collaboration across a WAN or Internet VPN. A replica project is a read-only project that is maintained in sync with a project stored on a separate TIMS3 site. The TIMS3 nightly cleanup, after performing its local network cleanup will then check for updates and new documents in all remote source project replicas.

 

Project Properties

Please visit the section on Project Types further on in the documentation for more details.

Project Properties

Project directories are stored on one or more TIMS3 file servers. Users don't normally need to know the directory and file server where project files are stored but incase your TIMS Manager has allowed you to create sub-projects you will need to know how to create and edit project/sub-project properties.

Note: Once a project is created you cannot change the TIMS3 file server Node on which it resides.

You can change certain informational items that describe the project in the TIMS3 database by selecting the project's properties in the pull-down or pop-up menus.

A form will be displayed showing in solid text the items that can be changed. The dimmed text (in light grey) show the items that cannot change using this function.

 

Moving, Deleting, Copying and Renaming Projects

Projects can be moved or copied simply be using drag-n-drop to move or copy the selected project to a new location. The default drag operation is Copy, confirmed by the cursor containing a C. The move operation simply requires the press and hold of the <shift> key while the drag operation is being done. The move cursor looks the same except it contains an M.

Project Delete Verification

Deleting projects is performed by selecting the project then either using the right click popup menu to select Delete or by simply pressing the DEL key. As a safety precaution, projects cannot be deleted without first deleting all the documents currently in the project. When you attempt to delete a project you'll be asked to confirm the action before the project information is removed from the TIMS3 database and the project folder is deleted on the file server.

If documents and/or files with no matching document records are currently in the project, TIMS3 will return with a message indicating that these files and/or documents should be deleted first before deleting the project.

Error deleting project

Rename a Project

Renaming a project can be performed by using the click popup menu to select Rename or by clicking a second time on the project name in the project tree:

When a project is renamed you are given the option of changing the server storage location (directory path). After project rename all documents in the project are moved to the new directory even if there are files checked out (no problem here) and the document default corporate ID is updated to reflect the new project name. If you choose Yes to rename the path a default path is provided based on the new project name and its parent project storage location.

   

 

File Transfer Operations

While you are in the file list view, you can right-click on a project folder to access a sub-set of the file transfer function. You may either check out, copy out or clean up the entire project that is selected. As shown in more detail in the next sections, the check out and copy out functions allow you to select whether reference files should be copied out or checked out automatically.