Date

30 Sep 2016

Attendees

Item	Who	Notes

FAQs and user labs	Scott	Some of the FAQs might need to point to the user labs area, need to communicate with them to let them know about cross over.
Where to draw the line with out of scope questions?	Scott	Where should we draw the line on giving answers for issues that aren't directly related to using ASpace (like the Windows documentation question or the Excel csv question)? Our decision: if it's out of scope but definitely an FAQ, and is easy to answer (or point people in the right direction) we can do that case by case.
Linking to members only content	Scott	How should we handle questions where part of the answer is drawn from the listerv or other openly accessible sources and parts are best answered by linking to members-only documentation that not all users on the open FAQ will have access to? Our decision: probably okay to go ahead and link to the protected documentation even though not having access to the answers might (will probably) be annoying to some users who aren't members.
Separate spreadsheets for feedback	Ann	We'll think about whether this might be a workable / good idea as we finish up answering questions and putting in the text for the answers: creating a seperate spreadsheet for each sub-team with the questions we're asking for their feedback on so we can send them a link and they won't have to sort through the entire sheet to find the places where their sub-team is mentioned.

Scott Hanrath (Unlicensed) will start looking into platform possibilities
All will continue to work through answering unanswered questions
All will work on typing up the answers in the spreadsheet (and keeping the links in)
All will think of sub-teams to ask for feedback on certain questions (record in the column Rachel created for this in the spreadsheet)