# data[].attributes.headline
Is the forum principally for people who haven't been to a 1-1 / who can't make a 1-1??

# data[].attributes.subject
Is the forum principally for people who haven't been to a 1-1 / who can't make a 1-1??

# data[].attributes.body
It sounds like it will be good..  I like the collaborative feel

# data[].attributes.body
Good, as long as the forum is actually easy to locate (perhaps even on the main library page) rather than just somewhere in the libguides and Keats.

# data[].attributes.headline
Getting feedback from peers in answering in-depth stuff will be really useful :)

# data[].attributes.subject
Getting feedback from peers in answering in-depth stuff will be really useful :)

# data[].attributes.body
Related to tying up all our methods of communication in one spot, currently when people book sessions, they go into the guide for that area, then to the area to book support, which suggests the person they book is specific to their area. Maybe a separate contact link on the front page of Libguides would be good to show it's a more generic resource as well as having all the various ways listed, some of which aren't particularly intuitive to get to.

# data[].attributes.headline
Will we follow word limits in our replies to enquiries within the forum (the staff guidance on creating and using forums seems to suggest we should)?

# data[].attributes.subject
Will we follow word limits in our replies to enquiries within the forum (the staff guidance on creating and using forums seems to suggest we should)?

# data[].attributes.headline
Are there any restrictions as to how many new questions a student can ask us via the forum per week/month/term?

# data[].attributes.subject
Are there any restrictions as to how many new questions a student can ask us via the forum per week/month/term?

# data[].attributes.headline
I think it's really great, as long as it's made clear to students that forums are for in-depth enquiries and QP not, in order to avoid unnecessary delays and/or confusion.

# data[].attributes.subject
I think it's really great, as long as it's made clear to students that forums are for in-depth enquiries and QP not, in order to avoid unnecessary delays and/or confusion.

# data[].attributes.body
Find the guidance document below in our Sharepoint space. Give it a 10 minute review. Does anything need adding or changing?

# data[].attributes.headline
it could end up being a discussion between SLAs and the enquirer gets left behind in the noise....

# data[].attributes.subject
it could end up being a discussion between SLAs and the enquirer gets left behind in the noise....

# data[].attributes.body
Have to take screenshot, save, go to forum, insert --> picture --> upload --> *navigate to saved screengrab* --> upload --> add descriptive text...….

Any way to allow copy n paste into forum of pics?

# data[].attributes.headline
For the skype one below, it would give away our full names and personal email addresses - some sort of group skype email? like library@kcl.ac.uk

# data[].attributes.subject
For the skype one below, it would give away our full names and personal email addresses - some sort of group skype email? like library@kcl.ac.uk

# data[].attributes.headline
Is it possible to some day have Skype chat instead of QP? 

# data[].attributes.subject
Is it possible to some day have Skype chat instead of QP? 

# data[].attributes.headline
How do we tie up all of these ways to get in touch? 

# data[].attributes.subject
How do we tie up all of these ways to get in touch? 

# data[].attributes.body
Separate entrypoints for 121s, drop ins, QP, emails, KLaSS module, book training courses, studyskills leaders, KASL

# data[].attributes.headline
is this going to be another timed task like QP sessions in our calendar?

# data[].attributes.subject
is this going to be another timed task like QP sessions in our calendar?

# data[].attributes.headline
one of the things SMT noted was we had over  ways for students to contact us - isn't this just adding yet another way for them to contact us without really getting rid of the other avenues to reach us?

# data[].attributes.subject
one of the things SMT noted was we had over  ways for students to contact us - isn't this just adding yet another way for them to contact us without really getting rid of the other avenues to reach us?

# data[].attributes.headline
Useful for certain kinds of questions but can be more difficult to distribute workload fairly compared with QP. 

# data[].attributes.subject
Useful for certain kinds of questions but can be more difficult to distribute workload fairly compared with QP. 

# data[].attributes.body
You know when someone types something
And then someone replies
And then the next reply is                  further to the right
And then the whole                               answer ends up as a                  very short line

Limitation of KEATs?

# data[].attributes.headline
It is a good way to answer questions and at the same time share our knowledge with colleagues. We can learn a lot from our colleagues' answers.

# data[].attributes.subject
It is a good way to answer questions and at the same time share our knowledge with colleagues. We can learn a lot from our colleagues' answers.

# data[].attributes.body
Allow editing time beyond 30 mins

# data[].attributes.body
Navigating how to correct wrong information provided by colleagues. Possibly by contacting colleague directly and allowing them to edit/correct their original post.

# data[].attributes.body
Use of repetitive language could become jarring/noticeable. e.g. "my colleague X..." in every response.

# data[].attributes.headline
a good way of engaging with and assisting students. SLAs will learn a lot too. A bit daunting. 

# data[].attributes.subject
a good way of engaging with and assisting students. SLAs will learn a lot too. A bit daunting. 

# data[].attributes.body
KEATS forums feel quite clunky to use