Transaction documents and digital assets: new challenges of the 2.0 era

1. GILBANE
San Francisco
Content Convergence
Transaction documents and digital assets:
new challenges of the 2.0 era
Eric Barroca Gilbane Conference
4th June 2009
eb@nuxeo.com San Francisco, CA

2. Who am I?
CEO of Nuxeo
open source ecm software vendor
global presence: US / EU / MEA
leading open source ecm platform
Long-time open source advocate
Working with content for 10 years
email: eb@nuxeo.com corporate: nuxeo.com
twitter: @ebarroca developers: nuxeo.org
blog: blogs.nuxeo.com/ebarroca community: linkedin - forums

3. from wikipedia...
transaction document: Transaction documents refers to legally
relevant documents that are either printed, inserter and mailed, or
electronically presented.[1] They consist of a mixture of fixed and
variable data.
digital asset: Digital Asset: A digital asset is any form of content
and/or media that have been formatted into a binary source which
include the right to use it. A digital file without the right to use it is not
an asset. Digital assets are categorised in three major groups which
may be defined as textual content (digital assets), images (media
assets) and multimedia (media assets); (van Niekerk, A.J. 2006)

4. digital transaction
assets documents

5. Logos Purchase Orders
Diagrams Invoices
Specifications Memos
Contracts Terms Contracts
Blueprints Fin. Statements
Slides Admin docs
Photos Tax declaration
R&D docs Delivery order
... ...
digital transaction
assets documents

6. vs.
digital transactional
assets documents

7. R IP
OU vs.
DY
H OL
digital transactional
assets documents

8. R IP UR N
OU vs. YO U
DY KE S R
H OL MA NES
SI
BU
digital transactional
assets documents

9. the link?

11. CONTENT!

12. is this specific?
library services search & browse
browse & view publish to the web
extract metadata annotate content
classify distribute content
share & collaborate enforce access rights
apply processes convert formats
manage lifecycle ...

13. is this specific?
library services search & browse
browse & view publish to the web
extract metadata annotate content
classify distribute content
share & collaborate enforce access rights
apply processes convert formats
manage lifecycle ...
i don’t think so... ;-)

14. the difference?
content type?
file formats?
security?
volume?
features?

15. the difference?
content type?
file formats?
security?
volume?
features?
in the end it’s just files, with
metadata and a set of services on top

16. the actual difference
what users expect to see
how the content is used
in which business process it participates
where it should be published

17. the actual difference
what users expect to see
how the content is used
in which business process it participates
where it should be published
it’s all about content usage and users’ views

18. the promise of ecm...
DM
Collab DAM
RM Web
BPM

19. what is actually happening...
RM
BPM Collab
DM
DAM Web

20. 2 .0
Entering the web era...

21. Web?
Universal delivery channel for applications (browser)
Flexible and convenient rich content format (HTML)
Protocol for content-oriented architectures (HTTP)

22. CEVA?
Centric
Content Enabled Vertical Application
Oriented
spawns the whole ECM scope to solve actual
business problems
centered on user’s workflow and expectations

23. CMIS?
Content Management Interoperability Services
Allows applications to interact with repositories
Enables
unified repositories
application mashups
and ultimately a vibrant ecosystem of apps

24. time for convergence...
because ecm is about more than a file + metadata

25. Strategy One
App Mashup
Federated Search
Content Portals
Business Processes
Leverage existing apps & srv
HTTP / HTML
Apps / UI Mashups
CMIS + Services Interface
App A App B App C
Content Repository Content Repository Content Repository

26. Strategy One
App Mashup For
Leg
Federated Search a cy A
Content Portals pps
Business Processes
Leverage existing apps & srv
HTTP / HTML
Apps / UI Mashups
CMIS + Services Interface
App A App B App C
Content Repository Content Repository Content Repository

27. Strategy Two
Unified Platform
Content Infrastructure / unified repository
Business Oriented UIs
Leverage content services
Content Repository

28. Strategy Two
Unified Platform
Content Infrastructure / unified repository
Business Oriented UIs
Leverage content services
XML
Office doc Video
Diagram
Rich Content Repository Photo ...

29. Strategy Two
Unified Platform
Content Infrastructure / unified repository
Business Oriented UIs
Leverage content services
CMIS Interface (API)
XML
Office doc Video
Diagram
Rich Content Repository Photo ...

30. Strategy Two
Unified Platform
Content Infrastructure / unified repository
Business Oriented UIs
Leverage content services
Service-oriented Interface (API)
Publish ...
Workspaces Capture
Workflow Retention
Content Services
Transform Search Classify Annotation ...
CMIS Interface (API)
XML
Office doc Video
Diagram
Rich Content Repository Photo ...
ECM Platform

31. Strategy Two
Unified Platform For
Content Infrastructure / unified repository
N ew
Business Oriented UIs
A pps
Leverage content services
User-centric CEVAs
Marketing Doc Contract Mngt New Drug Appr. ...
Service-oriented Interface (API)
Publish ...
Workspaces Capture
Workflow Retention
Content Services
Transform Search Classify Annotation ...
CMIS Interface (API)
XML
Office doc Video
Diagram
Rich Content Repository Photo ...
ECM Platform

32. Let’s stop considering ecm
as file sharing with metadata and versioning.
Time to really think about content in business terms.
And define content strategies
to solve actual business problems.

33. Questions?
Check it out: www.nuxeo.com
Discuss: eb@nuxeo.com