Website interoperability

From smultron.org

Jump to: navigation, search

see: https://wiki.sourcefabric.org/display/CC/Ideas+on+Airtime-Drupal+Interoperability

Process-centred data storage

A major problem at Reboot.FM as it is today, is that the same data has to be input several times through different interfaces, and sometimes manually converted. This is the case for audio file metadata, schedules and playlists,

Looking at the data flows inside the Reboot.FM system (http://ourproject.org/moin/projects/rsdoc/reboot_system_dfd), it is apparent that the system lacks a unified data repository. This is a classic problem aka the 'Silo Concept'. Each of the subsystems used in the Reboot.FM workflow uses it's own data mapping. This mapping is the product of the logical structure of the data in each subsystem, which is itself the product of different needs and design decisions in each individual process. For example: Wordpress stores playlist data in it's database, but the same data is copied (manually) in ID3 tags and coded in the audio file name. The Silo Concept leads to fragmented data storage and poor communication between components.

Personal tools