Tasks and Analysis Data
Can you please provide your input on the following scenario that has come in discussion:
A document is uploaded and converted, edited and analysis data capture has been performed. Now approve admin finds some issue with the document text and switches the task to 'Edit' in order to update the HTML text.
- What happens with the Data Capture analysis? Based on what we've seen in ILG it looks as thought the tagging data will be maintained. Can you confirm?
- If the user editing the text deletes and entire tagged excerpt, will the reference data be removed from the relevant research tool?
- If the user add/edits text within the excerpt area, will the tagged excerpts be updated in the relevant research tool?
I don't believe this scenario was ever described, so your input would be appreciated. We have not seen all of the task features yet however it seems as though some of this may already be working as we hoped (in ILG) and would love if you could confirm.
Thank you,
Melissa
We are internally discussed above points and mentioned the appropriate answer.
What happens with the Data Capture analysis? Based on what we've seen in ILG it looks as thought the tagging data will be maintained. Can you confirm?
If the user editing the text deletes and entire tagged excerpt, will the reference data be removed from the relevant research tool?
Thanks for the answers above. I've added this to the agenda for discussion tomorrow.
Note that we'll need to maintain the ability to edit HTML text after analysis is performed to ensure we can correct problems with the HTML text that only get discovered after the document is scrutinized through analysis. Therefore, we'll need to build in requirements that will maintain the integrity of the analysis data and notify the admin user when a scenario occurs similar to what you've described above.
Also, the requirements we build will be useful in tacking and correcting issues that arise when migrate data from the old application that may not match-up correctly with the new HTML text and tags in the new application. We could use this as a tool for identifying and resolving problems that would otherwise require trial and error testing by users.
Thanks,
Morgan
We will provide admin to edit HTML text after analysis is performed to ensure we can correct problems with the HTML text that only get discovered after the document is examine through analysis. To achieve this behavior we are planning to do as per following.
1, Admin can change html text as per his/her needs but he/she can not able to changed text of first and last line of paragraph on which admin has already tagged and saved in database. middle of text of tagged html text he/she can change but first and last line should be read only in order to maintain our logic and functionality. Even if Admin want to change first or last line of tagged text than he/she need to delete that particular tagged from document and save than edit html text as per he/she want after that he need to do again tagging.
2, Second, after migration from old to new application all excerpt/tagged paragraph will be migrate and display as per current tagging functionality in new application. but what about those excerpt/tagged which are broken down due to manually added in old application. We would display those broken excerpt/tagged in one notification message so please let us know where we need to display.
Thanks,
Jitesh
Re changing HTML text while tagging, understood. Based on what you've described above, assuming there are no tags applied to the applicable text, would the admin user be able to edit all text in the paragraph? Let's discuss tomorrow, but this may work.
Re broken tags post-migration, it's important that the notification message provide a list of the specific tags from the old application that didn't get integrated into the HTML text of the new application. That way the admin user will be able to identify and manually modify/add tags to the HTML text as necessary. Also, we'll need to generate a report after performing the migration that lists all the documents (and applicable tags) where such issues are occurring. Let's discuss how to implement this during tomorrow's call. However,
Thanks,
Morgan
Further to our discussion this morning, we'll proceeding with resolving the issue above as follows:
Note that each type of tag is given it's own tab, and each tag will occupy a row in the report. Therefore, if a document has multiple broken tags across multiple types, it could have multiple rows in multiple tabs.
Let me know you thoughts, and we can discuss in more detail during the call next Thursday.
BTW:
Thanks,
Morgan
In preparation for tomorrow's meeting, could you please provide an update on the items above.
Any progress on the R&D?
Is the proposed sample report work for you?
Thanks,
Morgan
Partially we have done R&D about how to HTML text read-only when a tag has been inserted into the text but we have not implement and integrated in our application, We will update you soon.
Yes, you have proposed sample report is fine and understandable.
Thanks,
Jitesh
Could you please provide an update on the above.
Thanks,
Morgan
We will look into it once ISLG admin cards complete. This is 3 to 4 days R&D task and will complete between 15 to 20th April.
Thanks,
Morgan
I have created a card with the relevant details here:
https://industrialagency.tpondemand.com/entity/15093-randd-greater-editing-html-text-after
Mel
Morgan
Could you please provide an update on the progress made concerning R&D on the issue above.
Thanks,
Morgan
Yes. We are planning to complete this story by 20th April. Team is working on this and will update you once it is completed.
Morgan
We have completed this R&D and integrated in HTML editor. Now, The HTML text will freeze in html editor if user performed tagged on that html text.
We will deploy this change with other stories on 23rd April.
Morgan
I'm adding this to the agenda for tomorrow's call. Referring to item #2 from my post on March 5th above, I'd like to discuss and confirm that work is being done to prepare and create reporting tools needs to identify and address broken tags that may occur during the final migration.
Thanks,
Morgan