http://wiki.radiotime.com/ 2008-12-02T09:32:50-06:00 http://wiki.radiotime.com/ http://wiki.radiotime.com/lib/images/favicon.ico text/html 2008-11-10T14:22:38-06:00 Thomas Hutchings http://wiki.radiotime.com/doku.php?id=dev:doc:openmedia:start&rev=1226348558&do=diff1226348558 The OpenMedia API is a web service complement to our lightweight, browse-oriented OPML interface. It is a collaborative specification pioneered by Sonos, Inc. and adapted to radio by RadioTime. It officially launched in October 2008 and supports hundreds of thousands of connected devices across the globe. text/html 2008-11-08T20:38:40-06:00 Thomas Hutchings http://wiki.radiotime.com/doku.php?id=dev:doc:home&rev=1226198320&do=diff1226198320 Developer FAQ OPML OPML is a simple XML-over-HTTP service optimized for browsing the RadioGuide. * Getting started with OPML OpenMedia The OpenMedia API is a document-oriented web service optimized for browsing the RadioGuide. * Open Media Technical Overview text/html 2008-10-14T16:02:40-06:00 Bill Moore http://wiki.radiotime.com/doku.php?id=cms:radiomill:cms_daily_guide_station&rev=1224018160&do=diff1224018160 Purpose: Monitor for problem stations Process: Distribution: cmsstation@radiotime.com Responsible: Frequency: Daily Typical count: 300 items Interior Sections: *Dupe stations* These active stations were marked as dupes and have been disabled. text/html 2008-10-14T16:00:17-06:00 Bill Moore http://wiki.radiotime.com/doku.php?id=cms:radiomill&rev=1224018017&do=diff1224018017 Using RadioMill * Feedback and Admin Task Reports Station Processes * Station acquisition rules * Stream acquisition rules * Updating streams in RadioMill * Station duplicates * Station region fix * Station country fix * External station sources text/html 2008-10-11T23:32:27-06:00 Bill Moore http://wiki.radiotime.com/doku.php?id=cms:radiomill:cms_repeater_consolidation&rev=1223785947&do=diff1223785947 Purpose: Show nearby repeaters that are being automatically removed Process: One removed if within 20 miles of the other or same city. Review for any obvious errors and sense of problems Distribution: cms@radiotime.com Responsible: Admin assigned to the country text/html 2008-10-11T23:14:20-06:00 Bill Moore http://wiki.radiotime.com/doku.php?id=cms:radiomill:cms_stream_monitor&rev=1223784860&do=diff1223784860 Purpose: Warn for important stream failures during the day Process: The tester will automatically disable any marked “Fatal” (usually means a bad URL), but otherwise leave them alone Distribution: cms@radiotime.com Responsible: Manually assigned text/html 2008-10-11T20:48:36-06:00 Bill Moore http://wiki.radiotime.com/doku.php?id=cms:radiomill:cms_daily_guide_program&rev=1223776116&do=diff1223776116 Purpose: Monitor program data integrity and catch problems Process: Distribution: cmsprograms@radiotime.com Responsible: Program admin Frequency: Daily Typical count: 150 items Issues: * Define tasks or specific responsibility * Create alternative for finding/fixing game collisions for a season. text/html 2008-10-11T20:41:34-06:00 Bill Moore http://wiki.radiotime.com/doku.php?id=cms:radiomill:cms_schedule_import&rev=1223775694&do=diff1223775694 Purpose: Monitor updates applied from PRF source Process: Distribution: cms@radiotime.com Responsible: Manually assigned Frequency: Weekly, Sun 1am? Typical count: 100 items Tasks: New and updated programs assigned as tasks Issues: * Manually add unmapped stations and assign update/dedupe task text/html 2008-10-11T20:35:41-06:00 Bill Moore http://wiki.radiotime.com/doku.php?id=cms:radiomill:cms_fcc_validation&rev=1223775341&do=diff1223775341 Purpose: Review and resolve problems from new FCC data update Process: Distribution: cms@radiotime.com Responsible: Manually assigned Frequency: Manually run Typical count: 2000 items Issues: Interior Sections: *Updated mapping* Found a better region match