Hi Dan,

Roughly there are two flows to do baseline version management for publications

1. The typical one is using Publication Manager, and create or select version of content objects there.
2. A small minority of customers allows their authors to deliberately create new versions from their preferred Xml Editor (with Authoring Bridge). Any newly created version is unattached to a publication. To close that gap people can select an existing baseline through the Candidate For Baseline field. Later on the Publication Manager user can select that baseline to do baseline versioning for his Publication through an AutoComplete action (see documentation below)

http://docs.sdl.com/LiveContent/content/en-US/SDL%20Knowledge%20Center%20full%20documentation-v2/GUID.30330F01.D0ED.4EF6.A566.6EF8B024D446

[...]
Candidate for baseline

This Autocomplete behavior assigns versions marked as candidate for the specified Baseline to complete yours. This affects any object that are linked as candidate to the selected Baseline.

Each object can be linked to a Baseline as "candidate", as part of its properties.

Click Select Baseline. You are prompted to select the baseline to use.

After you confirm by clicking the Autocomplete button,Publication Manager will consider any object marked as candidate to the selected Baseline that is used in your publication. When there is no version for an object in your publication, Autocomplete will assign it from the corresponding candidate. If an object has a different version between your publication and the corresponding candidate, Autocomplete will propose a change and a confirmation dialog lets you choose if the replacement is performed or not.
[...]

Welcome back Dan.

In essence the 'Candidate for Baseline' field is a metadata field on the version level of topics, maps and alike. So any operation that retrieves the material and filters for a certain baseline identifier should work.

So to get you going the below suggestions. Remember that the result set could eventually return your full database.

• Make it search-able over the FullTextIndex by adapting C:\InfoShare\Web\Author\ASP\ClientConfig\MetadataConfig.xml on the server which is synchronized to your Client Tools. Near "<ishfrm id="Trisoft.InfoShare.Forms.Searcher.SearchControl">" add an entry after "<ishfrmfield name="CheckedOutByField" ishfieldref="CHECKED-OUT-BY" level="lng">" that looks like
  • <ishfrmfield name="ReleaseCandidateField" ishfieldref="FISHRELEASECANDIDATE" level="version">
                <label resourceref="FISHRELEASECANDIDATE.Label">C&amp;andidate for baseline</label>
                <description resourceref="FISHRELEASECANDIDATE.Description">Candidate for baseline.</description>
                <typetext assist="yes" filter="yes">
                  <valuelist ref="ActiveBaselineList" />
                </typetext>
                <multivalue />
       <fulltextsearchoperator>equal</fulltextsearchoperator>
              </ishfrmfield>
• Or do an API call directly or over the PowerShell automation library. So use Find-IshDocumentObj with a metadata filter on the FISHRELEASECANDIDATE field
• ...

Best wishes,
Dave