TOLOGIX - ISLG App Rebuild

Document 2021-05-27 - Weekly Tologix-DevIT-Industrial Meeting.mp4 (342 MB)

Download ↓

Hi everyone,

Here is the recording from today's meeting, and here are the relevant actions items:
  • Naomi Joanis, UX Team Lead at Industrial Naomi and Melissa Cowell, General Manager at Industrial Melissa , please share copies of the complete wireframes with the updates to the results view and document view within ILG, and Morgan Maguire, CEO Morgan will provide final review/comments before work is completed on writing the relevant user stories. 
    • We will plan to have a meeting next Thursday to review and finalize the requirements ( Martin Laporte, CTO at Tologix Martin and Jitesh Dhuravala, DevIT Jitesh , please comment below on whether we should invite Rob Wiesenberg, Contegra Rob   and Radomir Mladenovic, Contegra Radomir  to the meeting to review the requirements with us).
  • Harsh Parikh, Tech Lead at DevIT Harsh , please provide Jitesh Dhuravala, DevIT Jitesh and Akash Buch Akash with copies of the HTML documents that have been causing issue within the ISLG application: Re: UN/0101/14 Issues on the Live Site - TOLOGIX - ISLG App Rebuild and Jitesh Dhuravala, DevIT Jitesh and Akash Buch Akash will consult with HTML technical review team to understand the issues and ensure the appropriate adjustments are made to ensure issues to do not get missed during future documents.
Thanks,

Morgan

Comments & Events

Morgan M. posted this on · Download ↓
Martin Laporte, CTO at Tologix
Hi Morgan Maguire, CEO Morgan ,

Jitesh Dhuravala, DevIT Jitesh and I just discussed, and we will organize a session with Rob Wiesenberg, Contegra Rob and Radomir Mladenovic, Contegra Radomir after our meeting next Thursday, once we better understand the application requirements. 

So no need for them to attend our June 3 session.

Thanks,
--Martin
Morgan Maguire, CEO 👍
Morgan Maguire, CEO
Hi Melissa Cowell, General Manager at Industrial Melissa and Naomi Joanis, UX Team Lead at Industrial Naomi ,

Following-up on above, I haven't been sent the wireframes to provide comments. Could you please send those to me today so that you can integrate that feedback into your user stories and updated wireframes?

Thanks,

Morgan
Morgan Maguire, CEO
Hi Harsh Parikh, Tech Lead at DevIT Harsh , Jitesh Dhuravala, DevIT Jitesh and Akash Buch Akash ,

Could you please report back on the action item above.

Thanks,

Morgan
Naomi Joanis, UX Team Lead at Industrial
Hi Morgan Maguire, CEO Morgan

Here is the link to the wireframes: https://invis.io/4JTAJLMZ3HR

Thanks, 

Naomi
Morgan Maguire, CEO
Thanks Naomi Joanis, UX Team Lead at Industrial Naomi . I've inserted one comment into the wireframe but otherwise everything looks good. The only other outstanding issue that I need further confirmation on is the use of the term "paragraph" within ILG. This term has been carried over from ISLG, but it may not be appropriate in the context of agreements/contracts, rather than decision and awards. We may need to replace this term globally across the application with term like provision, clause or section.

I'll provide more details later today.

Morgan 
Naomi Joanis, UX Team Lead at Industrial
Hi Morgan Maguire, CEO Morgan

Thanks for reviewing and confirming. I have also responded to the comment in Invision. I will go ahead and start writing user stories for this and tag you to review. 

Thanks, 

Naomi
Morgan Maguire, CEO
Hi Naomi Joanis, UX Team Lead at Industrial Naomi and Jitesh Dhuravala, DevIT Jitesh ,

I've discussed this internally and the best term for us to use is "section" or "section(s)" when referring to any location with a document. This means that we'll need to replace the term "paragraph" or "paragraph(s)" with "section" or "section(s)" across the application. Also, I believe "section" or "section(s)" is being used in other context in the wireframes to refer to document details and project details:


We'll need to modify or remove this term from any existing copy across the application and ensure the term "section" or "section(s)" is reserved only to refer to locations within documents.

In addition, we'll need to modify the way "sections" are displayed in as pinpoint references. We'll need ensure "pa" is automatically removed from the display link and only the number is displayed:

Note this should be done globally within the application, both on the admin site and subscriber site.

Thanks,

Morgan
Morgan Maguire, CEO
Hi Jitesh Dhuravala, DevIT Jitesh and Martin Laporte, CTO at Tologix Martin ,

I just thought of an issues that we should consider before we start working on altering the result view and document views. There is a strong possibility that we will launch ILG without a "Browse By Topic" feature and launch a more basic product that only has "Search by Keyword" and "Browse By Project" features. As a results, we will likely need to supress all features related to browsing by topic from the subscriber side of the application for a period of time:
In addition, when we eventually release this feature, we will likely limit access to certain tiers of subscriber. Ideally access to the relevant features would be controlled at the user and group level settings.

I raise this now, because I'm wondering if certain steps should be taken now to ensure there is this flexibility is the system before we start modifying searching features on the subscriber side of the application.

Thanks,

Morgan