198 Lotus blogs updated hourly. Who will post next? Home | Blogs | Search | About 
 
Latest 7 Posts
MWLUG 2017 – We Believe!
Thu, Sep 7th 2017 6
Why we DO migrate code.
Tue, Jun 27th 2017 8
Migrate Notes to DOCOVA Blog Series Part 17: Input translation and input validation formulas
Thu, May 25th 2017 7
Migrate Notes to DOCOVA Blog Series Part 16: Form events
Tue, May 23rd 2017 7
Migrate Notes to DOCOVA Blog Series Part 15: Private on first use folders
Thu, May 18th 2017 2
Migrate Notes to DOCOVA Blog Series Part 14: Column sorting and categorizing
Tue, May 16th 2017 3
Migrate Notes to DOCOVA Blog Series Part 13: Shared columns and fields
Thu, May 11th 2017 5
Top 10
Is 2017 The Year IBM Announces the End of Life of Notes?
Tue, May 24th 2016 24
Migrating from QSI to DOCOVA
Thu, Jun 25th 2015 10
ICAA – Did IBM Release a Free Version of the Notes Client?
Sun, Oct 30th 2016 10
@DbLookup in Javascript? You Bet!
Mon, Nov 7th 2016 9
DOCOVA SE General Release Announcement!
Wed, May 27th 2015 8
DOCOVA V4.1 Overview Webinar
Fri, May 30th 2014 8
Are You Attending IBM Connect 2017?
Thu, Dec 15th 2016 8
Why we DO migrate code.
Tue, Jun 27th 2017 8
DIY – Migrating from IBM Quickr with DOCOVA Migration Tools
Tue, Apr 21st 2015 7
EngageUG – Ghent Belgium
Tue, Apr 7th 2015 7


DIY – Migrating from IBM Quickr with DOCOVA Migration Tools
Twitter Google+ Facebook LinkedIn Addthis Email Gmail Flipboard Reddit Tumblr WhatsApp StumbleUpon Yammer Evernote Delicious
Chris Fales    

With the end of life for IBM’s Quickr product, many organizations are looking for options to deal with their legacy Quickr environments.   Two of the key criteria for considering migration choices are 1) Functionality, and 2) Ease of Migration.   Companies want to be able to maintain (or increase) their existing levels of functionality and migrate their existing Quickr content easily without a lot of overhead.  In addition, many companies want to be able to perform the migration themselves without the overhead of costly consulting services.

In this article we will take a brief look at the migration tools provided by DOCOVA to allow a company to easily migrate their Quickr environments to the DOCOVA platform, as well as some of the specific functionality available in DOCOVA that make it such a good fit for Quickr migrations.

quickr_to_docova

Ease of Migration

The DOCOVA Migration Manager is a complete solution for migrating an existing Quickr environment to DOCOVA.  Using the DOCOVA Migration Manager, companies can target single or multiple Quickr places to be migrated automatically to DOCOVA.

docova_quickr_migration_manager

DOCOVA Migration Manager for Quickr

Through the click of a button, existing Quickr places can be migrated to DOCOVA Libraries (Places).  The DOCOVA Migration Manager will automatically;

  • create any required DOCOVA libraries to store the migrated places
  • migrate Quickr Place Access Control Lists (ACLs)
  • migrate Quickr Place Members as DOCOVA Library Members
  • migrate Quickr Rooms and Folders to DOCOVA Folders and Sub Folders
  • migrate Quickr Pages and File Attachments to DOCOVA Documents and Files

The DOCOVA Migration Manager comes pre-packaged with migration configurations for the standard Quickr form types (eg. Image, Imported File, Page, etc).  These configurations can be added to or modified as needed to account for any customizations that may have been done to the Quickr environment being migrated.

docova_quickr_migration_document_types

Quickr Form to DOCOVA Document Type Mappings

 

The structure of the Quickr content migrated to DOCOVA is very similar, with the existing as shown by the following diagrams.

quickr_docova_comparison

