question

Upvotes
Accepted
16 5 8 12

N2_UBMS equivalent FIDs in MRN_STORY

Hello Team,

We are using the following 4 FIDs to retrieve real-time news via "N2_UBMS" RIC.

1) STORY_ID
2) STORY_TYPE
3) AREA_ID
4) SF_NAME

Please advise the equivalent FIDs in RIC "MRN_STORY".

Thank you.

Regards,

elektronrefinitiv-realtimeelektron-sdknewsmrn
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Upvotes
Accepted
16 5 8 12

@Warat B.@Umer

Thank you both for your responses and the explanation.It is much clearer now.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Upvotes
4.4k 10 6 9

Hi @NWM

These fields are either field for TR's back-end system or deprecate fields which are no longer part of MRN.

  1. STORY_ID is a unique ID.
    MRN now use "id" field in MRN's JSON and GUID in the feed envelope as a unique ID.
  2. STORY_TYPE is the type of the take as supplied by editorial.
    The type is now determined by "messageType" field in MRN's JSON.
  3. AREA_ID and SF_NAME are back-end fields that identify the source feed. They are no longer part of MRN.
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Upvotes
16 5 8 12

@Warat

Thank you for the confirmation. Please close this ticket.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Upvotes
16 5 8 12

@Warat

Apologies, please do not close this ticket now. One question regarding FID "STORY_TYPE". In the MRN/N2_UBMS FieldMapping document provided by Reuters, there is no mapping provided between "STORY_TYPE" and "messageType".

Also, in the article below

https://developers.refinitiv.com/en/article-catalog/article/machine-readable-news-mrn-n2_ubms-comparison-and-migration-guide

the equivalent of "messageType" is "DSPLY_NAME".

Please reconfirm the MRN equivalent of N2_UBMS FID "STORY_TYPE" and possible values.

Thank you.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Hi @NWM

STORY_TYPE is deprecated. It has no direct equivalent field.

The type is now determined by "messageType".

Upvotes
16 5 8 12

@Warat

Thank you for the reply.

With reference to your earlier post,

[STORY_TYPE is the type of the take as supplied by editorial. The type is now determined by "messageType" field in MRN's JSON.]

However, looking at the value of "STORY_TYPE", it is always "S".

Whereas, the values of messageType and "FID#3 DSPLY_NAME" of N2_UBMS seem to be similar (1 character 0~8 depending on whether it is alert, first take,correction,etc..)

Agreed STORY_TYPE is deprecated however the value of "STORY_TYPE" is always "S" so it does not match the value of messageType.

So, please help to clarify in N2_UBMS what was the significancne of "STORY_TYPE" and the meaning of the value "S" ?

Thank you for your support.

Regards

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

@NWM

The value is set by the editorial team.

The value itself has no meaning from the client point of view.

But from the Elektron server point of view, "S" is normal news, while "Z" is permanent news.

So, what's permanent news?

In N2_UBMS, you have to get the news headline and PNAC from <N2_UBMS> RIC. Then use the PNAC to get the story body.

Normally, the PNAC story body is only available for 24 hours. But if the news is permanent, then it will be kept on the server indefinitely.

This is no longer the case in MRN, the client now receive both headline and body from MRN_STORY.

story-type.png (83.0 KiB)
Upvotes
20.3k 73 10 20

Hi @NWM

STORY_TYPE was used to Indicate the permanence type of story where Z meant Permanent Item anything else meant non-permanent. As my colleauge mentioned it has been deprecated.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Click below to post an Idea Post Idea