1 / 18

Retrofitting CMSs to support centralized ontologies

This document highlights the journey of retrofitting various Content Management Systems (CMSs) to support centralized ontologies. With numerous systems like WordPress, Drupal, and custom-built solutions in use, there is an increasing need for aggregating and managing diverse content efficiently. The study discusses the implementation of an ontology widget that can plug into existing CMSs, support heterogeneous data fields, and streamline the tagging process. Future enhancements include generating JSON objects and integrating RDFa standards to promote better content organization across web platforms.

vevina
Télécharger la présentation

Retrofitting CMSs to support centralized ontologies

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. Retrofitting CMSs to support centralized ontologies

  2. What we have • A lot of Content Management Systems • An increasing chance that future CMSs will be hosted off campus

  3. CMT Managed CMSs • Luwak • Homebuilt J2EE/XML CMS • Approx 30 sites • Hr, Library, FYE, Summer, Helpdesk, Public Safety…. • WordPress • approach.rpi.edu • Drupal • Approx 15 sites • MANE, CEE, Faculty, Alert, Provost

  4. Externally Managed Content • Sedexo • Athletics • Alerts

  5. Implemented An Aggregator • Aggregates RSS/ATOM (news) content • Curators pick which news items to promote • Drupal • Feeds • CCK • Views • Output for: mobile, desktop, email, digital signage …… whatever is next

  6. Organizing the data Deaggregation & widgets

  7. http://faculty.rpi.edu/news.php?person=rss/hendlj2 JS widget

  8. Tag Conventions • Kinda Suck • RCSids for tagging people • Consistent • Takes too long for the writers to look up the ID • Buildings, Depts • Inconsistent naming creates a mess

  9. Ontology Widget For CMSs • Plug into existing CMSs • Heterogeneous ontology space within CMSs • A drupal install may have a ‘person’ field • A WP install may only have a ‘tag’ field • Support multiple ontology widgets on a single page • Support multiple ontology pushed into a single field • Support pre-existing data on a form element

  10. How it works $(document).ready(function() { RPIbuildingstags("edit-taxonomy-tags-8", "http://morningmail.rpi.edu/buildings.js", "", ", "); }); HTLM form element to overload (central) ontology object Pre-tag delimiter Post-tag delimiter

  11. Native Form Element Form Element Overloaded Previously Added Building (click to remove) Input box Building Suggestion

  12. JSON Object • Supports multiple tags under a single common name • Adding VCC adds all three tags • Removing VCC removes them

  13. JSON Object Generation • CRON/PHP generates JSON object based on resources in a given folder • JSON object could be output from a more sophisticated ontology management system

  14. Future • Get data for a ‘People’ widget • Use similar central JSON Ontology to support an RDFa WYSIWYG editor for web based CMSs • Wikipedia people as data source • Web Sys Dev Spring ‘11 • http://lamp3.server.rpi.edu/ontology/buildings/demo.html

More Related