It would be straightforward to now define a full refresh job using the existing jobs and could be scheduled.
However at present it is useful to observe progress via the IATI.log in $existHome/ iati.log (sym link to webapp/WEB-INF/logs/IATI.log) . If the update procedure involves copying between servers, at present this is a manual task so full automation does not look possible.
It is also necessary to check new publishers particularly for the quality of their XML. The application does not attempt to validate activities not restrict update to validated activities only because it makes minimal assumptions about the document. However when rendering into HTML assumptions are made and these can be broken.
It would be straightforward to now define a full refresh job using the existing jobs and could be scheduled.
However at present it is useful to observe progress via the IATI.log in $existHome/ iati.log (sym link to webapp/WEB-INF/logs/IATI.log) . If the update procedure involves copying between servers, at present this is a manual task so full automation does not look possible.
It is also necessary to check new publishers particularly for the quality of their XML. The application does not attempt to validate activities not restrict update to validated activities only because it makes minimal assumptions about the document. However when rendering into HTML assumptions are made and these can be broken.