Quickr and DOCOVA Structure Comparison

Quickr Table of Contents and Folders are migrated to DOCOVA Folders and Sub Folders.  Quickr Pages, Documents, and Files are migrated to DOCOVA Documents and Attachments.

docova_quickr_migrated_folders_documents

Migrated Folders and Documents

 

DOCOVA Features of Particular Interest to Quickr Users

DOCOVA has a variety of features that are of particular interest to both novice and power users of Quickr.  Here is a quick snapshot of some of the key features of interest.

1) Place / Library Members (Groups and Users)

DOCOVA has the ability to configure Library (Place) specific group and user membership.  These user and group members can be migrated from Quickr or added and maintain directly from within DOCOVA.

quickr_docova_members

DOCOVA Library (Place) Members

 

2) Microsoft Office Connectors

DOCOVA has the ability to open and save documents/files directly from within Microsoft Office applications such as Word or Excel.  Using the DOCOVA Office Add-In users are able to access and update their files in DOCOVA in a similar fashion to the Quickr Connectors for Microsoft Office.

docova_office_connectors

Microsoft Office Connectors

 

3) Local File Sync

Select folders and files can be synchronized locally to allow for off-line disconnected access to files.   Files synced locally can be opened and edited while disconnected from the network and automatically synchronized back to DOCOVA when re-connected.

docova_file_sync

DOCOVA Local File Sync

4)  Mobile Access

Quickr content migrated to DOCOVA can automatically make use of the DOCOVA Mobile Access interface to access folders, documents and attachments from mobile devices such as Android, iOS, etc.

docova_mobile

DOCOVA Mobile Access

 

This is by no means an exhaustive list of features for DOCOVA.  Just a sampling of some of the key ones that may be of interest to users migrating off of Quickr.

 

Hopefully this has given you an idea of how easy it is to move your existing content off of Quickr and onto DOCOVA, while both maintaining and expanding the functionality required by users of the system.

For more information check out our Quickr Migration Toolkit Page.  It has a collection of assets related to Quickr migrations.

 



---------------------
http://www.docova.com/migrating-from-ibm-quickr/
Apr 21, 2015
8 hits



