jirikadlec2[CodePlex] Right now when I register a service as a normal user I must wait a few days before the service is harvested.
Only a special quotadministratorquot user can start the data harvest.
The few-days delay is a barrier for users who want to make their service appear quickly in the catalogue.
Please add a new quotrun data harvestquot button to the users web service details page under quotmy data service.quot
When user clicks quotrun data harvestquot, start the harvest and show a link to the harvest log.
Also for each service registered by the user show a quotharvest historyquot option where the user can view the past harvest logs and whether they were successful or not.
I understand that running a quotdata harvestquot for a very big service with tens of thousands of sites is resource-intensive. So perhaps you could limit the user-launched quotrun data harvestquot option for data service with less than 1000 sites.
jirikadlec2[CodePlex]
Right now when I register a service as a normal user I must wait a few days before the service is harvested.
Only a special quotadministratorquot user can start the data harvest.
The few-days delay is a barrier for users who want to make their service appear quickly in the catalogue.
Please add a new quotrun data harvestquot button to the users web service details page under quotmy data service.quot
When user clicks quotrun data harvestquot, start the harvest and show a link to the harvest log.
Also for each service registered by the user show a quotharvest historyquot option where the user can view the past harvest logs and whether they were successful or not.
I understand that running a quotdata harvestquot for a very big service with tens of thousands of sites is resource-intensive. So perhaps you could limit the user-launched quotrun data harvestquot option for data service with less than 1000 sites.