nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Migrating Metadata from Lotus Notes to TeamSite

rohitspathak123

Hi ,

Background
We have a requirment i which we have to migrate content from Lotus Notes to TeamSite & also the metadata associated with each content.

Query
Lotus Notes maintains the version history of each file ( like TeamSite does i.e, content creator, series of modification made , different version of same file etc ) .

We are able to get the revision and version history of the files from Lotus Notes.

Just want to know how we can apply these metadata information to TeamSite.
We have the command called iwextattr -s.

How do we store the version control informations.

For e.g., Suppose we have a file X. It has been modified 5 times by five different authors .Is there set this information to TeamSite for any given file X.

I know with the help of iwextattr -s we can set the attribute , but how we do for these version control attributes.

Regards
Rohit

Find more posts tagged with

Comments

nipper

How important is this ? Also what OS ? On Unix I have run something like this:

get file & metadata
copy file to new location
switch user to author who changed that version
iwsubmit with comments about date.

From what I have seen the history is seldom used. You could take the previous check-in date, user, etc and make that a comment for the iwsubmit. That will be easier and then you do not need to have all the previous users in TS.

Andy

hideColumnBasedOnParameter.rptdesign

gzevin

How important is this ? Also what OS ? On Unix I have run something like this:

get file & metadata
copy file to new location
switch user to author who changed that version
iwsubmit with comments about date.

From what I have seen the history is seldom used. You could take the previous check-in date, user, etc and make that a comment for the iwsubmit. That will be easier and then you do not need to have all the previous users in TS.

Andy

well, that is all doable, but one will have to script:

1. versioning of individual files
2. versioning of editions

I am not sure this is all doable within a reasonable budget.... Sacrifices will have to be made somewhere.. Smiley Happy

nipper

well, that is all doable, but one will have to script:

1. versioning of individual files
2. versioning of editions

I am not sure this is all doable within a reasonable budget.... Sacrifices will have to be made somewhere..

reasonable budget ? Why would we be concerned about that ? I flew some marginally competent consultant from Australia a couple times for a project.

reasonable, yea right.

:-)

gzevin

reasonable budget ? Why would we be concerned about that ? I flew some marginally competent consultant from Australia a couple times for a project.

reasonable, yea right.

:-)

that was an exception that is the proof of the rest Smiley Happy

Sailesh

Don't think you can maintain the version history from Lotus to Teamsite, you can though set the other extended attribute but not the version.

gzevin

Don't think you can maintain the version history from Lotus to Teamsite, you can though set the other extended attribute but not the version.

not directly. but something could be done about it, as nipper and myself have mentioned

Sailesh

One option is then to pick each file from Lotus (from version history), bring it to teamsite set extattr and submit it to teamsite with same user information as in Lotus.

One doubt I have though is Lotus keeping each version as the new file like teamsite or is it incremental update like other CVS? If it is case of later then that is big issue.