If the websites have some sort of syndicated feed, like RSS or Atom or
the like, it would be easy to write a basic script to pull the latest
info from that. Likewise if there is regular version information in a
web-accessible version of the file as well as the module's config file
on the lines of SourceVersion=1.7.6 or SourceDate=1999-10-06 or
something like that.
If that sort of information is not available in a structured way, then
tracking updates to the upstream material can become far more difficult.
--Greg
On Jan 13, 2010, at 7:37 AM, David Haslam <d.has...@ukonline.co.uk>
wrote:
Do we have any system in place to monitor for changes the websites
where our
module source texts from from?
e.g. When the text itself has been updated.
Or do we rely on ad hoc knowledge and reporting by interested
volunteers?
David
--
View this message in context:
http://n4.nabble.com/Watching-websites-where-our-source-texts-come-from-tp1013006p1013006.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
_______________________________________________
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
