Promise #2 – The Public Sector Digital Landfill

Digital Continuity logo

Refer: 14 Unfulfilled Promises


In my post “The Public Sector Digital Landfill” I described how NZ Archives were creating a Digital Continuity Strategy that would “ensure that valuable information is preserved and migrated when necessary to the latest formats and media, appropriate metadata is attached, and documents that are no longer relevant are securely deleted”.

I also expressed some excitement at the fact that NZ Archives had drawn up a “Digital Continuity Action Plan“, and stated that I would be following the progress of it.

Delivering on the Promise

I admit that I didn’t follow what was happening with that initiative. However, I recently made contact with Mike Crouch from NZ Archives.

Turns out that NZ Archives has been doing a lot with regards the Digital Continuity Action Plan.

Digital Continuity Action Plan

The Digital Continuity Action Plan is described beautifully in a publication that Archives NZ actually published in 2009. You can view it in HTML format here, or a PDF copy can be downloaded here.

The key messages given in the report really made sense to me. They are:

  • There when you need it – digital information will be maintained so that it can be accessed when needed.
  • Authentic and reliable – public-sector digital information should be tamper-proof and free of technological digital rights restrictions
  • Trusted Access – Publicly available information should be findable and usable by all New Zealanders,  and sensitive information will be protected from unauthorised access.
  • Do nothing, lose everything

2010 Conference

In May 2010, a conference was held with experts from Australasia, North America and Europe who presented on a range of aspects in the digital preservation and information continuity fields. There were three streams, and the presentations, and recordings of the sessions can be viewed/listened to here.

2012 Conference

At the end of March, another conference was held. The title was “Digital Preservation by Design”. It looked like there was an excellent line-up of speakers from around the globe.


The idea of digital preservation has been taken seriously by the government in New Zealand. The last of the four key messages (see above) sums it up well: “Do Nothing, Lose Everything.”

Promise #4 – Comments on “The Problem with Network Folders”

Refer: 14 Unfulfilled Promises


In the post “Comments on ‘The Problem with Network Folders'” I made a few arguments against the claim that Network Folders were no longer of any use.

Then I promised I would go into this further in a later post.


Promise Fulfilled!

In the post “Using a network file share – a case study” I described where Network Folders are still useful.

Promise #1 – The value of a Content Management system

Refer: 14 Unfulfilled Promises


In my post “The value of a content management system” I described how the US Air Force Medical Service had added an E2.0 interface to their content management system, and finished the post by trying to find out if I could republish some of the material from the article.

Delivering on the Promise

Instead of republishing excerpts from the post, I have included a link to the post, so that you can read it yourself:

Social Network Enlightenment Found in the U.S. Air Force Medical Service

Return to…CIP Land

What follows is one of my post that was recently published on AIIM’s site as an “Expert Blogger”. (The original can be read here)


Return to…CIP Land

In my last post I talked about that recently discovered, and charted, land called “CIP Land“.

When I originally started writing that post, I had a vision of an island where each knowledge domain” represented a part of the island, which further contained representations of the “sub-domains”.

And, that’s when I drew the “map” that can be seen in that last post.

However, after I had written the post I realized that this “CIP land” was not an island.

An island, by definition, is not a continuous landmass, and is surrounded by water. With an island, there is no connection with other islands or, for that matter, with other countries (especially if you looked at the map I drew). It is separate from everything else.

This was very, very wrong.

The whole idea of an Information Professional, as defined by the CIP certification is, (and as Jesse Wilkins described it in his post “Are you T-shaped?“), someone who has a good, broad, knowledge of the different territories (knowledge domains), someone who has travelled the highways of the land, and knows enough to be able to get around each territory without the use of GPS, or SatNav.

They know enough about the customs of each territory, city, or village that they can communicate and interact, easily, with the locals of each area. If they need more in-depth local knowledge, they can hire a guide, but they have enough knowledge that they can see how each city, town, or village, interacts with the others.

They can see the “big picture”.

But the whole idea behind this, is that CIP Land is isolated.

