Migration

2.0.0 ➡ 3.0.0

When updating from 2.0.0 to 3.0.0 there's some new features that requires new configuration in Open Content. These are ArticleSize and ArticleMetaAssignmentUuid. These properties should be added by updating OC with the latest version of the default OC configuration.

Since this is a major release with large changes in how we configure, we recommend that you save your current configuration, reset the configuration in the application, and then make manual changes to the features you had earlier.

Otherwise you will need to go over each config part and try update where you see fit but you might miss out on something.

Remember to check the requirements page for Newsroom Planner.

indexfields:
    - name: ArticleMetaAssignmentUuid
      type: STRING
      multivalued: false
      readonly: false
      suggest: false
      description: Uuid to assignment the article linked to used in NRP

    - name: ArticleSize
      type: STRING_LOWERCASE
      multivalued: false
      readonly: false
      suggest: true
      description: DO NOT DELETE OR CHANGE... Size of article

contenttypes:
    - Article:
        - name: ArticleMetaAssignmentUuid
          type: STRING
          multivalued: false
          searchable: false
          readonly: false
          description: UUID to assignment used in NRP
          indexfields:
            - ArticleMetaAssignmentUuid
            
        - name: ArticleSize
          type: STRING
          multivalued: false
          searchable: false
          readonly: false
          description: DO NOT DELETE OR CHANGE... Size of article
          indexfields:
            - ArticleSize

xpathextractors:
    - id: be624432-5ee6-4609-9e3e-7727f336cd07
      property: ArticleMetaAssignmentUuid
      contenttype: Article
      mimetype: application/vnd.iptc.g2.newsitem+xml.article
      xpath: /*:newsItem/*:itemMeta/*:links/*:link[@rel='assignment']/@uuid
      ignoreroot: false

    - id: c5d04093-5fd8-4b83-bfaa-6183b86e0d47
      property: ArticleSize
      contenttype: Article
      mimetype: application/vnd.iptc.g2.newsitem+xml.article
      xpath: /*:newsItem/*:itemMeta/*:links/*:link[@rel="content-size"]/substring-after(@uri, "im://content-size/article/")
      ignoreroot: false

If you want to utilise the new Email notification service for assignments, Some new key store values has to be added.

• EMAIL_SERVICE_SEND

• EMAIL_SERVICE_LIST

• EMAIL_SERVICE_DOMAIN

These should point to the sendmail service corresponding with the environment your NRP is running in.

1.x.x ➡ 2.0.0

If you've been running NRP in a prior version to 2.0.0 you probably already have Events which will not look complete when running the new version. This due to us adding priority on Events in current version.

A event card without priority info in XML

Same event now with complete priority info

In order to make these look okay a migration of content is needed.

in the XML you'll need to add the tag <urgency></urgency> with a value depending on which priority you want the item to have.

[...]
<contentMeta>
    <contentCreated>2020-01-29T14:09:25.539Z</contentCreated>
    <contentModified>2020-03-02T14:33:32.580Z</contentModified>
    <description role="nrpdesc:extern">l</description>
    <contentMetaExtProperty type="nrp:sector" literal="Domestic" value="domestic"/>
    <links xmlns="http://www.infomaker.se/newsml/1.0"/>
    <urgency>2</urgency>
</contentMeta>
[...]

You'll also have to load OC with the new config for NRP. This will add the extractors, properties and index fields needed for the priority on Events.