Hi All,
We need to upload lotus notes emails in content server in bulk. Please provide your suggestions.
Content Server 16.0.5 (2017-06), build 1344
Regards
Abhi
Hi Abhi,
Can you provide further information?
- are the emails currently stored in LN (or on a file share)- is there a requirement to store the emails in CS as emails (plus extract email metadata) or simply as documents with objtype 144- volume: 1000 emails or 1000000 emails- what email format do you want to store them in? e.g. eml or msg or ...
Paul | SLIM Applications
-----Original Message-----From: "eLink Entry: Content Server Development Forum" <development@elinkkc.opentext.com>To: "eLink Recipient" <devnull@elinkkc.opentext.com>Date: 11/17/17 13:47Subject: How to upload lotus notes email with extension (.eml) in bulk in Content Server How to upload lotus notes email with extension (.eml) in bulk in Content Server Posted by abhimanu.walia@prudential.com (Walia, Abhimanu) On 11/17/2017 07:32 AM Hi All,We need to upload lotus notes emails in content server in bulk. Please provide your suggestions.Content Server 16.0.5 (2017-06), build 1344RegardsAbhi[To post a comment, use the normal reply function]Forum:Content Server Development ForumContent Server:Knowledge Center CS 16.2.2
Hi,
Thanks for your reply.
Please find below details
are the emails currently stored in LN (or on a file share) --> Fileshare- is there a requirement to store the emails in CS as emails (plus extract email metadata) or simply as documents with objtype 144 --> upload as email with email metadata- volume: 1000 emails or 1000000 emails --> it would be a continuous upload process time to time but at a time maximum should be 10 K.- what email format do you want to store them in? e.g. eml or msg or --> .eml
The key problem is that CS 16 does not support uploading eml files as emails.
Below some options you may wish to consider:Option A Convert to msgConvert emails using a tool from eml to msg format and then upload the msg's using e.g. Enterprise Connect or Object Importer
This requires purchase of a (commercial?) conversion tool and the emails end up as msg files. This allows for uploading as emails into CS and viewing the emails in CS but your user base may not be able to open the emails in msg format using the standard client.The conversion may also not be allowed from a compliance perspective.
Option B (likely not sufficient)Upload the emails in eml format as documents. Email metadata is not extracted.The emails are archived in CS and the email contents is searchable. Lack of metadata means advanced searching, viewing, sorting, etc.. is not possible. The eml format does allow your users to open the emails.
Option CUse a 3rd party tool to upload the eml's, extract the metadata and populate the CS categories / attributes. Basically the emails are uploaded as documents (objtype 144) and the email metadata is captured into a category.(I am not aware these tools exist. My company has developed tools to upload emails in eml format to a different content management system. It is not available in the current tool for Content Server that only supports Livelink and CS10.x)
Option DUse a script (e.g. .Net or PowerShell) to extract the email metadata from the eml's and then generate an xml file conforming to the Object Importer (OI) format.Then use OI to import the eml's and set the email metadata in categories.
Hope this helps.
Option E
Upgrade to Content Server 16.2.3. The December 2017 quarterly update will support .eml messages as email objects, including extracting the usual email metadata.
Patrick
Thank you paul for your reply
we are discussing these options if we can opt any. Meanwhile i also did some research that i want to share here and want to know your thought as well on that.
If we can upload emails in Content Server as document ( subtype 144). After that we can run the email metadata utility with option "upgrade email document with email object" , would it convert existing email documents (we just uploaded) in email bodies ?
"If we can upload emails in Content Server as document ( subtype 144). After that we can run the email metadata utility with option "upgrade email document with email object" , would it convert existing email documents (we just uploaded) in email bodies ?"
The email metadata utility runs in the browser and uses html5 to extract email metadata from an email that has just been read (from the local disk or file share) and then generates a lapi request to upload the email plus metadata. It is a client-side tool.
The approach to upload eml files to CS and then in a separate operation add the email metadata is feasible. The "solution" then needs to extract email metadata (from the original set on a file shares) and then set the metadata values in the category. I would prefer to use a category and keep the eml as objtype 144 and not try to store the eml file as an email object since that is officially not yet supported.BTW: great to hear CS16.2.3 will support eml files. That is definitely the best strategic solution but looks like you need a tactical solution in the interim period.
If the emails already exists in CS as regular documents (objtype 144) then having a solution that can set the email metadata at a later stage (in bulk) is feasible. For example, using REST API calls. There are possibly also tools available to bulk upload metadata to CS16 from a csv file. This only leaves the task to generate the csv file with the metadata. The nature of the solution will be batch-like.
Options Fupload eml files using EC as documents (objtype 144) + use script to extract email metadata into csv format + use tool to bulk load metadata (from csv file)
One thing to be aware of is the naming of the emails. I am not sure what the eml files are named but with msg's saved from Outlook the names are not as useful because they contain sequence numbers like <subject>(1).msg. Because eml's in CS cannot be previewed in the browser users need to open the eml's in their email client. This may slow down the task of finding the "right" email in an email archive. It is good to communicate this upfront.
Paul
