Improvement of crawl jobs (data model and catalog)

AgnieszkaK

1. When one of the dates on the configuration page (repository or catalog) points to a day and time from the past, changing just one of them and saving the settings will cause an automatic start of the crawler for another one. It would be better if the configuration could be saved separately for each crawler. 
2. The input fields unfortunately do not work, the only effective way to change the time is to use the built-in calendar in the popup (icon to the right of the input field). 
3. Further runs even in the case of an unscheduled crawl should be planned using the specified configuration and not the time of the last one. It currently works in a different way, let us assume that according to our configuration both crawle should start at 8 a.m. every day. If one of the crawlers is automaticly started in the meantime (e.g. at 10 o'clock), its next run will not take place the next day at 8 o'clock (as it is still in the configuration), but at 10 o'clock. Thus, it is necessary to check every day whether an unscheduled run has taken place and, if so, to reconfigure the settings.