WORKSHOP ON INFORMATION SYSTEMS  ARCHITECTURES Information / software architectures based on Content Management Systems (C...
CMS + external sources  + commodity services <ul><li>AgriFeeds  (www.agrifeeds.org) </li></ul><ul><li>Information architec...
AgriFeeds architecture Organization Regional network news  events news events website website harvesting metadata filterin...
Example: Upcoming Forestry Events
Item level: semantics come from the sources Future versions: automatic indexing with controlled vocabularies
Feed level: semantics come from the system
Advantages <ul><li>Information architecture : </li></ul><ul><ul><li>Relevant contents are stored and indexed without human...
Challenges <ul><li>Information architecture : </li></ul><ul><ul><li>Depends ( partially: the basic functionalities rely on...
CMS as integrated solution <ul><li>AgriDrupal (http://aims.fao.org/community/group/agridrupal) </li></ul><ul><li>Informati...
CMS for specialized functions Through an extended use of metadata and workflows, a CMS can perform the functions of specia...
Advantages <ul><li>Information architecture : Both external and local contents managed through metadata models and content...
Challenges <ul><li>Information architecture : </li></ul><ul><ul><li>Depends ( partially)  on the availability of good sour...
Upcoming SlideShare
Loading in …5
×

Information / software architectures based on Content Management Systems (CMS)

1,840 views

Published on

Presented at the WORKSHOP ON INFORMATION SYSTEMS ARCHITECTURES held on 25th April 2010 as a side event of the IAALD 13th Congress in Montpeller, France, 26-29 April 2010.

Information on the workshop:
http://aims.fao.org/events/ciard-workshop-information-systems-architectures-iaald-2010

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,840
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
32
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Information / software architectures based on Content Management Systems (CMS)

  1. 1. WORKSHOP ON INFORMATION SYSTEMS ARCHITECTURES Information / software architectures based on Content Management Systems (CMS): some examples with Drupal Valeria Pesce (GFAR) IAALD 2010 side-event SupAgro, Montpellier, France 26 April 2010
  2. 2. CMS + external sources + commodity services <ul><li>AgriFeeds (www.agrifeeds.org) </li></ul><ul><li>Information architecture : </li></ul><ul><ul><li>individual sources </li></ul></ul><ul><ul><li>“ commodity services” </li></ul></ul><ul><li>Software architecture : </li></ul><ul><ul><li>CMS to harvest, store and manage content </li></ul></ul><ul><ul><li>CMS + custom code for advanced filtering and custom feeds </li></ul></ul><ul><ul><li>“ Commodity services”: feed generators like Feedburner, Google API for calendars, widgets exploiting the APIs of various popular RSS readers </li></ul></ul> Processing  - search/display - sources  commodity services
  3. 3. AgriFeeds architecture Organization Regional network news events news events website website harvesting metadata filtering AGGREGATED VIEW FeedBurner Commodity services CMS
  4. 4. Example: Upcoming Forestry Events
  5. 5. Item level: semantics come from the sources Future versions: automatic indexing with controlled vocabularies
  6. 6. Feed level: semantics come from the system
  7. 7. Advantages <ul><li>Information architecture : </li></ul><ul><ul><li>Relevant contents are stored and indexed without human intervention </li></ul></ul><ul><ul><li>Metadata standards are exploited </li></ul></ul><ul><li>Software architecture : </li></ul><ul><ul><li>No need to write code from scratch </li></ul></ul><ul><ul><li>No need to maintain code: relies on an active community of developers </li></ul></ul>Complies with good practices in IM: re-use, re-usability, re-packaging, use of standards
  8. 8. Challenges <ul><li>Information architecture : </li></ul><ul><ul><li>Depends ( partially: the basic functionalities rely on the CMS ) on the functioning and continued availability of the commodity services </li></ul></ul><ul><ul><li>Quality depends on the quality of the sources </li></ul></ul><ul><li>Software architecture : </li></ul><ul><ul><li>Relies on the continued maintenance of the CMS </li></ul></ul><ul><ul><li>The custom code needed to extend the basic CMS functionalities needs to be maintained </li></ul></ul>1st version: 30% custom code  2 nd version: 15% custom code  NEXT VERSION: >> 1% CUSTOM CODE
  9. 9. CMS as integrated solution <ul><li>AgriDrupal (http://aims.fao.org/community/group/agridrupal) </li></ul><ul><li>Information architecture : - external sources - locally managed contents </li></ul><ul><li>Software architecture : </li></ul><ul><li>CMS to manage any kind of information using any metadata set </li></ul><ul><li>CMS to interface web services, APIs, RDF, XML… </li></ul> Coherent management  metadata Model / content model - search/display - exports CMS as an “information management tool” CMS as an “information hub” CMS as a pool of specialized solutions
  10. 10. CMS for specialized functions Through an extended use of metadata and workflows, a CMS can perform the functions of specialized software. Example of document repository management in Drupal
  11. 11. Advantages <ul><li>Information architecture : Both external and local contents managed through metadata models and content models  flexibility and adaptability to standards </li></ul><ul><li>Software architecture : </li></ul><ul><ul><li>No need to write code from scratch </li></ul></ul><ul><ul><li>No need to maintain code: relies on an active community of developers </li></ul></ul><ul><ul><li>One tool to manage everything </li></ul></ul>
  12. 12. Challenges <ul><li>Information architecture : </li></ul><ul><ul><li>Depends ( partially) on the availability of good sources </li></ul></ul><ul><ul><li>Common vocabularies are needed </li></ul></ul><ul><li>Software architecture : </li></ul><ul><ul><li>Relies on the continued maintenance of the CMS </li></ul></ul><ul><ul><li>Functionalities limited to the functionalities of the CMS </li></ul></ul><ul><ul><li>The custom code needed to extend the CMS functionalities needs to be maintained </li></ul></ul><ul><ul><li>Specialized functions will not be as specialized as in specialized software </li></ul></ul>

×