Pages: 1
Print
Author Topic: Best way to link to files in a Documentum Repository?  (Read 12370 times)
njh1076
Member

Posts: 3


« on: February 18, 2009, 04:12:09 PM »

Hi,

Just wondered if anyone had experience of linking from text and images in DITA documents to Documentum objects (Word files etc), with the intent of publishing both to the web (XML transforming to HTML) and retaining the links.  Any tips much appreciated.

Thanks,


Logged
wetcoastwriter
Member

Posts: 13


« Reply #1 on: July 27, 2009, 11:34:35 AM »

It looks like nobody has any suggestions. We've had to pull our content out of Documentum because we were having too many issues with links. I'm watching this topic, hoping someone comes along and tells you something promising.
Logged

Don't be afraid, Jellybean. It's a hamster spa and I'm going to give you a massage.
njh1076
Member

Posts: 3


« Reply #2 on: July 27, 2009, 11:48:46 AM »

It looks like nobody has any suggestions. We've had to pull our content out of Documentum because we were having too many issues with links. I'm watching this topic, hoping someone comes along and tells you something promising.

Hi,

In the end we just used the 'File' option that is available when selecting 'Insert link'

If you are using the Documentum/XMetaL integration, when the document is checked back in, a relation link is created reconciling the parent and child object_ids in the Doc Base. 

Hope this helps.

Logged
Su-Laine Yeo
Solutions Consultant
Member

Posts: 260


« Reply #3 on: July 28, 2009, 10:43:14 AM »

Thanks for sharing. This will probably help someone else.

Su-Laine
Logged

Su-Laine Yeo
Solutions Consultant
JustSystems Canada, Inc.
wetcoastwriter
Member

Posts: 13


« Reply #4 on: August 27, 2009, 02:53:45 PM »

We had no end of trouble with links in our Documentum integration. Many of our links would not resolve to paths when we exported content from the Docbase, regardless of the process we used to do this.
We didn't have trouble *creating* links in the Docbase, and we really, really, really miss the ability to do all kinds of things to the linked files (move them, rename them, and so on). We are in the midst of waiting on the corporate freighter make a turn mid-ocean and upgrade our components to make a working system for writing, collaborating, and publishing.
It's been so long, I can't actually recall the steps, but they are documented somewhere (we wrote our own DITA User's Guide to complement our style guide).
Logged

Don't be afraid, Jellybean. It's a hamster spa and I'm going to give you a massage.
njh1076
Member

Posts: 3


« Reply #5 on: September 10, 2009, 12:34:36 PM »

We had no end of trouble with links in our Documentum integration. Many of our links would not resolve to paths when we exported content from the Docbase, regardless of the process we used to do this.

Hi,

Out of interest, what version of Documentum are you on?

In our DITA content a link to a Word document located in the repository looks like this;

<xref scope="peer" format="nondita" class="- topic/xref " href="dctm://CabinetName/3701f9c880002217?DMS_OBJECT_SPEC=RELATION_ID">DocumentName</xref>

When the relation_id of 3701f9c880002217 is looked up in the relationship table view we've created for this purpose in Documentum, the object_id and chronicle ID of both child and parent are available. 

As the chronicle_id is persistent across all versions of an object, it enables location of the latest version and should make moving/renaming of the child or parent an irrelevance. 

I'd be interested in the approach you've taken if it differs.





Logged
Pages: 1
Print
Jump to: