-
Projects
+
#logger.Projects#
- Projects not in this logger application instance which can be linked in:
+ #logger.lt_Projects_not_in_this_#
-
Variables
+
#logger.Variables#
-
Logger Application Instance
+
#logger.lt_Logger_Application_In#
-
Help
+
#logger.Help#
- The logger can track a number of variables in different projects.
+ #logger.lt_The_logger_can_track_# #logger.variables# #logger.in_different# #logger.projects#.
- A variable is something you wish to track, for example:
+ #logger.A# #logger.variable# #logger.lt_is_something_you_wish#
-
- Time spent (hours)
+ #logger.Time_spent_hours#
-
- Expenses (currency, USD, EUR, whatever)
+ #logger.lt_Expenses_currency_USD#
-
- Weight of goods shipped (lbs, kgs)
+ #logger.lt_Weight_of_goods_shipp#
-
- Your personal weight (lbs, kgs). Non-additive.
+ #logger.lt_Your_personal_weight_#
- Variables are shared between all projects, so that you can
- summarize the variable across projects. However, if you have many
- diverse projects going on, only certain variables will make sense
- for any given project, hence we let you map variables to
- projects.
+ #logger.Variables_are# #logger.lt_shared_between_all_pr##logger.lt__so_that_you_can____s# #logger.lt_map_variables_to____p#.
- Some variables will be additive, meaning that it makes
- sense to add them together and look at the total. An example of an
- additive variable is time spent. Others are non-additive,
- which means the opposite. Instead, you would typically average
- over them. An example is measuring your personal weight, or the
- account balance of your bank account. It doesn't make sense to add
- those numbers together, they're snapshots at a given point in
- time, and just because you check your account balance 10 times a
- day doesn't (necessarily) mean you're getting richer and richer.
+ #logger.lt_Some_variables_will_b# #logger.additive##logger.lt__meaning_that_it_make# #logger.non-additive##logger.lt_____which_means_the_o#
@@ -88,24 +76,13 @@
- You can mount multiple instances of the logger
- application. The projects you define are shared between all
- logger application instances, subject to the permissions you grant
- on them. Each instance of logger will be setup to display a
- certain subset of the projects available, as defined by the
- administrator of that instance.
+ #logger.lt_You_can_mount_multipl# #logger.lt_instances_of_the_logg##logger.lt__The_projects_you_def#
- An example of why this is useful is if you work for a company,
- which works on many different projects for different clients. In
- that scenario, you would mount a logger instance in your intranet,
- where people log the hours they spend on projects. Then if you
- want to give your clients access to your logs, you can mount an
- instance per client in the client's extranet area. These client
- loggers would only have access to the projects that pertain to the
- given client.
+ #logger.lt_An_example_of_why_thi#
+
Index: openacs-4/packages/logger/www/admin/project.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/logger/www/admin/project.adp,v
diff -u -r1.12 -r1.13
--- openacs-4/packages/logger/www/admin/project.adp 17 May 2004 15:15:21 -0000 1.12
+++ openacs-4/packages/logger/www/admin/project.adp 29 Jul 2005 23:05:06 -0000 1.13
@@ -9,26 +9,27 @@