Documentum Bulk Export Tool v1.3

I updated the QuikDIE Documentum Export Tool to v1.3.  You can download it here.

This update includes the following changes and additions:

  • Added r_creator_name, r_creation_date, r_modifier, and r_modify_date attributes to the standard output set.
  • Converted object_name, subject, title and all custom attribute values to XML-safe.
  • Updated the dmRecordSet JAR to v1.2 and included it in the /lib folder.
  • Fixed bug that considered any object not starting with “dm_” to be custom, instead of ignoring all objects in OMIT_OBJ_PREFIXES array.
  • Included source project in archive.
  • Minor cosmetic tweaks.

The first two enhancements were suggested by Malcolm MacArthur (thanks!).  You can see that discussion thread here.

Advertisements

About Scott
I have been implementing Documentum solutions since 1997. In 2005, I published a book about developing Documentum solutions for the Documentum Desktop Client (ISBN 0595339689). In 2010, I began this blog as a record of interesting and (hopefully) helpful bits of information related to Documentum, and as a creative outlet.

16 Responses to Documentum Bulk Export Tool v1.3

  1. I haven’t used this yet. I’ll take a look at it when I get a chance, sounds really great. Thanks.

    Like

  2. Can this be made to run from a client by copying the right files or do you have to run it on a server?

    Like

    • Scott says:

      I run QuikDIE on a client workstation/laptop, never on the server.

      Like

      • That would make the most sense. However, in your export.bat file you have:
        CONFIG_DIR=c:\documentum\config

        How do you get documentum installed on the workstation in the webtop era? I realize this question is beyond the scope of this thread and app but if you can point me in the right direction that would be great.

        Like

  3. Scott says:

    You will need the DFC installed on the workstation where you run QuikDIE. When you install DFC, it will create this directory structure and create a Dfc.properties and log4j.properties files.

    Like

  4. Given a set up exported set of documents and metadata, I’m wondering of a tool exists that you could open and it would present the files in a way similar to windows explorer so you could navigate to a file and open it. This would be a kind of off-line viewer for exported Documentum content in an exported structure.
    I have some REALLY long path’s that blow up when exported to Window using the standard Webtop Export command so I’m looking for a better solution.

    Like

    • Scott says:

      Scott, the tool dumps everything in a single directory. Each file is named according to its r_object_id. All metadata, including the original path, is contained in a similarly named XML files. You can browse the exported content files in Windows Explorer, but the metadata you must open separately. Does that help?

      Like

      • Sort of. That’s cool but not really something you can give an end user. I guess I’m looking for another tool that puts the XML output from your utility into a GUI and lets you navigate around and open files like you are in Documentum.

        Like

      • Scott says:

        I see… Like an off-line browser of the export. Cool idea.

        Like

  5. Josh says:

    Hi,

    This is a great tool, thanks for sharing! A few questions:

    1. Is there a way to export different metadata values? For example my query is only “SELECT r_object_id, object_name, revision FROM …” but the revision column does not get exported, only the same metadata as if I’ve used “SELECT * FROM …”

    2. I’m wondering if anyone came up with a way to rename the files from the xml data (or name them differently on export) – I would prefer to name them using (object_name)_(revision).ext for example

    Like

    • Josh says:

      3. An option to export metadata to csv files or one single csv file would be excellent

      Like

    • Scott says:

      Josh, there is standard set of attributes that are exported: object_name, title, subject, acl_domain, acl_name, owner_name, r_version_label, i_chronicle_id, r_creator_name, r_creation_date, r_modify_date, a_content_type. In addition, an attributes that are not part of the dm_document model are also exported. I will add your request for differnt attributes to be exported to the enhancement list. I will also see if I can devise a way for the user to provide a filename pattern for the exported files. Thanks for the feedback.

      Like

  6. Pingback: Yet Another Documentum Export Tool | dm_misc: Miscellaneous Documentum Information

  7. Pingback: Documentum Bulk Export Tool v1.4 | dm_misc: Miscellaneous Documentum Information

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: