As shown in the video below, when editors insert new Subject Navigator entries by highlighting the HTML (which will be the case on app.islg), new entries are currently placed as the first entry under the selected branch. This  default location will not work for us.

Subject Navigator entries are presented in chronological order. Can we change the default location of new entries to:
1. Chronologically right place based on the date of the source document (most ideal)?
2. If not, can we insert an option next to each individual entry (not branch) to place a new entry above or below that designated entry (currently an option under legacy site)?
3. If not, can we change the default location to the bottom of each branch, appearing as the last entry of the branch designated?

This video presents option 1 and option 3, but please consider option 2 as well.

Default entry location to the top of each branch and request for chronologically right place (23-Mar-21).mp4 17.4 MB • Download

The same happens when I copy an existing entry and place it under another branch as shown below.

Copying SN entry to another branch (23-Mar-21).mp4 2.81 MB • Download

Thanks,

Paul

Thanks for this Paul . We'll get this integrated into the pipeline as a priority post-launch.

Thanks,

Morgan

Hi Paul ,

We are preferring 3rd option because if we go with first option then again we need to check performance as we need to check with Dispute Document Date for ordering.

Please confirm that option 3rd is good for you ? 

Hi Harsh :

My preference is still option #1. However, please also investigate option #2, as we currently have that option on the legacy admin site when editors insert entries directly; I don't want to lose that ability on app.islg.

Only if the first two options are totally impossible, I will settle for option #3. 

Thanks,

Paul

Hi Paul ,

We checked this task and found that we are providing Reorder functionality. so we are set all the branches as per order number.

It is technically not possible to display document reference branch as per dispute document date. IF we do that thing then reorder functionality will not work.

We can manage order only one way.

We can only do that ascending or descending. so if you want then will do that always new branch will be display at bottom.

Please let us know.

Hi Harsh :

image.png 3.54 KB • Download

You're saying option #1 isn't possible, right?

image.png 2.95 KB • Download

I will settle for option #3 only if you can implement showing each entry's document UIN + short title + document description + date (Subject Navigator Master Tree branches - presentation of Dispute Document entries - TOLOGIX - ISLG App Rebuild)

Thanks,

Paul

Hi Paul ,

This task (Subject Navigator Master Tree branches - presentation of Dispute Document entries - TOLOGIX - ISLG App Rebuild) will take in next sprint.

so in this task just let us know what you need ? In ascending or descending order ?

Hi Harsh :

Please make the default location to the bottom of each branch selected (option #3), so new entries would appear as the last entry of the branch designated. 

We need entries to appear in chronological ascending order (the oldest dated document entry appearing at the top of each branch and the newest document entry appearing at the bottom) as the legacy site currently does now.

Thanks,

Paul
 

Hi Harsh ,

I had a discussion with Paul and he has confirmed that we are fine with proceeding with Option 3: when a new entry is added to the Subject Navigator Master Tree through analysis, the entry will automatically be added to the bottom of the list.

Thanks,

Morgan

Hi Morgan and Paul ,

You need every and each branch to be added at bottom. Suppose if admin user will do Add peer, Add Child, Add Level or any thing then always new branch will be created at bottom.

Am I Right ? Please correct me If i am wrong.

Hi Harsh :

What Morgan asked is only for when editors highlight HTML and right click to insert a Subject Navigator entry. This should NOT affect how new entries are inserted directly under Subject Navigator Master Tree. The only exception is shown below in the video of copying an existing entry to another branch (please make any copied entries to appear at the bottom of a designated branch even if entered directly via Subject Navigator Master Tree).

Copy to another branch entered as the first entry (13-Jul-21).mp4 3.53 MB • Download

Add Peer, Add Child and Add Level are options available only if inserting entries directly under Subject Navigator Master Tree. How they function currently under Subject Navigator Master Tree shouldn't change.

Thanks,

Paul

Hi Harsh ,

We should note that adding the Add Peer, Add Child and Add Level options is essentially what Paul requested in option #2 above. Therefore, if integrating these options into Subject Navigator analysis is possible, let's proceed with that option.

Thanks,

Morgan

Hi Paul ,

As per our discussion on call, We have completed this task on staging.islg. Please check and confirm.

https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/811

Hi Piyush :

As I described below, "Copy to another branch" option is still inserting new entries as the first entry under the destination parent branch selected. Similar to what "Move to another branch" does, please make the "Copy to another branch" option to insert new entries at the bottom of the selected parent branch.

Copy to another branch entered as the first entry 2 (27-Jul-21).mp4 9.35 MB • Download

Thanks,

Paul

Hi Paul ,

The "Copy to another branch" issue is resolved on staging.islg. Please check and confirm.

Thank you, Piyush .