And this is wrong, because CIP land is not isolated. It makes up part of a “global” environment. It interacts with other “lands”.

Think of it as a landlocked country in a continent made up of multiple countries (Europe for example). It takes advantages of its local talent, and specialized knowledge, but it interacts with the other countries. It requires them for services, and resources, that it doesn’t have. Just as the other countries, in turn, require the local skills and resources that it can provide.

So, from this, you can see that “CIP Land” is not an island. It’s a country. A country Political Map of Austria - Map of Austria, Europesurrounded by other countries.

Information Management can’t exist without databases, without networks, without hard drives, or storage areas. Hell, if CIP Land was an island, my friend, we wouldn’t exist for long.

Clearly my map of “CIP Island” needs to be redrawn…

CIP Land

What follows is one of my posts that was recently published on AIIM’s site as an “Expert Blogger”. (The original can be read here)


The CIP Land

I’ve been working my way through the excellent CIP exam preparatory videos on the AIIM site. (These were prepared by Steve Weissman, and the Holly Group, and are very impressive.)

As I went from one “Knowledge Domain” to another I started realizing what it is that I like about the CIP. It’s that it creates a boundary.

What do I mean by this?

Well – think of your “Information Professional” as someone living in a village. A village called “Content Management”. They do their job, and do it well. They’re not aware of the fact that beyond their own village lies a whole world. Then the person travels. Maybe they have to visit another area for their work, or they see people from other areas visiting, and decide to go exploring. In any case, they get to see new sights, or learn new things. The world, for them, however, is still uncharted.

I have lived in this land, and I also only knew of only a few areas. Gradually, however I have travelled and seen new things.

At one point I started actively seeking out other residents. We all seemed to talk a common language, but each person had their own “regional” vernacular, or way of saying things. Each had their own experience and knowledge based on the areas where they were living. We learnt from each other.

The land we lived on was still uncharted. It had no boundary, or borders. No-one knew where it started or stopped, or what places made up the land.

The CIP however, defines what knowledge an Information Professional should have. It creates a map of that land. And it appears that it is an island in a sea of other similar islands. All interacting together.

Looking at the map, I have come to realize that this collection of experiences and knowledge that I have from my many trips through different areas all fits into a big picture.

And that is what I like about the CIP. I now can look at it, and get an idea of the various places that make up this world.

I know which areas I need to revisit, or spend more time in, to give myself a more rounded set of knowledge and skills to be able to call myself an Information Professional.

Europe Momentum 2011 – Resources for those who couldn’t be there…

This year’s EMC’s European Momentum is being was held in Berlin.

The Momentum conference is something I have always tried to attend. It  is a great opportunity to:

  • find out what EMC’s strategies are.
  • Attend great sessions to learn more
  • Meet great people
  • Share ideas & experiences,
  • etc, etc.
So – what if you can’t couldn’t attend?
I’m trying to put together a list of resources that will give you the opportunity to follow Momentum online.

Hopefully I will be adding to this page as I find more excellent ways to “be there” (virtually).

