Pre-populate Date and Time field

pwolanin, How do you think dates should work with node clone ideally? Should it be the dates from the old-node (like the OP suggests) or the current date and time? Or do you have something else in mind.

Personally I feel (maybe in a separate module?) ideally dates would be calculated based on rules and when you clone a node it would clone it based on those rules. When it comes to calenders most people think of things in terms of "1st and 3rd Sunday of the month". So I'm thinking a widget for the date module that allows people to input that information and have it calculate the specific date for that month and then some kind of rule for the node clone module that means that the rule is cloned but the actual date is calculated again for the new month that the old node is cloned to.

What do you think? We're developers so we're happy to build this stuff, its not a feature request. But I'm interested if what I'm talking about fits in with something node clone could do?

I'm also going to investigate re-occuring dates that the date module has but I've used it before and I think there are a number of reasons why cloning some event content types is better then reoccurring dates.

If required I'm happy to make a separate issue rather then hi-jack this issue.

Perhaps these assumptions cannot be made by the module, since it depends on every installation.
You can use the hooks provided by the module, as described in the documentation and in #1256478: API Documentation for hook_clone_node_alter()

Yeah, this seems like very site specific logic. When I clone something it's usually to make a "new" version that should have the current time.