localendar Forums Homepage


Print at Aug 24, 2025, 6:56:47 PM

Posted by mygig at Feb 19, 2009, 10:55:44 AM
Re: Knowing who is adding events
 
 
Just to be clear; having the owner name wouldn't solve the problem of an event being "rejected", because no record would be stored. If the event isn't retained, the owner name would be lost as well.

I am fine suggesting a "Contributor Contact" address on the Event Add form. The questions are:
1. Should this be visible only to the calendar owner?
2. Should it be a required field?

Naturally, even if it is required, some people will still fill it w/ bogus information.


Even if a bogus e-address was entered on occasion by the poster, it would still be better to have it for contact and clarification purposes for missing, confusing etc. info on the event in cases where the address is valid.

On receipt of the normal system message notifying me of an event that is sent to my e-address from Localendar, if it has the e-address of the poster, whether valid or bogus, all I would do is send an e-mail via my normal provider to the e-address given to let the poster know there is a problem with the posting. Then I would either get clarification from the poster and make the adjustment or the poster could him or herself. In the case of a bogus address, I would receive a report via my provider that it was invalid and simply delete. the event.

For my purposes, it need be visible only to the calendar owner and it should it be a required field.


I just received six notifications that events had been added to my calendar, likely by the same contributor on examining the content and the approach.

All events appear valid, but in each case there was no indication of the time of the event nor any detail in the Description.

Without the e-mail of the poster, I have no way to follow up on these postings nor to provide guidance to whoever posted the events.

Incidentally, it appears that they were posted using the Add Event button at the bottom of the calendar, so at least THAT was working in this case.

Help! | Cobranding | Legal | Privacy Policy | About localendar.com | Contact Us