1) The list of Person documents may be large, although I think you are already iterating over all of the person documents.
2) The names may change but the Person document may not (such as during a marriage / divorce / etc) -- so we probably should track the person document UNID along with the name, so we can be certain as to what has changed for a given Person Document UNID in the update comparison.
3) This will extend the time the DominoMeter instances take to upload data to the DUCA.nsf
4) We need for the log to simply state who has been added and removed. We probably need a way to just see end user related log entries - so if they don't already, the log entries probably need a 'type' of some kind added.
5) I suggest a Rich Text Field on the Server collection document in DominoMeter that is of the format:
1) The list of Person documents may be large, although I think you are already iterating over all of the person documents.
2) The names may change but the Person document may not (such as during a marriage / divorce / etc) -- so we probably should track the person document UNID along with the name, so we can be certain as to what has changed for a given Person Document UNID in the update comparison.
3) This will extend the time the DominoMeter instances take to upload data to the DUCA.nsf
4) We need for the log to simply state who has been added and removed. We probably need a way to just see end user related log entries - so if they don't already, the log entries probably need a 'type' of some kind added.
5) I suggest a Rich Text Field on the Server collection document in DominoMeter that is of the format: