Content Services - PowerPoint PPT Presentation

About This Presentation
Title:

Content Services

Description:

The TC process will determine the REAL requirements, features, interfaces, ... Primary difficulty is the impedance mismatch between specialist CM functions and ... – PowerPoint PPT presentation

Number of Views:36
Avg rating:3.0/5.0
Slides: 10
Provided by: rda81
Category:

less

Transcript and Presenter's Notes

Title: Content Services


1
Content Services
  • Ron Daniel Jr.
  • Standards Architect
  • rdaniel_at_interwoven.com

2
Outline
  • Purpose
  • Suggested Requirements
  • Suggested Features
  • Suggested Architecture
  • Suggested Interfaces

3
Disclaimer
  • The following requirements, features, interfaces,
    are simply some suggestions for the WSRP TC
  • The TC process will determine the REAL
    requirements, features, interfaces,

4
Purpose - What is the problem WSRP istrying to
solve?
  • Overall problem managing content in Portals
  • Content Management Functions
  • Creation, Versioning, Workflow, Enhancement,
  • Portals imply
  • Broad user base, many tools, formats,
  • Considerable content, sorting wheat from chaff?
  • Problem yes, in-scope ?
  • Primary difficulty is the impedance mismatch
    between specialist CM functions and broad user
    base
  • Secondary issue is technical - how to interface
    between portal servers and content management
    services

5
Suggested Requirements
  • Users must be able to
  • View list of tasks and respond to them
  • Editing content or simply approving
  • Surf edit portal content
  • Add, delete, edit content (files and forms) from
    CM portlet/gadget
  • Tag content with metadata
  • Sophisticated merging of content versions is an
    anti-requirement
  • Web service architecture is TCs chartered
    purpose (WSDL, SOAP, XML, HTTP, Motherhood, apple
    pie, )

6
Suggested Features
  • For ease-of-use, the repository should look like
    a file system
  • Wide variety of file formats must be supported
  • Locking functionality should allow
    exclusive-write in order to avoid complex merging
  • Permissions appropriate to users role

7
Suggested Architecture
Content Services
Portal Content
Updated Content
Content Deployment
(Virtual) File System
Workflow Specifications and Active Jobs
Metadata
Web/ Apps/ Portal Server
SOAP Request
CS Server Stubs
Data Entry Forms and Captured Data
SOAP Response
Metadata
Vendor Extensions through URLs
Users, Groups, Roles
8
Suggested Interfaces
  • File Management
  • List directory, read/write/delete file, bulk file
    import, get file info, get/set metadata,
  • Workflow
  • newTask, getTasks, updateTask, finishTask,
    removeTask,
  • Collaboration
  • Edit file, submit, undo changes, synch,
  • Data Entry
  • listForms, submitForm, updateRecord,

9
QA
Write a Comment
User Comments (0)
About PowerShow.com