lawquest,
We are currently using ETM in a multi-user environment by leveraging
ETM plain text files and a version control system (such as
Subversion). We are able to see shared calendar items as well as log
time and generate reports of time for one or more people. It has been
working pretty well for over a year now. The version control system
also provides a permanent, traceable history of every change to
calendars and time logs and can be used for making and archiving
billing reports as well.
Our basic file structure looks like this:
- etm data directory
| personal task files calendar items, etc.
| shared data
| shared calendars
| time logs
Everything in the shared data directories and below is part of a
version control system. Each person puts their time entries in a file
dedicated to them (e.g. actn_xyz.text where 'xyz' is person's
initials). We have a company calendar file as well a user-specific,
shared calendar files in the shared calendar folder. Each time a
calendar item is modified, the file is committed to the version
control system and other people can update and see it immediately. At
least once at the close of each month, everybody commits their final
monthly time logs, which can then also be seen by everyone after they
update. Even if two people modify the same calendar file (i.e. the
company calendar), the version control system is able to merge the
changes together in most cases because they are plain text. There is a
permanent history of all of these changes. For example, we could go
back to a calendar from 9 months ago if we needed to, or we could find
a time entry error from 6 months ago if there was some question.
The personal area is where you can keep your tasks or other personal
calendar items that you don't need to share with others. Using filters
on files, such as '-f !calXYZ', allows you to hide items from other
people that you don't care to see all the time. At the same time, a
single person is able to roll up the action entries of any person or
group of people for billing/accounting purposes. Because of the unique
files that each person uses for action entries, we don't need to use
the @U user field in our entries.
Hopefully this helps give you an idea how we have set up ETM for a
multi-user environment. We are in a virtual office as well, so we are
all located in different places yet are able to share information
seamlessly.