Need to use the API or IshRemote to create publication objects

Hello,

I am trying to automate the creation of CCMS publications. I've been able to create a script that generates and imports the publication data (maps, topics, media, etc), however, I'm stuck on the creation of the actual publication objects. To be clear, I'm not referring to publication outputs, but instead I am trying to create the top-level publication object that contains links to the baseline, bookmap, resources, and outputs as well as persisting the conditionalization settings among other metadata.

I probably overlooked something as the absence of this functionality is a pretty big problem in terms of automation. I looked through the API docs and also reviewed the IshRemote help, but I found no mention of publication objects or methods to manipulate them. I also searched this site and the internet for other mentions, but found nothing. Either the methods for creating publication objects is painfully obvious and isn't documented, or it doesn't seem to exist. 

Can anyone confirm that top-level publication object creation is possible via the API and, if possible, point me to documentation or a code example?

Thanks in advance,
josh

emoji
Parents
  • Hi Josh,

    Agreeing with Greg's answer. Allow me to add that ISHRemote Add-IShPublicationOutput is the cmdlet that is about as close as you can get. C# source code is on https://github.com/RWS/ISHRemote/blob/master/Source/ISHRemote/Trisoft.ISHRemote/Cmdlets/PublicationOutput/AddIshPublicationOutput.cs

    Why close, because in general Tridion Docs is trying to avoid incomplete logical-version-language hiearchies from a UX perspective. So for Content Objects, like an OASIS DITA Topic, it means that only creating the Logical level (GUID, Title, etc) and Version level (Version number, changes field, etc), missing Language level (Language, status, author, etc) is not encouraged. These partial objects complicate retrieval, search, reporting, etc user experiences.

    You are asking a similar question for Publications where the Logical level (GUID, Title, etc) and Version level (Version number, baseline, condition-context, changes field, etc) is often known as "a Publication" and when adding the Lanuage level (language, outputformat, fall-throughs, status, etc) is known as "a PublicationOutput".

    You can use https://docs.rws.com/992527/70028/tridion-docs-15/publicationoutput-2-5-create to create only Logical and Version. If you can make a meaningfull Language, so PublicationOutput, then it will bring a better user experience in the future.

    Best wishes,
    Dave

    emoji
Reply
  • Hi Josh,

    Agreeing with Greg's answer. Allow me to add that ISHRemote Add-IShPublicationOutput is the cmdlet that is about as close as you can get. C# source code is on https://github.com/RWS/ISHRemote/blob/master/Source/ISHRemote/Trisoft.ISHRemote/Cmdlets/PublicationOutput/AddIshPublicationOutput.cs

    Why close, because in general Tridion Docs is trying to avoid incomplete logical-version-language hiearchies from a UX perspective. So for Content Objects, like an OASIS DITA Topic, it means that only creating the Logical level (GUID, Title, etc) and Version level (Version number, changes field, etc), missing Language level (Language, status, author, etc) is not encouraged. These partial objects complicate retrieval, search, reporting, etc user experiences.

    You are asking a similar question for Publications where the Logical level (GUID, Title, etc) and Version level (Version number, baseline, condition-context, changes field, etc) is often known as "a Publication" and when adding the Lanuage level (language, outputformat, fall-throughs, status, etc) is known as "a PublicationOutput".

    You can use https://docs.rws.com/992527/70028/tridion-docs-15/publicationoutput-2-5-create to create only Logical and Version. If you can make a meaningfull Language, so PublicationOutput, then it will bring a better user experience in the future.

    Best wishes,
    Dave

    emoji
Children