‹ Home
Exported

TOLOGIX - Infrastructure LawGuide (ILG)

Harsh Parikh, Tech Lead at DevITMelissa Cowell, General Manager at IndustrialDevaang BhattMorgan Maguire, CEO at TologixHiren PatelMarysia RaptisPaul MoonIrit WeinfeldPrerak Shah, Executive Director & Jt CEO at DevITPatrick Harris, Web Designer at IndustrialPiyush Kanpariya, DevITRob Wiesenberg, ContegraRadomir Mladenovic, ContegraKetan Sondarva, Technical Project Manager at DevITStephanie Ducasse, Web Developer at Industrial +10 others
From the list: ILG Prototype

✔ Problem with Meta Fields and Value List design

Morgan M. added this on
Completed by Morgan M.
Assigned to
Anil Vaghela Anil V. Hiren Patel Hiren P. Melissa Cowell, General Manager at Industrial Melissa C. Stefanie Gibson, UX Researcher at Industrial Stefanie G.
Notes
Further to the video below, I believe we need to revisit the design of how meta fields are presented to admin users at the project vs. document level, and also reconsider how values in the value list are used and assigned to different value types. The current setup will lead to redundancies and duplicate entries, and we need to come up with a solution before we proceed with further document uploads.

Stefanie Gibson, UX Researcher at Industrial Stefanie and Melissa Cowell, General Manager at Industrial Melissa , I've proposed making the meta fields presented at the project level and document level only be those that have been added to their respective Meta Field lists. Also, I've proposed making all values appear as available options in any type of meta field (both project and document meta fields), and that when a value is assigned to a project or document, the value type is automatically adjusted in the value list.

Please review and provide your suggested solutions to the problem. Note I know there is still some outstanding discussion on these issues on TargetProcess. Apologies if this is interfering with that process.

Thanks,

Morgan

Problem with Meta field and Value List Design (24-May-18).mp4 23.4 MB • Download

Comments & Events

Morgan Maguire, CEO Morgan Maguire, CEO
In addition to the above and further to the video below, the crux of the Meta Field problem seems to be the option to make a Meta Field "Value Type(this will make this field available across all projects and documents.)". There is no reason why a meta field needs to appear at both the project and document level. A document automatically inherits the meta data of a project when it is assigned to that project, so there's no need for a meta field to appear at both the project and document level.

Problem with Meta fields option (24-May-18).mp4 6.56 MB • Download
Notified 5 people
Morgan Maguire, CEO Morgan Maguire, CEO
Sorry, one more comment to add (and video below), we currently treat document meta fields differently from project meta fields. Project meta fields are tied to the value list, and data added to these fields will affect the value list (and vice versa). On the other hand, document meta fields are plain text fields with no connection to the value list. I don't understand why there is no connection between the document meta fields and the value list. These meta fields should be setup the same way as the project meta field, and tied to the same value list.

Thanks,

Morgan
Problem with Document Meta Fields (24-May-18).mp4 8.88 MB • Download
Notified 5 people
Anil Vaghela Anil Vaghela
Hello Morgan Maguire, CEO Morgan ,

We reviewed your above videos and understood the scenarios you explained.

Regarding Video 2 and Video 3:
Meta fields will be created differently whenever user will select "Value Type(this will make this field available across all projects and documents.):" to "Yes" or "No" as described below: 
  • If user will create a meta field with "Value Type" as "No" then meta field will be created as a TextBox. 
  • If user will create a meta field with "Value Type" as "Yes", meta field will be created as a Dropdown field and it can have multiple type values.
Hence, instead of eliminating the field "Value Type(this will make this field available across all projects and documents.):" we can just rename it as "Value Type" and will do the first change that you described in Video 1 so that project level meta fields and document level meta fields can be separated. 

Hope you understood my above explanation. Please let me know if you need more details.
Notified 5 people
Morgan Maguire, CEO
Morgan Maguire completed this to-do.