Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling restricted fields in viewer #79

Open
eBrasack opened this issue Aug 9, 2023 · 2 comments
Open

Handling restricted fields in viewer #79

eBrasack opened this issue Aug 9, 2023 · 2 comments
Assignees

Comments

@eBrasack
Copy link

eBrasack commented Aug 9, 2023

We currently do not understand how this viewer would treat fields that are listed as restricted. We understand that restricted fields would be listed in BT-195. Does the viewer still display these fields like any other fields or does the viewer check if the duration of hiding these fields has passed and only then displays these fields? What other logic is applied here?

I already tried addressing this question to the TED helpdesk, they pointed me here.
Thanks in advance

@rousso
Copy link
Contributor

rousso commented Oct 12, 2023

Hi @eBrasack,
Restricted (a.k.a. "unbulished") fields are masked before publication.
The viewer displays the masked value just like it would display any other field.

@pdonohoe
Copy link

Dear @eBrasack , the current logic for the display of restricted/unpublished information fields is that they are only displayed while the value of the unpublished field is masked, i.e. before the Access Date. After the Access Date, when the value of the unpublished field is revealed, the unpublished information fields are not displayed.
This is due to change, so that the unpublished information fields will always be displayed. This will probably take effect with the release of SDK 1.12, and then applied to previous SDK versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants