retrofitting cmss to support centralized ontologies

18
Retrofitting CMSs to support centralized ontologies

Upload: vevina

Post on 14-Feb-2016

38 views

Category:

Documents


0 download

DESCRIPTION

Retrofitting CMSs to support centralized ontologies. What we have. A lot of Content Management Systems An increasing chance that future CMSs will be hosted off campus. CMT Managed CMSs. Luwak Homebuilt J2EE/XML CMS Approx 30 sites Hr, Library, FYE, Summer, Helpdesk, Public Safety…. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Retrofitting CMSs to support centralized  ontologies

Retrofitting CMSs to support centralized ontologies

Page 2: Retrofitting CMSs to support centralized  ontologies

What we have

• A lot of Content Management Systems• An increasing chance that future CMSs will be

hosted off campus

Page 3: Retrofitting CMSs to support centralized  ontologies

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

Page 4: Retrofitting CMSs to support centralized  ontologies

Externally Managed Content

• Sedexo• Athletics• Alerts

Page 5: Retrofitting CMSs to support centralized  ontologies

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

Page 6: Retrofitting CMSs to support centralized  ontologies
Page 7: Retrofitting CMSs to support centralized  ontologies
Page 8: Retrofitting CMSs to support centralized  ontologies

Organizing the data

Deaggregation & widgets

Page 9: Retrofitting CMSs to support centralized  ontologies
Page 10: Retrofitting CMSs to support centralized  ontologies

http://faculty.rpi.edu/news.php?person=rss/hendlj2JS widget

Page 11: Retrofitting CMSs to support centralized  ontologies

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

Page 12: Retrofitting CMSs to support centralized  ontologies

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

Page 13: Retrofitting CMSs to support centralized  ontologies

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

Page 14: Retrofitting CMSs to support centralized  ontologies

Native Form Element

Form Element Overloaded

Previously Added Building (click to remove)

Input boxBuilding Suggestion

Page 15: Retrofitting CMSs to support centralized  ontologies

JSON Object

• Supports multiple tags under a single common name

• Adding VCC adds all three tags• Removing VCC removes them

Page 16: Retrofitting CMSs to support centralized  ontologies

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

Page 17: Retrofitting CMSs to support centralized  ontologies
Page 18: Retrofitting CMSs to support centralized  ontologies

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