Hi Martin :

I suspect we need Naomi's user story assistance to accomplish this task. I outlined what I would like to see on the subscriber site based on separate opinion information on the admin site.

Could we tackle this in January?

Separate Opinion Direction (15-Dec-21).mp4 6.74 MB • Download

Thanks,

Paul

Hi Paul ,

I agree that this will require a more detailed user story, and that Naomi will be best positioned to help us with that.

Naomi : can you do a review of Paul's request above and let us know your thoughts on the next step? Is a meeting required to further discuss? 
What is your estimate in terms of time required to complete the user story?

Thanks,
--Martin

Hi Paul , 

This video is pretty clear and I believe I understand your goal here. In terms of next steps, I would want to review the existing functionality around the "separate opinion" and notice functionality to confirm there aren't any other implications to be aware of. After that, I could write a user story for this. This should take an hour maximum. 

Let me know if I should proceed. 

Thanks, 

Naomi

Hi Naomi :

How many hours have you spent on ISLG for December so far? I don't believe there was a Knowledge Centre article yet. If you haven't filled your 10 hours yet, please proceed with this item. If you are working on a Knowledge Centre article which will fill up your 10 hours, please work on this in January.

Thank you,

Paul

Hi Paul , 

No I haven't used hours this month for KC content so this will be fine. I would like to confirm something regarding the above video:

Thanks, 

Naomi

Hi Naomi :

Yes, anything that is marked on the admin site currently as a separate opinion would also be flagged as a related document. I want to ensure the following:

Hope it makes sense.

Thanks,

Paul

Hi Paul , 

Yes this makes sense, thanks. Has your team removed the duplicates from the "related document" field when adding the documents to the separate opinion field? Otherwise it may be difficult for the application to recognize when a document has only a separate onion and not also a related document to display just the one notice. 

Thanks, 

Naomi

Hi Naomi :

Unfortunately, there was a previous decision to keep all separate opinions in the Related Document field after we populated the Separate Opinion field. Is there any way to implement a logic where if the UINs under both Separate Opinion and Related Documents are the same, only the new separate opinion notice you create will appear when there are no other UINs under the Related Documents field? If it is too complicated, I will consult with Nafiseh to see how long it would take to remove separate opinion UINs from the Related Documents field.

Thanks,

Paul

Hi Paul ,

I imagine implementing such logic could potentially affect the performance of the site and create unnecessary checks for something that could be fixed once and not needed moving forward. Maybe Martin  can confirm here. 

I've written the user story with the understanding that the Separate Opinion document won't be also duplicated in the Related Documents field. I've tagged you there to review.

Thanks, 

Naomi

Hi Naomi :

Please look at the video below to clarify what the content team needs to clean up for the purpose of this user story.

Separate Opinion Related Documents (21-Dec-21).mp4 5.19 MB • Download

Thanks,

Paul

Hi Paul ,

The team would need to remove the duplicated documents from the "Related Documents" field (duplicated meaning they are populated in the "separate awards field" as well) in both the opinion and award document types. Doing this would ensure only the one notice related to the separate opinion will display on the front end, and not the additional notice that is currently there regarding the "related documents" field.

Let me know if this makes sense, 

Naomi 

Understood, Naomi .

Nafiseh : please go ahead and remove duplicates from both separate opinions and their related award/decision as we discussed. 

Thanks,

Paul

Will do, Paul . Thanks.

Nafiseh

The new card design will address this issue.