Thanks for reporting this Katrina .

Note that video above is in an unsupported format. Would it be possible to convert the video to MP4 format and repost it.

Thanks,

Morgan

Apologies for that and thank you for letting me know Morgan . I've reuploaded the video in MP4 format. 

Thanks, 

Katrina

Great. Thanks Katrina .

Jitesh and Hiren , let us know what your assessment is of the issue above.

Morgan

Morgan and Katrina ,

I can not identify the problem in absence of URL in video so kindly taken video with browser URL to identify the problem.

Thanks,

Hiren

Hello Hiren , 

I have re-recorded the video to include the URL. Please let me me know if you encounter any other issues with the video. 

Thank you, 

Katrina

Hi Katrina ,

The problem is facing due to you are doing whole html selection and doing tagging second time for same text. I think this is not real case scenario and Morgan we need to do proper selection and tagging. unaccepted text selection (entire file) multiple times tagging might be getting issue and it is unpredictable also. so please select proper text rather than entire file.

Thanks,
Jitesh

Hi Jitesh ,

I agree that it will be unlikely to tag whole HTML sections and probably document level tags would make more sense in that scenario. However, we are still experiencing this issue when tagging large portions of text. I included another video to demonstrate that I was experiencing the same loading issue when I tried to tag about 25% of a document. Tagging this much of a document while likely be a common scenario. 

Sch 1 - tagging large portions of text.mp4 6.52 MB • Download

Thank you, 
Katrina

Hi Morgan ,

As per Katrina mentioned issue in provided video, it is unexpected due to jquery manipulation of huge amount of text selection and consider it will be getting in such cases. We have worked out to implement multiple paragraph selection issue as Kevin not provided solution earlier and we have did it but it will produce error in huge amount of text selection. I hope admin will do proper selection of paragraph as per need. Please kindly consider it and make this to do completed.


Thanks,
Jitesh

Hi Jitesh ,

We'll have to workout a solution to this problem. I understand if an excerpt of this size would take longer to load, but we still need to give users the ability to create tags of this nature, because there will be circumstances where it's required for value added analysis. If there a way for us to optimize this and perhaps provide a warning to the user when they are attempting to tag a larger excerpt like this?

Thanks,

Morgan 

Hi Morgan ,

It is good idea to provide a warning to the user when they are attempting to tag a larger excerpt like this. We will look into it and provide feedback.

Thanks,
Jitesh

Ok. Sounds good, Jitesh , but let's ensure we confirm the threshold of when these warning will occur, and determine whether further work needs to be done to accommodate longer excerpts.

Thanks,

Morgan 

Naomi , could you please log the issue above as user stories in TargetProcess.

Thanks,

Morgan 

Hi Jitesh and Morgan ,

I am wondering if this issue could be solved through the manual paragraph reference functionality outlined here: https://industrialagency.tpondemand.com/RestUI/Board.aspx#page=board/5661532064567160038&appConfig=eyJhY2lkIjoiNTBFODBFN0M1RkNFMDJDREQ3MjFFRjYwM0NFNzdGQUQifQ==&searchPopup=userstory/20408 that was raised in this basecamp thread: Create quicklinks function within tag assignment process - PRIORITY - TOLOGIX - Infrastructure LawGuide (ILG) for Tologix. 

In this way, the admin would be able to create a paragraph range of their desired size (ex. pa1-pa65) and this would allow admins to cite larger portions of text, potentially without the technical limitation if they were to highlight it?

Please let me know your thoughts on this, as that could be a solution for this issue as well. 

Thanks, 

Naomi

Hi Naomi ,

That would work for me, and would probably make it easier for users. However, I think there is a problem with the systems ability to identify paragraphs within the HTML, which relates to the item discussed here: https://industrialagency.tpondemand.com/restui/board.aspx?#page=bug/18395&appConfig=eyJhY2lkIjoiN0Q5ODA2RTFGMzEwMThCMjMzQTVEN0RGOThBNTNBQTYifQ==.

This is a broader requirement change that may be required for the application, and something that Jitesh and Hiren need to discuss with   Harsh and the ISLG team to understand how the ISLG solution can be applied in ILG.

Thanks,

Morgan 

Hi Morgan ,

I see. I can go ahead and link this target process story (https://industrialagency.tpondemand.com/RestUI/Board.aspx#page=board/5661532064567160038&appConfig=eyJhY2lkIjoiNTBFODBFN0M1RkNFMDJDREQ3MjFFRjYwM0NFNzdGQUQifQ==&searchPopup=userstory/20408)  to this basecamp thread in target process.

As Jitesh and Hiren have the required conversations, and implement a solution for recognizing paragraphs within the HTML, I can be sure to test this functionality for larger paragraphs in conjunction with the other related to-do item (for adding a tag to multiple paragraphs). 

Does that make sense as a way forward for this issue?

Thanks, 

Naomi 

Sure. Sounds good, Naomi .

Morgan