My question is: for each of these options, can I import historic versions "out of sequence", or must I import them in ascending order by major and minor version, starting with the first version 0.1 document?
Versions should be added in sequence in ascending order.
Also, when I create a document using any of these methods, can I specify a version number?
I don't believe any of the listed methods allows you to explicitly set the major/minor version number. However, major/minor numbers can be programatically changed with OScript. You might consider writing a small extension to whatever method you choose to control this.
Hi Patrick,
Typically versions added to CS are auto-numbered; CWS follows this rule as it "does what a user could do". Object Importer however needs to be able to reproduce what Object Exporter generates. As such it does provide the ability to set particular numbers on versions -- minor or major -- during their creation, so long as the numbers are increasing i.e. reflect a possible chronological progression.
Please see the documentation [1] for details.
-chris
[1] https://knowledge.opentext.com/knowledge/piroot/llessoi/v100500/llessoi-agd/en/html/llesoi-cfile-doc-rf.htm
My understanding (which might be wrong) is that you can set arbitrary version number information for Object Importer. However, there is special handling around version 1 / object level which you should check. Also note… some of the version handling changed in the last year, so there may be differences between 10.5 and 16.2, for example.
Patrick
From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]Sent: Thursday, July 20, 2017 12:29 PMTo: eLink Recipient <devnull@elinkkc.opentext.com>Subject: Importing multiple historic versions 2
Importing multiple historic versions 2
Posted by Webster, Chris On 07/20/2017 12:26 PM
Please seethe documentation [1] for details.
[To post a comment, use the normal reply function]
Topic:
Importing multiple historic versions
Forum:
Content Server Development Forum
Content Server:
Knowledge Center CS16
Good to know! Thanks for the correction.
Well, after some false starts, I can confirm that Object Importer does do what I want, with a couple of caveats.
Firstly, you need to specify both the <versionmajor> and <versionminor> tags in the control file. For example, to add version 10.4 of a document, you need to include the following, which is not clear from the OI 10.5 Administration and User guide:
<versioncontrol>TRUE</versioncontrol> <versionmajor>10</versionmajor> <versionminor>4</versionminor>
More seriously, I have found an apparent bug in how OI validates the correct sequencing of major and minor version numbers. The validation fails once you load ten or more minor versions and then try to load the next major version. For example, you can load the following sequence of versions (majors bolded)without problem: 1.0, 2.0, 2.1, 2.2, 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, 5.7, 5.8. 5.9, 5.10
but if you now try to load major version 6.0, OI fails the node, with a message that you must load version numbers in sequence. This error occurs every time I try to load a new major version immediately after a minor version >= 10. It doesn't seem to matter what the preceding major version and minor version numbers are, as long as the minor version >= 10. I have seen this error when trying to load major version 63.0 after minor version 62.14, for example.
I believe that the version numbering problem has been fixed as of Content Server 16.0.2 (September 2016).
From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]Sent: Friday, August 11, 2017 3:22 PMTo: eLink Recipient <devnull@elinkkc.opentext.com>Subject: RE Importing multiple historic versions 2
RE Importing multiple historic versions 2
Posted by McManus, Patrick On 08/11/2017 03:13 PM
More seriously, I have found an apparent bug in how OI validates the correct sequencing of major and minor version numbers. The validation fails once you load ten or more minor versions and then try to load the next major version. For example, you can load the following sequence of versions (majors bolded)without problem:1.0, 2.0, 2.1, 2.2, 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9,4.0, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, 5.7, 5.8. 5.9, 5.10
but if you now try to load major version6.0, OI fails the node, with a message that you must load version numbers in sequence. This error occurs every time I try to load a new major version immediately after a minor version >= 10. It doesn't seem to matter what the preceding major version and minor version numbers are, as long as the minor version >= 10. I have seen this error when trying to load major version 63.0 after minor version 62.14, for example.
That's good to know, but I don't know what our upgrade plans are for the near future. if we raise a ticket for this bug in 10.5, what are the odds of a patch being released to fix it, given that this is now a couple of versions past current, at least?
Not impossible, but certainly unlikely. We are relatively aggressive in trying to limit investment in older versions of software to maximize the improvements and fixes for latest updates.
