View stunning SlideShares in full-screen with the new iOS app!Introducing SlideShare for AndroidExplore all your favorite topics in the SlideShare appGet the SlideShare app to Save for Later — even offline
View stunning SlideShares in full-screen with the new Android app!View stunning SlideShares in full-screen with the new iOS app!
Allergan: EMC Documentum Compliance Manager Migration Revisited — What a Difference Two Years Makes David Mc Donagh Project Manager, EDMS Allergan, Inc. Jes Wills Migrations Practice Manager Blue Fish Development Group
Java Method Server lockup (if more than a few (4-5) people were promoting). Installed Media Server as part of the SP1 "C" build to process the promotion and notification events. HP/UX required additional time to get fix.
Serial workflow functionality was only 25% developed. Modified Quickflow to get required functionality.
17 reviewer/approver limit - Never fixed in 5.2.5 sp1
dcmCheckin method used for custom check ins did not work
dcm_change_cd_properties audit event was not logged. Fixed in SP1 "FCS" build.
Could not demote a document. Fixed in SP1 "FCS" build.
Could only assign the document owner as the periodic review owner and all class coordinators would receive the notification. We customized periodic review.
Search did not work as expected. Customized simple and advanced search.
Project Snow Goose involved not only a migration, but also an information re-architecture.
This re-architecture involved systematically determining the target object-type, attributes, lifecycle, content and location of a migrated object, based on the object’s previous incarnation. While the source repositories held a significant amount of information, this needed to be validated for consistency and then made accessible to the migration system.
Many facets of this re-architecture were complex.
Project Snow Goose Examples of complexity – Assembly Rules SOP#1, 2.0, Obsolete SOPs Released SOPs SOP#1, 2.0, Current SOP#1, 3.0, Current SOP#1, 4.0, Current Master SOPs SOP#1, 4.0, Current SOP#1, 3.0, Retired SOP#1, 4.0, Current + SOP#1, 3.0, Retired + SOP#1, 2.0, Obsolete +
Project Snow Goose Examples of complexity – Naming Conventions A naming convention describes how to break apart names into their meaningful elements. An example of a naming convention specification is: type – pla_state – unit_size – batch_size – destination – formula The elements of the name are used in other components of the migration, for example to determine the name of the destination folder in the target repository. An example target folder specification would be specified as: formula – 0525 – batch_size An example of a name that conforms to the convention, and its target folder: ointment – production – 30mg – 600 – waco – F245 F245 – 0525 - 600