TOLOGIX - Infrastructure LawGuide (ILG)

Changes to tagging process

Hi Melissa Cowell, General Manager at Industrial Melissa and Guillaume Morin-Simard, UX Designer/Researcher at Industrial Guillaume ,

As we discussed, below is the document providing an overview of the tagging template that will be used for the subject-matter analysis trial. Please give this a use review and let me know if you have any questions.

A few notes:
  • columns under the Risk section are the descriptive elements of the tags. 
    • Topic is the group where the tag exists
    • Title is the title of the tag
    • Description is the description of the tag that should be available to the user when they are searching and potentially assigning the tag to a section of text.
  • columns under Risk Allocation are examples of meta fields that could be assigned to tags; however, we should create an ability to manage what meta fields are associated with tags and be customized by the admin user as they are creating/editing tags in the tag directory.
  • Relevant Documents and Clause are examples what sections and documents would be assigned the tag.
  • Comments provide further detail on the tags relevant to the project being used for the trial, but don't need to be considered for the proposed design changes beyond the comment fields available when assigning tags to the documents.
Also, please take an overall look at the current tagging process, and assess whether further refinements could me made to the design to make identifying and assigning tags more intuitive to admin users.

Thanks,

Morgan 

Comments & Events

Guillaume Morin-Simard, UX Designer/Researcher at Industrial
Hi Morgan Maguire, CEO Morgan ,

As discussed during our call earlier, here are a few questions. More might be coming your way as we progress into this feature.
  • Can a user apply more than one tag to the exact same excerpt?
  • If it's the case, should they be able to add comments per tag applied?
  • Can a user tag an excerpt within an already tagged longer excerpt?
  • Is it useful for a user to see meta associated to a tag (ex.: risk allocation to public/private parties) in the dialogue box as they are tagging an excerpt, or should this only be visible from inside the tag tree?
  • Should a user be able to filter down the list of available tags according to said meta in the dialogue box?
Thanks,

Guillaume
Morgan Maguire, CEO
Hi Guillaume Morin-Simard, UX Designer/Researcher at Industrial Guillaume ​,

Here are my responses:

  • Can a user apply more than one tag to the exact same excerpt? - Yes, multiple tags can be applied to the same excerpt, and I believe the current tagging tools has that capability.
  • If it's the case, should they be able to add comments per tag applied? - No, unless it makes more sense from a design perspective, the same comment can apply to the same exceprt.
  • Can a user tag an excerpt within an already tagged longer excerpt? - Yes, the current tagging tool allows for overlapping excepts (if that's what you're asking).
  • Is it useful for a user to see meta associated to a tag (ex.: risk allocation to public/private parties) in the dialogue box as they are tagging an excerpt, or should this only be visible from inside the tag tree? - Yes, it's essential, because the admin user needs to select what  meta data options are assigned to the tag. For example, when the admin user is tagging an excerpt and selecting a tag topic, the admin user would also need to select whether the tag is allocating the risk to the private or public party or both).
  • Should a user be able to filter down the list of available tags according to said meta in the dialogue box? - I don't think so. The meta data is specific to each tag, and filtering should only occur on the front-end after a tag is selected. For example, a front-end user may select "environmental contamination" from the topic list, and this brings up all the documents and excepts tagged with "environmental contamination". Then as a further step the front-end user should be presented with the different meta data options assigned to each excerpt (allocated to private parties and allocated to public parties). The default would be to display all options, and then through checkboxes, the user could deselect options to limit the results to "allocated to private parties".

We might need a call to clarify this. 
Guillaume Morin-Simard, UX Designer/Researcher at Industrial
Morgan Maguire, CEO Morgan , would that mean that any one tag can have different meta values according to context?

Using the example above, the following would be true: I can tag excerpt A with "environmental contamination" and assign it a value of "Yes" for "Risk allocated to private parties", then I can tag excerpt B with the same tag but allocate the risk to public parties instead.
Guillaume Morin-Simard, UX Designer/Researcher at Industrial
Further to the above question, right now the 2 examples of meta fields for tags have a yes/no behaviour.

Do you think you'll ever have tag meta fields using a different type of behaviour? I'm thinking multiple choice, for example.

This would have an impact on meta field management, as we'd have to plan meta field types and, in some cases, possible values.
Morgan Maguire, CEO
Hi Guillaume Morin-Simard, UX Designer/Researcher at Industrial Guillaume

Yes, when each tag is created, the admin user would have the ability to determine what meta values are assigned to it. In the case of "environmental contamination", they would be able to assigned "allocated to private parties" and "allocated to public parties". 

Yes, you may have meta fields with yes/no behaviour, and I'm thinking that we'll need to create meta field management page similar to what we've designed for the new ISLG.

Also, a broader issue to consider is removing the distinction between topic groups and tags. Currently, a tag is create separately from a group, and excerpts can only be assigned tags. However, I've never understood why we separated the too. Instead we could treat all groups as tags (similar to the Master Tree for the Subject Navigator), and that way excerpts could be assigned groups or sub-groups depending on the context. Make sense?

Morgan
Guillaume Morin-Simard, UX Designer/Researcher at Industrial
Hi Morgan Maguire, CEO Morgan ,

I'll dive deeper into ISLG's meta field management and replicate it for ILG where applicable.

Regarding groups vs. tags, I completely agree. We should get rid of groups and only have tags that can be nested as needed to create a tag structure.

Guillaume
Morgan Maguire, CEO
Perfect. Thanks Guillaume Morin-Simard, UX Designer/Researcher at Industrial Guillaume .

Let me know if you have any other questions.

Morgan 
Guillaume Morin-Simard, UX Designer/Researcher at Industrial
Hi Morgan Maguire, CEO Morgan ,

We've made significant progress regarding the tagging process. We can discuss it at a high level during tomorrow's call, but I'd like to walk you through a few prototype screens to get your impressions before diving into user stories about the matter.

Would you be available sometime tomorrow, maybe after our status call?

Guillaume
Morgan Maguire, CEO
Hi Guillaume,

Sorry for the delayed reply. I’m in transit from Boston to Vancouver. I have an appointment after our call tomorrow, but I’m available anytime after 11:30am PDT.

Also, I’m cc’ing Stephen and Mel on the email (sent to Basecamp via email). Would it be possible to get them on the call as well. I would like to discuss something related to my meeting in Boston.

Thanks,

Morgan
Guillaume Morin-Simard, UX Designer/Researcher at Industrial
Hi Morgan Maguire, CEO Morgan ,

Quick question about default meta field value for tags: should the default value for any one meta field be set when creating that field (global default value, regardless of tag) or should it be set when making that meta field 'available' for a specific tag (default value changes according to tag)?

Thanks,

Guillaume
Morgan Maguire, CEO
Hi Guillaume Morin-Simard, UX Designer/Researcher at Industrial Guillaume ,

Could it be both? The default value is initially set at the meta field level in the meta field management page, and then the admin user can modify the default value to customize it the assigned tag.

Morgan