Has anyone given any thought to the ongoing monitoring of where we get the text (& graphics) for our modules from?
Important considerations: (a) conf files often contain a URL, but some of these are now broken links (b) "suppliers" may issue revisions or updates, but we have no means of knowing or being alerted As a result, our repos can become easily outdated, even though they were true and accurate at the time of module creation. For general web-page monitoring, there are or were excellent services such as http://www.changedetection.com/ http://www.changedetection.com/ . Is this still live? For finding broken links, we could use http://home.snafu.de/tilman/xenulink.html Xenu's Linksleuth , but first someone would have to generate a single page containing a table listing every module in one column, and the "supplier" URL (from the conf files) in another. Making one would be a simple task for a scripting techie. -- David -- View this message in context: http://www.nabble.com/Monitoring-the-sources-for-our-modules--tp25318901p25318901.html Sent from the SWORD Dev mailing list archive at Nabble.com. _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