Also check out my Google+ stream. I’ll post regular updates there as well. (


  • More to come…


Official site

Images and Videos from the Conference



#ECMJam 3 – SharePoint & ECM

Yesterday, the third #ECMJam was held. A lot of people were involved and it was a very interesting discussion about

the place of SharePoint in the world of ECM.

Bryant Duhon was the Jam facilitator. Check out his “Introductory” post here (

There were a number of Questions that formed the basis of the discussion. These were:

Q1: Is there problem with #sharepoint expectations, marketing, or the product itself?
August 11, 2011
Q2: #SharePoint / #governance — how to do it for real (in 140 characters or less!)
August 11, 2011
Q3: Is there/has there been a backlash vs. #SharePoint?
August 11, 2011
Q4: What does #SharePoint do well ootb? What doesn’t it do?
August 11, 2011
Q5 Can #SharePoint solve #collab and DM problems for larger companies, as well as smaller? Can/does it really scale?
August 11, 2011

Each question raised some interesting responses.

With regards Question 1, there was a feeling that SharePoint was not quite an ECM application:

#ECMjam A>Q1 Sharepoint is no #ECM system when you take the #AIIM definition as reference
August 11, 2011
#ECMjam A>Q1 Sharepoint claims to be #ECM, but a lot of ECM vendors make money enriching SPS2010 with ECM functionality
August 11, 2011
Q1: There’s a problem with expectations! #SharePoint isn’t the be-all/end-all too many folks seem to believe.
August 11, 2011

Others pointed out that the problem isn’t with what the product, itself, can do, but with the “misunderstanding” of what SharePoint actually is.

Q1: IMO, SharePoint “problem” is not with product as much as with misunderstanding of what, why, where, how it can/should be used.
August 11, 2011
Q1 Agree that SP does a lot and what it does, it does well. TCM is the big gap. #ECMjam
August 11, 2011
Q1: #sharepoint is a platform, but was sold as a product. Leaves users spending $$$ to get what they were promised #ecmjam
August 11, 2011
Others expanded on this, and discussed what ECM should actually be, as well as pointing out that after the “purchase” of SharePoint, extra costs.
Q1 you can not achieve ECM with 1 product or a platform, SP still does not provide scanning OOTB #ecmjam + you need PM consulting & techserv
August 11, 2011
Q1 Saw recent data from a SP conf that for every $1 of SP license it sells, partners sell $6 of services. Underscore OOTB issue. #ECMjam
August 11, 2011
Q1: So expectations are over-hyped and fueled by microsoft to make #SharePoint out as more than it is. #ECM #ecmjam
August 11, 2011
Q1. As follow up to my previous comment, from my standpoint, people just seem to buy software as a panacea. Why not more plan 1st #ecmjam
August 11, 2011
Q1. My theory, it’s from Microsoft, so folks believe it’s just going to be out of the box #ECM. #ecmjam
August 11, 2011
And not just by Microsoft RT @bduhon: Q1: So expectations are over-hyped and fueled by microsoft #ECM #ecmjam
August 11, 2011
Too hard, too long, too obvious! RT @bduhon: Q1. people just seem to buy software as a panacea. Why not more plan 1st #ecmjam
August 11, 2011

Question 2 (SharePoint and Governance) was met with a unaimous response – PLANNING & CONTROL

#ECMjam A>Q2 #Sharepoint governance needs good planning and administration esp. in distributed environments
August 11, 2011
4 characters: P-L-A-N. 5 characters: T-H-I-N-K RT @bduhon: Q2: #SharePoint/#governance: how to do it (in 140 characters) #ECM #ecmjam
August 11, 2011
#ECMjam Q2-You can define segments of SP with different technical restrictions to assist in governance (e.g. size quotas for team sites)
August 11, 2011
Q2: #sharepoint governance must be both centralized and distributed. Policies set by org, solution design by business units. #ecmjam
August 11, 2011
#ECMjam A>Q2 Viral, uncontrolled installation and usage of #Sharepoint is the death of every information management governance!
August 11, 2011
One of the advantages of SharePoint is that is puts the administration, and “growth” of a site into the hands of the end-users (empowers). But this is also a disadvantage. Sites can expand and spread “virally”. The discussion touched upon this.
Q2: Governace requires planning up front and RIM on the back. Can’t be done with a full featured ECM #ECMJAM
August 11, 2011
Q2 @piewords “Viral w governance can work.” Sort of like a organizational social media policy? #ECMjam
August 11, 2011
More involved but yes RT @inoldland: Q2 @piewords “Viral w governance can work.” Sort of like a organizational social media policy? #ECMjam
August 11, 2011
Q2 so how do you explain governance to an end user and get them involved? Easy to say, hard to do #ecmjam
August 11, 2011
There, and in CIO office (and in Redmond?) RT @bduhon: Q2. So #governance is where a hammer is needed? #ECM #SharePoint #ecmjam
August 11, 2011
Q2. So, @danieloleary @jessewilkins: #governance is where a hammer is needed? #ECM #SharePoint #ecmjam
August 11, 2011
The discussion surrounding this question ended with a few good points that summed up the use of governance in a SP environment. It is useful, but needs to be applied sensibly.
So what kills #SharePoint? RT @incontextmag: Q2: SP doesnt kill governance. People kill governance. #ecmjam
August 11, 2011
Q2: SP doesn’t kill governance. People kill governance. #ECMJAM
August 11, 2011
(Answer) So what kills #SharePoint? Governance! (sometimes) RT @incontextmag: Q2: SP doesnt kill governance. People kill governance. #ecmjam
August 11, 2011
Question 3 (Is there/will there be a backlash against SharePoint) was very much related to expectations.
Only against over-inflated expectations. RT @bduhon: Q3. Is there/will there be a backlash against #SharePoint? #ECM #AIIM #ecmjam
August 11, 2011
#ECMjam A>Q3 #Sharepoint is already outdated compared to mobile and apps
August 11, 2011
After 10 yrs? Seems to me we should have seen one already. <Q3. Is there/will there be a backlash against #SharePoint?> #ECM #AIIM #ecmjam
August 11, 2011
#ECMjam A>Q3 #Sharepoint is too complex in relation to consumerisation of #collaboration & #ECM
August 11, 2011
Q3: There surely is a @sharepoint backlash, but it’s misguided, because it’s based on the misunderstandings we discussed re: Q1. #ecmjam
August 11, 2011
Q3 Backlash will come only if SP doesn’t deliver value. Same reason there’s backlash against anything. (Apologies to Susan Faludi.). #ECMjam
August 11, 2011
Q3: SharePoint has a place, but it’s not a mass market tool. It won’t ever be the Facebook of ECM #ecmjam
August 11, 2011
In the end, this comment was made:
Q3: The problem is that they market it as ECM but ECM is a category and no one product is all ECM. #ECMJAM
August 11, 2011

But someone pointed out:

Only in our circles; elsewhere they promote other stuff (eg, collab) RT @incontextmag: Q3 The problem is that they market it as #ECM #ecmjam
August 11, 2011

Question 4 discussed what SharePoint did well, and what it did not do well.

While this question didn’t generate the same discussion as others, there were some interesting comments.

The “does well” comments included:

Q4 SP does sharing, collaboration and portals very well OOTB. It does not handle high-volume, transactional stuff well. #ECMjam
August 11, 2011
Easy way to share Office docs. Replacement for file shares. RT @bduhon: Q4: What does #SharePoint do well ootb? #ECM #AIIM #SP2010 #ecmjam
August 11, 2011
Q4 – Collab & portals are good. Governance, transactional content, capture weak. #ecmjam #ecmjam
August 11, 2011
#ecmjam Q4: Good: Basic document management. Huge improvement over shared drives. Bad: Dependent metadata and field validation.
August 11, 2011
Q4 SEARCH! In 2010 they nailed it, wish every platform was as functional #ecmjam
August 11, 2011

Whereas, the “does not do well” included:

Q4 SP doesn’t do BPM well. Managing docs from outside an org’s four walls that need to be processed. #ECMjam
August 11, 2011
Q4: Doesn’t physical records management, BPM, transactional content management, scanning & capture, archiving & library services #ECMJAM
August 11, 2011
Q4 – Weakness: Seen many orgs empower depts to make their own teamsites, but result is too many silos and no enterprise governance #ecmjam
August 11, 2011
Q4: SP default is to store as blobs, inflating the DB, but if you do much you need a SP work around. #ECMJAM
August 11, 2011

Question 5 asked “Can SharePoint solve collaboration and DM problems for larger companies as well as for smaller?

Generally it seemed that while SharePoint was useful for a small company, the administration, and maintenance requirements were too high to make it practical.

#ecmjam Q5 SharePoint has always been able to scale the difference is it puts it in the users hands front end, versus other ECM backend
August 11, 2011
#ecmjam Q5 so scaling requires more planning, but absolutely can scale for large companies
August 11, 2011
Q5 the time to live and staffing requirements are too much for small business, #sharepoint is a better fit for larger orgs #ecmjam
August 11, 2011
#ECMjam A>Q5 #Sharepoint can solve DM problems in smaller orgs but is some overkill in regard to admin
August 11, 2011
Q5 no 4 SMB’s. lack time and IT resources. rely on specific OOTB and references to their biz/problems that dont exist #ecmjam
August 11, 2011
Q5: Technically (performance, scaling) Yes, but for the features and manageability No. #ecmjam
August 11, 2011
The discussion also touched upon the scalability of SharePoint, as well as its use in the Cloud.
Short ans: yes. Better ans: yes, but, with “but” = may require 3rd pty apps RT @bduhon: Q5 Can #SharePoint really scale? #ECM #AIIM #ecmjam
August 11, 2011
Q5 the best way to scale sharepoint is to run in the cloud #ecmjam
August 11, 2011
What kind of cloud? Cloud cloud or VM? RT@shadrachwhite: Q5 the best way to scale sharepoint is to run in the cloud #ECMJAM
August 11, 2011
#ECMjam A>Q5 #Sharepoint as Office365 SaaS might be the solution for SMEs
August 11, 2011
@bduhon q5 Not yet. There is promise for the future for SP for SMBs with Azure and the future cloud platformed SP in dev. #ecmjam #AIIM
August 11, 2011
Q5 Wondering if performance is an issue as SP scales (when it does). #ECMjam
August 11, 2011
#ECMjam Q5: We’re 26,000 people. SP scales, but it needs careful focus and planning.
August 11, 2011
Q5: hmmm. Scale in what way? functionality … no. of users … geography … ? #ecmjam
August 11, 2011
So it was  a very interesting discussion with a lot of interesting comments.

For a read of the actual tweet stream, click here (

AIIM’s CMIS Product Guide!!!


Wow – call me Happy and knock me to the ground.

AIIM have just released their standards based Product Guide focused on CMIS. Being an AIIM Professional Member I was quick to download a copy.

For those of you unfamiliar with CMIS (Content Management Interoperable Services), one of my earlier posts “Small Brain Notes on CMIS” explains it more in detail.

About 9 months ago I started writing a blog post that would give an overview on the CMIS market at that stage. A lot of Vendors had recognised the real benefit of CMIS and were all making plans to implement it one way, or another.

My post did have some promise. (Click here if you’d like to view it in it’s unfinished glory). However I was not happy with the incompleteness of it, and decided, at the stage not to publish it.

The AIIM document is not comprehensive (which AIIM states clearly in the Introduction). It covers 13 vendors, and describes the CMIS enabled product of each of them along with more detailed information on the use of the product as well as (where possible) the CMIS capability support of the product.

Products covered in AIIM’s Report:

  • Alfresco Web Quick Start
  • Alfresco Activiti
  • CMIS Export for Kodak Capture
  • Content View
  • Documentum Content Management Interoperable Service
  • Fresh Docs
  • IBM Connections 3.0.1
  • IBM Content Manager Enterprise Edition 8.4.3
  • IBM FileNet Content Manager 5.0
  • IBM Lotus Quickr 8.5
  •  Nuxeo Document Management
  • Open Text ECM Suite 1.0
  • SharePoint 2010
  • WeWebU Open Workdesk

The authors hope that later versions of the guide will contain more vendors.

In the start of the Guide there is a very good introduction, and an article by David Choy (chair, OASIS CMIS Technical Committee). David Choy has also recorded a brilliant video, awhile ago, in which he explains CMIS. This was a great tool when I was trying to understand what CMIS was all about. (You can view the video here.)

After the vendor review, there are a couple of articles by Laurance Hart (@piewords) and Stephan Waldhauser (@WeWebU).

Following the articles, there is an excellent list of CMIS Resources, which I am going to look through when I get some time.

Taking into account that (at AIIM’s own admission) the Guide is not comprehensive, it is still a very handy document to give a better understanding of the CMIS landscape.

My only criticism is: Guys – when you are creating a PDF – do it properly. Get each section properly bookmarked, as well as the TOC hyperlinked to the corresponding page. It’s not hard to do; it makes the Guide a lot more usable (when viewing on screen).

Click on CMIS for my other CMIS posts.

CMIS is here … but where?

Note – this post is in a draft format. It was written in June 2010 and was never published. The information in this post is not complete.
I have released it now as part of my AIIM CMIS Product Guide post.

CMIS 1.0 was ratified in the beginning of May 2010. This is the standard that will allow interoperability between the various content management systems that are currently on the market. For more information on CMIS, refer my Small Brain Notes on CMIS. Go and read it now, and when you are finished, click on the back button. I’ll be waiting…

Ok – now that you understand a bit of what CMIS will offer, let’s ask the question – when will it be available in these disparate content electronic content management systems?

Let’s look at the list of companies that were associated with the creation on CMIS 1.0

And…who is ready for CMIS?


These three  were there in the beginning, and developed the initial draft.


The following companies also played a part in the moulding and shaping of the CMIS standard:

  • Alfresco – Version 3.3 (available now)
  • Open Text,
  • Oracle,
  • SAP

Others Adapting their systems to be CMIS compliant:

  • ASG Software Solutions
  • Content Technologies ApS
  • Day Software
  • Ektron
  • Exalead, Inc.
  • FatWire
  • Flatiron Solutions Corporation
  • Greenbytes GmbH
  • Harris Corporation
  • Nuxeo
  • Saperion AG
  • Sun Microsystems
  • Vignette Corporatio

Here is a list of the vendors with regards CMIS compliance.

Vendor Product CMIS Support Timeline
Alfresco Alfresco 3.2 Available for testing
EMC Documentum First half of 2010
IBM Content Manager Second First half of 2010
IBM FileNet P8 Second First half of 2010
KnowledgeTree KnowledgeTree 3.7 Available for testing
Microsoft SharePoint Server 2010 First half of 2010
Nuxeo Nuxeo DMS 5.3 Available for testing
Open Text Enterprise Library Services (ELS-Beta) CMIS connector available now
Open Text Open Text ECM 10 Mid 2010
Oracle Oracle Universal Content Management Not known
SAP SAP DMS Not known
Sense/Net Sense/Net 6.0 Available for testing

John Mancini’s Keynote View of the Digital Future


John Mancini, President of AIIM International was kind enough to make a zipcast of his info360 keynote presentation slides. This allows him to do “present” his slides. I am very, very grateful that he did this, as I was not able to attend the conference. I was really impressed by John’s comments. I made some “rough” notes. (I call them “rough” because they don’t capture all of John’s message – If you want, scroll to the bottom of this post to see the link to his zipcast.) ============================================================ Rough Notes made from John Mancini’s keynote at Info360 We are in the middle of an interesting technology inflection point —————————————————————- We have been through many phases, each with its content management focus.

  • Mainframe – Batch Transactions
  • Mini – Departmental Processes
  • PC – Documents
  • Internet – Web pages

Effectively what we have done is just taken the old world of paper-based records, ledgers and transferred it to the next phase of technology. This may the the source of some of the challenges that we have. The next iteration after the Internet will be “Social” – a focus on interactions and conversations. The content management focus will be capturing and managing these. John mentions that companies can’t just put a social layer on top of their current processes. They will need to think about the social layer and how they embed it in all of their processes and push it back through our web presences and information repositories so that everything connects up. A system of engagement that just has a front-end social process and nothing else behind it is not enough. John also points out that we need to avoid pushing just old world concepts into this social world. We will need to adapt these ideas, and ways of doing things. The old transactional ideas had to do with control, auditing and securing. This won’t be always possible in the new way. Implications ———— CIO’s will need to approach things differently.

  • Traditionally – Minimise Risk and Reduce Cost.
  • The new is Add Value and Create New Reality

The end of the email era John did an analysis of his e-mail:

  • 46% was actually unwanted (spam);
  • 21% was e-mails to colleagues – these could actually be better addressed with social media;
  • 21% was bac’n (interesting, but not essential, can be deleted without any harm).
  • The only things of real value were the e-mails sent to, and received from, real people outside of the organisation. This accounted for only 6% of total volume.

His point was – we need to think differently about e-mail. This is compounded by the fact that the people coming into the workforce are from the “social” phase, while the people making the decisions are from the “PC” phase. The End of IT autocracy.

  • 10 years – the coolest technology was was you got at work.
  • Now that is reversed.
  • Workplace IT is lagging behind.
  • If a business imperative is important enough, it doesn’t matter how much IT control it, if going outside that control will allow a user to get the job done, people will do it.

Implication of Compounding

  • Information growth will be incredible.
  • At the same time the cost of storage is dropping.
  • However this is not proportional. (Information growth exceeds decrease in cost).

Why we should care ——————-

  • If we ignore this, we will make the same mistakes again. E.g. when e-mail came out, companies considered it a risk, and that it was really only needed for management, etc.
  • However, companies need to embrace this technology to remain competitive. Otherwise there is a risk of a “digital divide”. The longer that it takes, the more difficult it will be.

============================================================== Link to John Mancini’s Zipcast ———————————————–

The Wingspan Connection – getting SharePoint & Documentum to talk to each other

This is just a short post.  Just want to show an overview of how Wingspan components  allow a user to access their Documentum documents from SharePoint.

wingspan spx sharepoint documentum firstdoc emc

Taken from Wingspan Documentation

Here you can see that there are two main components:

The DocWay UI is a collection of Web Parts installed on a SharePoint Server .

The DocWay Server comprises two components that are always installed together even though they function independently.

  • The DocWay Web Service provides Search, Content Management, and Workflow services.
  • The DocWay Content Transfer Service (DocWay Transfer Service) provides transfer of content between the user’s desktop and individual Documentum Docbases

So, basically, what happens is:

  • A user logs into their SharePoint site that contains Web Parts supplied by the DocWay UI.
  • These Web Parts display meta-data gathered by the DocWay Server about content stored in the Documentum Docbases.
  • Should the user transfer content between their local storage and a Docbase, the transfer is made by the DocWay Transfer Service, bypassing SharePoint entirely.

Included Web Parts for End Users

  • Home Cabinet
  • Subscriptions
  • Checkouts
  • Recently Accessed Files
  • Inbox
  • My Workflows
  • Virtual Folders
  • Repository Browser
  • DQL Query
  • Object View
  • Search

Included Web Parts for Administrators

  • DocWay System Administrator
  • Menu Designer
  • Component Administration
  • Web Part Group Settings

Included Web Parts for Developers

  • DocWay Diagnostics
  • AJAX Call Viewer
  • HTTP Request Inspector
  • System Information

Wingspan produce several other products that allow integration between Documentum and SharePoint. One of these is eResults that I have posted several times about in this blog (see Tag Cloud).

Related Posts

Momentum Lisbon – A welcome invitation.

I was invited out for dinner after the Welcome Reception by CSC.

CSC offer a product called FirstDoc that adds a compliance layer to Documentum. As well as that, they have products that allows documents in a  Documentum repository to be exposed in SharePoint, while maintaining 96% of the functionality of FirstDoc.

It was a very pleasant evening, and the meal that was served was wonderful.

Thanks Nigel, Paul, Chris & Jim.

The value of a Content Management system

I’m reading an excellent article in the January/February issue of AIIM‘s Infonomics. The article talks about the implementation of an E2.0 interface for the US Air Force Medical Service‘s content management system.

The opening paragraph really sums up, what I consider, one of the biggest problems with content management systems:

It’s not the application itself, it’s the commitment from the users.

The article is a good one. I am trying to arrange permission to reproduce parts of the article at the moment. Once I do, I will talk about this more.

– Mark