Lotus Notes to Sharepoint Migration now simple through REST API and Node.JS Technology
- IBM Domino Access Services are REST services that provide a standard way of accessing Domino resources over HTTP. Applications that use REST services use HTTP requests to post data (create and/or update), read data (for example, make queries), and delete data. REST services use HTTP for all create, read, update, and delete operations.
- The services that are currently available with IBM Domino Access Services are the following:
- Core service - This REST API provides access to resources not specific to any one service domain. For example, most applications have a requirement to read information about authenticated user passwords (last change date, expiration date, etc). Since this requirement is not specific to any one particular REST service (calendar, mail, etc.), this feature is included in the Core services. The resources currently available from the Core services include the password statistics resource (pwstats) and nonce resource.
- Data service - This is a REST API that accesses databases on Domino servers. The Domino data service receives requests and sends responses using HTTP and HTTPS protocols with body content in JSON format. The data service allows you to obtain information on databases, views, folders, and documents. You can update, add, and delete documents.
- Calendar service - This is a REST API that provides resources and methods to access calendar data. The service represents calendar data in both JSON and iCalendar format.
Domino document as REST API :
- Example :Suppose we have two database one for person details and other database is for address detail.Normal scenario we will be exporting the both database document in an excel and combined using primary key and provide an final excel to the user. here we can write the logic and combine the documents in a single JSON file. since it is a REST model any latest technology can consume it.
- I have show you below sample REST Api model from domino, basically we can convert any document.
- Easy to access via any technology since it is a REST API.
- We can merge multiple lookup views in a single JSON file, which make end consumer/customer to decide how to consume it.
- If any changes/update need to be done update the code same will follow remaining documents. And other database lookup also can be introduced as a JSON object and add to the existing document.
- There are three basic ways to store content in SharePoint:
- lists, 2.libraries, 3. pages
- Lists, libraries and pages First, you should understand that there are three basic ways to store content in SharePoint:
lists, libraries, and pages. Each of these has a number of interesting variations, but it is important to understand the differences between these three fundamental types so you can best decide what you want to migrate to. Each type is described briefly here; the sections that follow explain in detail how to migrate content to each.
- Lists: Lists are similar to tables in a relational database. A list is a flat collection of data records (called items in SharePoint) with a fixed set of data fields (called columns). Each data column has a fixed name and type. Lists can have one or more binary attachments and may have one or more views, which allow users to select and sort the items in various ways.
- ages : Pages are the building blocks of all SharePoint sites. These are the web pages you actually see in the web browser every time you click on a link to view a site, open a document, enter some information, or do just about anything else. Most people do not realize that the same pages that make up the sites themselves can also be used as data documents. SharePoint actually allows you to create several types of content pages, including basic pages, wiki pages, web part pages, and publishing pages.
- Libraries: Libraries are collections of binary files, such as images, Word documents, or audio clips. While lists and libraries are very similar internally, the metaphor is very different: in a list, the document may contain several binary file attachments; in a library, the binary file is the document. The emphasis in libraries is the document management functionality, including versioning and check-in/check-out. As with lists, libraries can have many additional data columns defined for capturing additional information about each document.
- Migrate to standard lists Lotus Notes came with many standard application templates that were widely used (with or without customization) by many customers, including discussion databases, calendars, task lists, team sites, contact lists, and document libraries. Happily, in all these cases there is an out-of-the-box SharePoint template designed for you by Microsoft to serve the same purpose. The user interfaces of these new templates may be a little different, but all of the functional-ity should be there.
- When migrating a custom Notes application to a custom list, your main job is going to be to map all the fields in your Notes database to the columns in your custom list.
- Migrate to custom lists Custom lists in SharePoint are just like lists based on standard templates, except that you define all the data columns (and possibly other list settings). When migrating a custom Notes application to a custom list, your main job is going to be to map all the fields in your Notes database to the columns in your custom list.
- A sophisticated migration tool will allow you to write formulas, perform lookups, and apply other data transformation techniques.
- Migrating a Notes database to a library typically involves extracting binary file attachments out of each Notes document and placing them in the library.
- When performing a Notes migration, your main job is to convert Notes documents to InfoPath XML data documents according to a particular XML schema and check them into a form library.
- The wiki page is probably the most popular page type for migrating Notes content.
For More Technical Support :
Whatsapp/Call Us +91-9910612773