Tagging Process + Tag Directory + Meta-Fields
Hi
Morgan
I wanted to give you a quick update of where everything stands. Wiring out the tagging process has taken quite some time, especially with regards to meta-field management, which leaves me lagging a bit behind.
The good news is I'm confident we have all the screens and interactions we need regarding the 3 topics above fleshed out in interactive prototypes, as you'll see below:
Morgan
I wanted to give you a quick update of where everything stands. Wiring out the tagging process has taken quite some time, especially with regards to meta-field management, which leaves me lagging a bit behind.
The good news is I'm confident we have all the screens and interactions we need regarding the 3 topics above fleshed out in interactive prototypes, as you'll see below:
- Document Tagging: https://invis.io/DYRNCUDZ5MA#/364616568_Tagging_SCREEN_Document_Default
- Tag Directory Management: https://invis.io/DYRNCUDZ5MA#/369941182_TagDirectory_SCREEN_Directory_Manage
- Meta-Field Management: https://invis.io/DYRNCUDZ5MA#/370946261_MetaFields_SCREEN_Fields
You can go ahead and click away at these, but I suggest we set something up tomorrow (Friday, June 28) so I can walk you through all of this.
In the meantime, I am diving into writing user stories for those 3 features. This will likely require a few additional days to be completed. I'll prioritize what's needed for development to start, most likely the Tag Directory itself, as it's required to address Document Tagging. Meta-Field Management will come last.
To accelerate the entire process, I'm likely to send cards your way before I've written acceptance criteria for entire features, as opposed to how we've done it before.
Guillaume
A call tomorrow sounds good to me. How about 10am Vancouver time?
Morgan
The wireframes look really good. Look forward to going through them in more detail tomorrow.
Morgan
Great! I'll make arrangements for a call.
Guillaume
Ahead of our upcoming ISLG Reporting call, I just want to throw this one by you regarding ILG Meta-Fields, so we can take just a few minutes to discuss this if time allows.
I've planned and wired meta-field management to work in a similar fashion on ILG as on ISLG, with the exception that a user has to to stick to Project, Document and Tag Meta-Fields. This means we have everything, including dependent fields, field sets, ability to mark as changed, ability to add another, etc.
I'm thinking now that it makes sense for Project and Document Meta-Fields, but it might be too much for Tag Meta-Fields, since Tags are, in a way, meta-fields themselves.
I'm just trying to figure out if we really need to track, for example, that 'Risk allocated to public party(ies)' was first set to Yes, then No, then Yes again on a 'Right to terminate for convenience' tag applied to a specific excerpt inside a document.
Depending on how we address this, I may add simplified wires for Tag Meta-Field Management only, removing superfluous options when creating fields and maybe even field sets.
Guillaume
Maybe show me during the call to illustrate what you mean, but I agree that the tag meta fields will be far more simplified than the Project and Document meta fields, and probably do not need the same level of functionality.
Morgan