More Related Content Similar to Co-Editing Complex Documents from Alfresco Share (20) More from Jeff Potts (20) Co-Editing Complex Documents from Alfresco Share1. CoEditing Complex Documents atop
Alfresco: Integrating EdYT with Share
Jeff Potts
jpotts@metaversant.com
Rocky Kahn
rocky@teampatent.com
2. © Copyright 2010, Metaversant Group, Inc. | http://www.metaversant.com
EdYT: Browser-Based CoEditor
Like Google Documents (real-time browser-based co-editor) plus:
•Validating, Autocompleting, Crosslinking
•Compound document support
•Run on premises
3. © Copyright 2010, Metaversant Group, Inc. | http://www.metaversant.com
Making Systems of Record
“Engaging”
Ad hoc emails, spreadsheets, MSWord docs live in unstructured
space ("S-drive") between Systems of Record and Systems of
Engagement.
Currently, only the existence of these documents can drive
workflow but nothing inside the documents is structured, limiting
automation & discoverability.
EdYT intuitively provides structure within otherwise free-form
documents.
4. © Copyright 2010, Metaversant Group, Inc. | http://www.metaversant.com
Example 1: TeamPatent
• TeamPatent is an example of EdYT applied to Patent
Preparation and Examination:
• Customer: US Patent & Trademark Office
• Historical IT budget: $125m
• Project Scope: Replace entire IT system
• Significance: Profound
5. © Copyright 2010, Metaversant Group, Inc. | http://www.metaversant.com
USPTO Characteristics
• 6250 patent examiners
• Valuable work product
• Labor-intensive examination process and enormous
backlog yet consistent inability to catch up
• Commodity approaches rejected by stakeholders
resulting in repeated IT development failures
6. © Copyright 2010, Metaversant Group, Inc. | http://www.metaversant.com
Patent system overhaul drivers
• Recognition at very top of our admin that innovation is incredibly
important to our country and to the world; that innovation is the
only sustainable source of competitive advantage; that the US is
an innovation-driven economy; and that innovation creates
jobs. And therefore the USPTO, which is an agency which
protects innovation--in fact it's THE agency that protects
innovation--is a jobs agency. The secretary of commerce…has
given me a mandate to blow up anything I need to in order to fix
the USPTO and the US patent system.
7. © Copyright 2010, Metaversant Group, Inc. | http://www.metaversant.com
Complex Structure
There are several types of relations woven through a patent
application:
•350 numbered references (e.g. "axis 20")
•150 callouts in 12 drawings
•130 unnumbered terms (e.g. "rotation axis")
•30 figure references (e.g. "FIG. 1")
•29 claim references (e.g. "claim 1")
•TOTAL: ~700 references
8. © Copyright 2010, Metaversant Group, Inc. | http://www.metaversant.com
Example 2: Junit
Cloud-based journalism service allowing journalists,
photographers, and editors to co-edit articles and manage
workflow.
9. © Copyright 2010, Metaversant Group, Inc. | http://www.metaversant.com
Example 3: Electronic Medical
Records
• Medications (e.g. “Adderall 15mg TID-aiD”, “Adderall XR 20mg
qD”)
• Diagnoses (e.g. “Major depressive disorder, currently in major
depressive episode panic disorder with agoraphobia, attention
deficit hyperactivity disorder 29633”)
• Symptoms (e.g. “anxiety 7/10”)
10. © Copyright 2010, Metaversant Group, Inc. | http://www.metaversant.com
High-Level Architecture
EdYT
Document Collaborators
cmislib
Checkout/che
ckin
11. © Copyright 2010, Metaversant Group, Inc. | http://www.metaversant.com
Create TeamPatent Doc
• Extend content manager
client-side JS
• Extend toolbar webscript
• Set icon, form ID
12. © Copyright 2010, Metaversant Group, Inc. | http://www.metaversant.com
Create TeamPatent Doc Form
• Share form config
– Includes hidden field to force a
“marker” aspect
• Custom form filter
– Sets mimetype
– Defaults content to empty
XHTML
– Automatically check out
document
13. © Copyright 2010, Metaversant Group, Inc. | http://www.metaversant.com
Edit/Join in TeamPatent
• Extend document list
• Extend document details
• In both cases, extension:
– Adds custom UI action to the action config
list
– Specifies “fake” permission, “teampatent-
edit”
– Adds a TeamPatentComponent client-side
JS instance
• Client-side JavaScript:
– Invokes a repo-tier web script to get a fresh
ticket
– Builds a form on the fly and POSTs it to
TeamPatent service
14. © Copyright 2010, Metaversant Group, Inc. | http://www.metaversant.com
Locked Banner
• Extend the path component
• Client-side JavaScript
decides what message to
display
15. © Copyright 2010, Metaversant Group, Inc. | http://www.metaversant.com
EdYT Browser-based Editor
16. © Copyright 2010, Metaversant Group, Inc. | http://www.metaversant.com
Resources
– http://incubator.apache.org/chemistry/
– OpenCMIS
– cmislib
– PHP CMIS Client
17. © Copyright 2010, Metaversant Group, Inc. | http://www.metaversant.com
EdYT Roadmap
• 508-Compliance
• Additional browser/mobile support
• Enhance reviewing capabilities
• Enhanced co-editing features
• Enhanced cross-references
• Modularization
18. © Copyright 2010, Metaversant Group, Inc. | http://www.metaversant.com
Calls to Action
1. Work for EdYT
2. Work with EdYT
3. Build EdYT into Alfresco
19. THANK YOU!
Tweet me with questions/feedback @jeffpotts01
Get up to speed and stay informed
with Alfresco news, tips, & tutorials!
rocky@teampatent.com
Editor's Notes In this session, we'll premier EdYT, a browser-based Alfresco co-editing extension, providing automation and validation for complex documents. To explain the automation and validation features, we'll demonstrate TeamPatent, a service built atop EdYT for the United States Patent & Trademark Office (USPTO). We'll then discuss how one may build new services upon the platform and Jeff Potts will lead a discussion of integration design patterns for authentication/permissions and CMIS.
In a typical patent, US6911012, there are 350 numbered references (50 unique), 150 callouts in twelve figures, 30 figure references, and 130 unnumbered terms in 29 claims, for a total of ~700 relations. Highly-paid patent experts spend countless hours attempting to ensure relations are used consistently yet frequently miss inconsistencies.