Recent Blog Posts
6
MWLUG 2017 – We Believe!
Thu, Sep 7th 2017 5:22p   Gary Walsh
They call Toronto “Leaf Nation”, because so many of the population are passionate about the hockey team, the “Toronto Maple Leafs”.  No matter where the team sits in the standings, they “believe”.   The Notes and Domino community has been like that too over the last decade or so.  Regardless of how the technology is trending, they believe it is the best. MWLUG 2017 in Virginia this past August, like most of the Lotus User Group type events, was a gathering
8
Why we DO migrate code.
Tue, Jun 27th 2017 1:28p   John Ryan
I decided to write a blog entry on the issue of migrating Notes application code when migrating Notes applications to DOCOVA.  When I say “code”, I mean the LotusScript and @formula language that is contained in Notes applications. Now, I’ve seen some blogs and vendor web pages that espouse how you should NOT attempt to migrate the code.  These vendors typically want to convince you that you should re-develop your Notes applications on their platforms.  I get it.  That repr
7
Migrate Notes to DOCOVA Blog Series Part 17: Input translation and input validation formulas
Thu, May 25th 2017 1:51p   John Ryan
Welcome to blog series part 17 of 17 on migrating Notes apps to DOCOVA.  The subject of this blog is Input translation and input validation formulas (formulae if you prefer). Right.  So, one day I hear this argument coming from down the hall here at DOCOVA.  The dev team embroiled in some discussion.  Oh the controversy.  Fisticuffs? Naw.  Heated?  Maybe that would be a bit of a stretch.  The debate?  How should input translation and input validation formulas be handled in DOCOVA? In a
7
Migrate Notes to DOCOVA Blog Series Part 16: Form events
Tue, May 23rd 2017 1:24p   John Ryan
Welcome to blog series part 16 of 17 on migrating Notes apps to DOCOVA.  In this entry I’m going to talk about form events. Okay, so the talk about form events usually starts of with the question: Does DOCOVA have document events like onLoad, onUnload, QueryOpen, QuerySave and WebQueryOpen? Yes.  DOCOVA supports both typical browser events like onLoad and onUnload but has also been extended to handle similar events that were found in Notes forms like QueryOpen, QuerySave, PostSave and so
2
Migrate Notes to DOCOVA Blog Series Part 15: Private on first use folders
Thu, May 18th 2017 1:38p   John Ryan
Welcome to blog series part 15 of 17 on migrating Notes apps to DOCOVA..  In this entry I’m going to talk about good ‘ol Private on first use folders. This is another one of those “interesting” Notes application design constructs.  In my journeys I don’t think I’ve ever come across this same sort of construct in any other application environment.  Anywhere.  Ever.  Sure, a private folder, but “…on first use” is the kicker.  Interestingl
3
Migrate Notes to DOCOVA Blog Series Part 14: Column sorting and categorizing
Tue, May 16th 2017 12:18p   John Ryan
Welcome to blog series part 14 of 17 on migrating Notes apps to DOCOVA..  In this entry I’m going to talk about view column sorting and categorizing. All view sorting and categorizing functionality is supported in DOCOVA.  Additionally, other properties like “Show multiple values as separate entries” and showing response docs in a hierarchy are also supported. I mean, as you get more in depth with DOCOVA, you’ll learn the breadth of the view object model and all the cool stuff
5
Migrate Notes to DOCOVA Blog Series Part 13: Shared columns and fields
Thu, May 11th 2017 1:52p   John Ryan
Welcome to blog series part 13 of 17 on migrating Notes apps to DOCOVA.  This entry is dedicated to shared columns and fields.  It’s short and sweet. DOCOVA does not support the concept of shared columns and fields between applications at this time. Say what?  I know, right?  DOCOVA is so over the top, so chalk full of functionality…it’s crazy, alas at the time of writing this blog entry, it doesn’t support shared columns and fields.  Well, that’s the reason ri
3
Migrate Notes to DOCOVA Blog Series Part 12: Multi-value fields
Tue, May 9th 2017 12:01p   John Ryan
Welcome to blog series part 12 of 17 on migrating Notes apps to DOCOVA.  In this entry it’s all about multi-value fields. Notes had the concept of multi-value fields on forms.  All fields were basically treated as arrays of values.  For example when addressing field values in LotusScript, you might write some code like; Dim myval = doc.myfield(0)  (where doc is a NotesDocument) Although it’s a bit of an odd duck, DOCOVA supports the same type of addressing when it comes to form
2
Migrate Notes to DOCOVA Blog Series Part 11: Pass-thru HTML and Generate HTML for all fields
Thu, May 4th 2017 1:02p   John Ryan
Welcome to blog series part 11 of 17 on migrating Notes apps to DOCOVA. In this entry I’m going to talk about “Pass-thru HTML and Generate HTML for all fields”. A neat aspect of forms development in Notes was the ability to treat text on a form as pass-thru HTML.  This meant that you could add HTML and inline JavaScript directly onto your forms and mark it as pass-thru so that the Domino server would let the text “pass-thru” as HTML/JavaScript when the form was being rende
1
Migrate Notes to DOCOVA Blog Series Part 10: Refresh fields on keyword change
Tue, May 2nd 2017 12:11p   John Ryan
Welcome to blog series part 10 of 17 on migrating Notes apps to DOCOVA.  In this entry it’s all about “Refresh fields on keyword change”. Ya, let’s take a moment to just love this one.  Have you ever used it in your Notes apps?  Refresh fields on keyword change was a bit of an odd beast, no?  The purpose of this operation was to enable field options (or values) to be recalculated based on the change of a selection field. For example, if you had one keyword field on a




Created and Maintained by Yancy Lent - About - Planet Lotus Blog - Advertising - Mobile Edition