1 / 0

Quest Notes Migrator for SharePoint

Quest Notes Migrator for SharePoint. Steve Walch, Senior Product Manager. Blog: http://notes2sharepoint.org . November, 2011. Partner Training Webcast Series - Session 7 Even more Advanced Content Migration Jobs. Partner Training Webcast Series.

reuel
Télécharger la présentation

Quest Notes Migrator for SharePoint

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Quest Notes Migrator for SharePoint Steve Walch, Senior Product Manager Blog: http://notes2sharepoint.org November, 2011 Partner Training Webcast Series - Session 7 Even more Advanced Content Migration Jobs
  2. Partner Training Webcast Series Migration Basics with the NMSP Designer Client Analysis and Automation with the NMSP Migration Console Advanced Content Migration Jobs Tool Deployment, Domino.Doc and QuickPlace / QuickR migrations Migrating Application Designs Tips and Tricks for Managing Large Migration Projects Even More Advanced Content Migration Jobs (Product demos using NMSP 6.1 beta)
  3. Today’s Agenda Even more Advanced Content Migration Jobs Working with Document Sets Migrating to Wiki and Basic Pages Migrating to Web Part Pages Migrating to Publishing Pages Migrating to InfoPath Form Libraries Introduction to SQL Server Migrations
  4. Working with Document Sets Multiple document library files in one logical document Similar to a folder Maintains header/detail properties Create a target column of type “Document Set“ Optional: Use “Document Set Template” designer to… Specify custom Content Type for doc set Define mappable columns on doc set header Map Notes data to properties on Mapping Tab Use “Column.Property” notation to map to doc set header At a minimum, map to “Name” property of doc set Any attachments mapped to File column become doc set members Any generated documents (Word, etc.) become doc set members
  5. More Document Set rules By default, the value mapped to the Name property identifies one unique doc set Two docs with the same mapped Name get merged into the same doc set Allows flexibility for combining multiple Notes docs into one doc set But may give unexpected results Or, set “Unique By Document ID” property to true Notes UNID controls document set uniqueness Either way, first document wins for header properties Subsequent documents can only add additional doc set members Document sets can be placed inside folders But not the other way around
  6. Document Set Document Set case #1 Properties Metadata Notes Document Data Items Rich Text Document (HTML, ASPX, Word, InfoPath) Data Items Properties Data Items Metadata Rich Text Body File Attachment Properties Attachment Metadata Metadata File Properties Metadata
  7. Document Set Document Set case #2 Properties #1 Metadata #1 Notes Document #1 Rich Text Document #1 (HTML, ASPX, Word, InfoPath) Data Items Properties #1 Data Items Metadata #1 Notes Document #2 Rich Text Body Rich Text Document #2 (HTML, ASPX, Word, InfoPath) Data Items Properties #2 Data Items Metadata Metadata #2 Rich Text Body Attachment File Properties Metadata Metadata
  8. “Basic” content pages Rarely used in SharePoint 2010 “Wiki” content pages Greatly expanded in SharePoint 2010 (web parts, etc.) Web Part Pages set Web Part Properties from Notes data “Publishing” pages leverage SharePoint ECM features Move embedded images/attachments/objects to separate library while migrating Use “AttachmentLinks” construct to compensate for lack of attachment area Generating ASPX Content Pages
  9. Migrating to Wiki pages Create a target column of type “Page Name” Set Page Type property to “Wiki” Mapped value will be appended with “.aspx” Create a target column of type “Note” Name must be set to “WikiField” Create additional target columns (optional) Additional metadata properties File columns with Alternate Library / Folder Folder columns Required column mappings Map Notes text column to Page Name column (above) Map Notes rich text column to Wiki Field column (above) Tip: Use prebuilt Target Data Definition
  10. Migrating to Basic pages Create a target column of type “Page Name” Set Page Type property to “Basic” Create a target column of type “Web Part Property” Web Part Title must be named “Content” Web Part Property must be named “Content” Create additional target columns (optional) Additional metadata properties File columns with Alternate Library / Folder Folder columns Required column mappings Map Notes text column to Page Name column (above) Map Notes rich text column to Content column (above) Tip: Use prebuilt Target Data Definition
  11. Migrating to Web Part pages Create a target column of type “Page Name” Set Page Type property to “Template” Paste in ASPX code into Template property (copy from SharePoint Designer) Create target “Web Part Property” columns as needed Web Part Title, Web Part Property must match ASPX code Supports Content Editor Web Part Create additional target columns (optional) Additional metadata properties File columns with Alternate Library / Folder Folder columns Required column mappings Map Notes text column to Page Name column (above)
  12. Migrating to Publishing pages Create a target column of type “Page Name” Set Page Type property to “Template” Paste in ASPX code into Template property (use “Download a Copy”) All Custom Document Properties may be set as standard target columns (or hardcoded in ASPX Template) Define PublishingPageContentas a Note column Define PublishingPageLayoutas a Text column Create additional target columns (optional) File columns with Alternate Library (“Images”, “Documents”) Required column mappings Map Notes text column to Page Name column (above) Map validstring to PublishingPageLayoutcolumn Approval Code, Content Type columns may be required Tip: Use prebuilt Target Data Definition
  13. Don’t forget “Render with Form”
  14. Migrating to InfoPath Form Libraries Generate InfoPath XML documents from Notes docs Supports any InfoPath XML schema Hand-developed InfoPath Form Templates NMSP-generated InfoPath Form Templates (automatic field mapping) Full support for generating complex documents Map Notes data to desired XML elements Supports hierarchical schema and repeating elements Supports rich text, doc links, images Supports internal or external attachments Generated docs checked into target Form Library Optional: Map SharePoint properties explicitly Optional: Leverage automatic synching of InfoPath properties
  15. Designing a migration job for InfoPath generation Add a target column of type “InfoPath” to your job Use template editor to import InfoPath Form Template Tool discovers mappable fields Override mappable field properties as needed Encoding options Options for handling missing Notes items Options for handling multi-valued Notes items Automap hints Optional: Override Published XSN location Sometimes the default is the form is missing or incorrect Example: InfoPath form publish as part of a solution
  16. Advanced InfoPath Migration Magic Repeating InfoPath Groups Map each group member individually Set Multi property to RepeatParent consistently
  17. Advanced InfoPath Migration Magic (2) Mapping Notes users to People Picker controls Preliminary steps required in InfoPath Designer Detailed workaround available on SharePoint4All site Use the version of the XSN that is published XSN may live in List, Content Type, or Central Administration Publishing from InfoPath Designer can rev version number Best bet: Download XSN from final SharePoint location Workaround: Hand edit Document XML template as needed Do not use XHTML encoding unless the field on your form is really a rich text field
  18. Reminder: NMSP migrate Notes forms to InfoPath (Covered in Session 5 on “Design Migration”)
  19. Why migrate directly to SQL Server tables? Very high volume of data records Application requires transactions Data is needed by other applications Data needs to be migrated to other systems SharePoint limitations (example: number of columns) SharePoint not deployed yet
  20. Migrate to SQL Server Populates existing SQL Server tables only Does not delete prior contents Does not detect “duplicate” documents Supports most column types Rich text typically written as HTML on Text columns Binary files typically written to Image columns Supports a variety of primary key schemes Migrated columns Identity columns Supports data normalization One-to-many (especially images and attachments) Lookup columns Supports link tracking / finalization
  21. Migrate to SQL Server example
  22. Creating a SQL Server migration job Specify target type “SQL Server” on Target tab Select target databases from predefined server list Server list configured in tool Options Create target data definition Load schema from existing table Column properties control primary keys and normalization behavior Extra configuration needed to support record linking How should links to SQL documents be formatted? How should links to images / attachments be formatted? Where does the redirector page live?
  23. External Lists: SQL Server data in SharePoint
  24. Notes Migrator for SharePoint 6.1 Beta Program Beta in progress now! Go to http://communities.quest.com/groups/notes-migration-product-beta-group Sign in with your Quest Community ID Or register to create a new one Use corporate email (No gmail or hotmail accounts) Press the “Ask To Join This Group” button Once approved, log in and download Reviewers Guide Product Installer Expected release: January 2012
  25. Steve’s blog: http://notes2sharepoint.org Product: http://quest.com/notes-migrator-for-sharepoint/
More Related