Considering that we are only 3 days away from ending the sprint, and given that we are in the process of completing sprint items, I would prefer we create a bug that can be tackled at the beginning of the next sprint.
Does that work?
Thanks, -Martin
Notified 1 person
Paul Moon
Hi
Martin
:
As long as this could be tackled as a first item (please create a DevOps item) and released to app.islg within the first days of the next sprint, it'd be ok. I need this fixed, as this will be featured in the Article Citator Tutorial video, as well as the ICSID tutorial scheduled for May 9th.
Please prioritize to the top and we will tackle it either in this sprint (if time permits), or early next sprint.
Thanks, -Martin
Order #1
Notified 1 person
Martin Laporte,CTO
Hi
Harsh
: please note that this item is higher in priority.
If you or
Piyush
have the bandwidth to address in this sprint, you can drag it directly into Sprint 16. Otherwise, can you tackle as a first priority in Sprint 17?
Thanks, -Martin
Notified 3 people
Martin Laporte,CTO
Hi
Paul
,
Based on the conversation I had with the team this morning, the behaviour we see in the new ISLG is aligned with the user story.
The sort by number of references most referenced is counted from this entry:
It appears the user story has not been entirely correct; could we discuss this later next week?
Thanks,
Paul
Notified 3 people
Martin Laporte,CTO
Tagging
Naomi
.
Notified 4 people
Naomi Joanis,UX Team Lead
Hi
Paul
,
I looked into this a bit more and also discussed with Mel. Ultimately this was a deliberate decision with Morgan to allow the sorting for "Most referenced" on dispute documents to provide the higher level context as to why certain documents are important. The thinking here is that 1) likely most referenced paragraphs will mean the document itself will be among the most referenced, and 2) users are looking for context around important documents, not just the specific paragraphs.
Making a change to this would be quite a large task, as the entire application is organized around the structure of dispute document listings, and breaking this to allow the structure to be around the paragraphs would require a lot of rethinking (in both UI and functionality).
The insight into number of paragraph citations is currently available when hovering over the paragraph label. We suggest evaluating whether or not the ability to sort in this manner offers enough value to justify the effort required.
Thanks,
Naomi
Notified 4 people
Paul Moon
Hi
Naomi
:
Thanks for this explanation. I do not agree with Morgan's assessment, because it dilutes the precision of Article Citator (i.e., by referring users back to "all" references to the dispute document that may not be related to the specific reference, ICSID Convention Article 25 in this example, that brought the users to this page in the first place), so we should've not sacrificed the Passage Most Frequently Cited sorting function in the legacy in lieu of Most Referenced that we have.
Considering we have more pressing matters, I'll move this item for future development for now, once and when we have more capacity.
As shown below, Article Citator's most referenced sorting function is not working as expected. Please add it to unplanned/critical.
Thanks,
Paul
Considering that we are only 3 days away from ending the sprint, and given that we are in the process of completing sprint items, I would prefer we create a bug that can be tackled at the beginning of the next sprint.
Does that work?
Thanks,
-Martin
As long as this could be tackled as a first item (please create a DevOps item) and released to app.islg within the first days of the next sprint, it'd be ok. I need this fixed, as this will be featured in the Article Citator Tutorial video, as well as the ICSID tutorial scheduled for May 9th.
Thanks,
Paul
DevOps bug https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/1776 was created.
Please prioritize to the top and we will tackle it either in this sprint (if time permits), or early next sprint.
Thanks,
-Martin
If you or
Thanks,
-Martin
Based on the conversation I had with the team this morning, the behaviour we see in the new ISLG is aligned with the user story.
The sort by
number of referencesmost referenced is counted from this entry:We can further discuss when we are all on our Monday Zoom call.
Thanks,
-Martin
Ok, I look forward to the user story.
Sort by "Number of References" is working as expected, but sort by "Most Referenced" is what I have an issue with.
Thanks,
Paul
Sorry, I meant to say "Most Referenced" instead of "Number of References" in my comment above.
Here is the link to the user story:
https://industrialagency.tpondemand.com/restui/board.aspx?#page=userstory/7643
-Martin
It appears the user story has not been entirely correct; could we discuss this later next week?
Thanks,
Paul
I looked into this a bit more and also discussed with Mel. Ultimately this was a deliberate decision with Morgan to allow the sorting for "Most referenced" on dispute documents to provide the higher level context as to why certain documents are important. The thinking here is that 1) likely most referenced paragraphs will mean the document itself will be among the most referenced, and 2) users are looking for context around important documents, not just the specific paragraphs.
Making a change to this would be quite a large task, as the entire application is organized around the structure of dispute document listings, and breaking this to allow the structure to be around the paragraphs would require a lot of rethinking (in both UI and functionality).
The insight into number of paragraph citations is currently available when hovering over the paragraph label. We suggest evaluating whether or not the ability to sort in this manner offers enough value to justify the effort required.
Thanks,
Naomi
Thanks for this explanation. I do not agree with Morgan's assessment, because it dilutes the precision of Article Citator (i.e., by referring users back to "all" references to the dispute document that may not be related to the specific reference, ICSID Convention Article 25 in this example, that brought the users to this page in the first place), so we should've not sacrificed the Passage Most Frequently Cited sorting function in the legacy in lieu of Most Referenced that we have.
Considering we have more pressing matters, I'll move this item for future development for now, once and when we have more capacity.
Thanks,
Paul