You are currently browsing the category archive for the ‘content distribution’ category.
Continuing business plan. Need to define final output to subscribers and then work backwards from that to code up data manipulation and database(s) structure.
Want to give subscribers something where info is aggregated and tagged/categorised so that it can be scanned quickly and interesting new items picked out for follow up. Call this a “full data view”
Everything in database, generate a full data view from database via user generated action.
Advantages – Intrinsic flexibility of ways of viewing data, minimises user management overheads (alerting lists etc.)
Disadvantages. Subscriber will forget to check, won’t use much, won’t re-subscribe. Not re-assuring to subscriber that there is no “permanent” format to keep should Scibella (an unknown new start up) fail. Technically, query structure for hundreds of item could take annoying time to build up on screen. Repeated queries for same month could occur (user would have to re-run over web every time) . Bandwidth quota issues for Scibella with host ISP?
Generate a stand-alone full data view file that gets sent out to subscribers. Users archive and read over organisation intranet or on local device.
Advantages – permanent output held by user on local PC or intranet. Access /Query times would be faster than web only access.
?? would item by item database(s) (15000 project records a year) be needed at all. CMS database(s) could be a lot simpler.
Disadvantages – Flexibility of viewing, this approach “freezes” data format. Copyright management – files could be transferred to non-subscribers etc.
Technically, what would be size of files. Peak bandwidth/ISP reliability issues as files are pushed out. Non-receipt issues (anti-spam filters in subscriber organisations etc.)
Hybrid push pull variants
Set up email/rss alert that new full data view is available for download from Scibella (embed link to data download)
As above but also TOC that links back to full view of item in database -this assumes database(s) containing project info.