initial designs for keywords instead of PoAMs on report/new, report/show, exsum view, and summary view

[erincd]

We were giving one member of the SFAC a demo yesterday to get his feedback, and he had a couple of really great ideas. The SFAC currently has to deal with a few issues related to surfacing useful information from the reports. Many reports that are entered are low content, especially when an advisor meets with their advisee for coffee and relationship building, where there may not have been specific outcomes.

He suggests the use of keywords to indicate whether or not the engagement was routine i.e. no interesting information for the rest of the mission, just relationship building. We were thinking that perhaps a toggle to indicate routine is a better fit, and it can collapse some fields and filter the report out of the daily rollup.

He also suggested flagging the reports with keywords (basically the way that labels work in email or github or whatever) so that users can flag critical topics, like corruption, security issues, etc. and people can filter on those when reading the daily rollups, or filter on them for their subscribed searches.

My favorite part of the idea was that he suggested that we just tie the keywords to PoAMs on the backend, so that the users only have to pick topics that are actually contained in the report. that way people can focus on surfacing critical information, and the mission command can still access reports filtered by PoAMs as needed.

I also think that this idea will help approvers understand what they actually need to look for when approving reports. Since they typically have no sense whether the content of a report is right or wrong, they just check spelling and grammar. However, if there are labels w/ keywords on the report, they know that they should make sure each of those topics is clearly contained within the report.

So let's start working on some preliminary designs.

[efo-usds]

@erincd I can do this today, are we still interested in chasing this down?

I'm thinking that we'd simplify the interface by asking them: "Was this a routine, and non-important, meeting?" If they answer yes, then nothing else is asked, if they answer no, then they're presented with a series of check-box arrays with keywords for them to select from (e.g. corruption, elections, water, etc) -- this list of keywords should be tied to PoAMs - understanding that there will be overlap between them. One idea to run down may be specific keywords based on EF, so only display keywords that match PoAMs that are associated with EF 1.

[erincd]

I'd still like to prep this so that we can at least get some user feedback before leaving so NATO knows they want. I'm not sure that I like the checkbox rather than a keyword search, but I trust your judgement, so feel free to whip it up and we'll get feedback

[erincd]

@efo-usds just a heads up that we leave on thursday so if you can have this done by tuesday night your time that would be ideal

[efo-usds]

@erincd after going back and forth several times, I settled on reusing patterns that had already been established. Below is the direction that we should display:

Let me know what you think, assign it back to me if you have feedback.

[erincd]

Thanks eduardo I think this will be great to pass on. If you have time -- it's okay if you don't -- if we could see what the summary view of the report would look like with this implemented. here's what it looks like now:

[efo-usds]

@erincd tried with a stacking list, and columns, and the comma-separated list is the best possible display given that we don't know what length topics may be, also allows for a sentence-like structure to the display. (ignore the chart area)

[erincd]

Accidentally clicked the wrong button. The chart totally threw me off for a sec, but now I see! Thanks Eduardo!!

[efo-usds]

@erincd yah -- same display, comma-separated :)