1 / 15

Information Exchange in CHM Portals

CHM portals syndicate and expose various content types via RDF and ATOM feeds, including news, events, stories, and uploads. Administrators can define and display local and remote feeds, and customize filters to narrow down the information. The system supports RSS, RDF, and ATOM formats, with internationalization and support for multiple content types. Further improvements include generating and exchanging dedicated feeds, filtering by type, language, and geographical coverage, and exchanging data about experts and organizations.

ltatum
Download Presentation

Information Exchange in CHM Portals

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Information exchange in CHM portals Rania Spyropoulou Miruna Bădescu

  2. Current status • CHM portals syndicate all the content types and expose them via RDF and ATOM • Most used feeds are: • latest news • upcoming events • selected stories • latest uploads

  3. Expose feeds Administrators define the local channels: • Define what channels are relevant for the portal from Administration -> Syndication -> Local channels • A default set of local channels is available when the portal is created

  4. Inspect available feeds • Portal visitors see the local channels exposed by each CHM portal clicking on the feed icon in the browser: • in Firefox • in Internet Explorer

  5. Display remote feeds • To visualise remote feeds in a CHM portal, administrators need to: • Obtain the feed URL • Access the Administration -> Syndication -> Remote channels page and create a new remote channel and a portlet for it • Click ‘Update now’ to fetch the information • Place the portlet somewhere in the portal • The system then updates the feed on regular basis (e.g. once a day)

  6. Feed formats in CHM sites • Depending on the format, a feed contains a set of attributes (e.g. title, description, language, link, coverage) for each entry • CHM portals support: • RSS – “really simple syndication” • RDF – contains the Dublin Core element set • ATOM – a more detailed and feature-rich format • support for internationalization • does not allow mistakes in creating it • is able to understand multiple content types of the description: HTML, plain text, files, etc.

  7. What next? • We can generate and exchange other types of feeds, dedicated to a certain subject: technology transfer, indicators, genetic resources, etc. • We need to be able to filter by: • type • language • geographical coverage • other attributes, based on the local needs

  8. What’s needed to accomplish that? • Fill in the geographical coverage and keywords fields from multilingual glossaries • Build dedicated glossaries and translate them in each language of the active CHM portals • Create local channels in the appropriate language(s) • Specify filters to narrow down the context: e.g. language, coverage, type, keywords • Pick up similar channels from all CHM portals and create remote channels or an aggregated channel • Use the available filters to narrow down the information you want: e.g. language, coverage, type, keywords

  9. Improvements to the system • With just small adjustments to the software, dedicated channels (feeds) can be built and shared • Automated scripts can facilitate indexing multiple items with the same words: • e.g. all the items in a folder can inherit the folder’s keywords or have the same coverage • automatic discovery of the keywords and coverage from the text • The feeds exposed by the CHM community can be shown in a central network registry, grouped by type and language

  10. Exchanging data about experts, organisations and contact information Case study:

  11. Looking for the right formats • Success factors in identifying the standard to follow: • Common machine readable formats (syntax and semantics) supported by • Critical mass of users as well as • Enabling technologies to solve practical use cases

  12. FOAF or “friend of a friend” • Acronym for • Technology that makes it easier to: • share and use information about people and their activities • share and use information about organisations and records of people’s affiliations to them • transfer information between Web sites and to automatically extend, merge and re-use it online • RDF-based => easy to harvest and aggregate • Recommended by the ExpertFinder initiative http://wiki.foaf-project.org/ExpertFinder

  13. FOAF terms

  14. Issue to face • Identifying widely agreed and usable vocabularies and taxonomies to use for expertise annotation • use the Naaya Glossary to hold the data • provide translations

  15. Conclusion • Providing we agree on a common standard for syndicating experts, organisations and their links: • each CHM site will have content types for Expers and Organisations and will provide an XML-based export • Other applications can pick up this data and display it locally • It will be possible to have an overview and search of experts and organisations at regional or global level

More Related