# data[].attributes.headline
Not sure what has changed from the previous version. 

# data[].attributes.subject
Not sure what has changed from the previous version. 

# data[].attributes.headline
Happy with this though slides that reference the Scholarly Comms website might need to be changed once the new microsite is available.

# data[].attributes.subject
Happy with this though slides that reference the Scholarly Comms website might need to be changed once the new microsite is available.

# data[].attributes.headline
I'm due to do this and haven't done it for years and was a bit taken aback by how much content there is. There is a query over the Padlet exercise - could an account be created that uses similar logins to the team Mentimeter

# data[].attributes.subject
I'm due to do this and haven't done it for years and was a bit taken aback by how much content there is. There is a query over the Padlet exercise - could an account be created that uses similar logins to the team Mentimeter

# data[].attributes.headline
Like the flow.  Has nicely linked the practical and theory. From my perspective, just a few tweaks: need to change link on slide 21 to general subject guide index - currently the London guides (just a hangover from where session was first run).  Slide 36 - might want to add in a new Google dataset search (currently beta):  https://toolbox.google.com/datasetsearch  ???

# data[].attributes.subject
Like the flow.  Has nicely linked the practical and theory. From my perspective, just a few tweaks: need to change link on slide 21 to general subject guide index - currently the London guides (just a hangover from where session was first run).  Slide 36 - might want to add in a new Google dataset search (currently beta):  https://toolbox.google.com/datasetsearch  ???

# data[].attributes.headline
This interesting and a lot of work has gone into it -thank you. I can see how you are trying to deepen the content, which I understand, but I confess that I would struggle to present this as it is 'off the peg',  compared with the previous version, especially with all the different types of plagiarism referenced. Sorry for the long comment, which I don't mean to seem negative, but I thought it would help to be specific. Please could you look again at the slides 7, 8 and 9 to explain the colour coding and especially slide 9 where the notes do not seem to relate to the slide.  Slide says 'word for word plagiarism' but the notes say 'not plagiarism'.  I am confused by these slides - sorry if I am being dim!  I would also be wary of using the word 'student' in slide 6, as doctoral researchers can flinch if they think that they are being seen as undergrads - perhaps change to 'these paragraphs'?

# data[].attributes.subject
This interesting and a lot of work has gone into it -thank you. I can see how you are trying to deepen the content, which I understand, but I confess that I would struggle to present this as it is 'off the peg',  compared with the previous version, especially with all the different types of plagiarism referenced. Sorry for the long comment, which I don't mean to seem negative, but I thought it would help to be specific. Please could you look again at the slides 7, 8 and 9 to explain the colour coding and especially slide 9 where the notes do not seem to relate to the slide.  Slide says 'word for word plagiarism' but the notes say 'not plagiarism'.  I am confused by these slides - sorry if I am being dim!  I would also be wary of using the word 'student' in slide 6, as doctoral researchers can flinch if they think that they are being seen as undergrads - perhaps change to 'these paragraphs'?

# data[].attributes.body
Slide 15 - Notes don't match the text on the slide - would be great to have an example of this. Is this may be what the references on the slide relate to?
Slide 22 - Petty point but need opening quotation marks for the definition of schol comms
Slide 25 - Has the wording been checked with Naomi and Katie as IR Managers?  The act of submitting the e-thesis does not make the thesis open access; the default is to make it openly available but there can be an embargo, so they might have some wording to reflect this.    The wording as it is a bit dramatic and could worry the PGRs unnecessarily, especially if they view the slides without attending the session.
Slide 26:  petty point, but missing an 'it' in the title of the slide
Side 27:  accrediting the journal or another place of publication is not enough to cover you in plagiarism/copyright - journal usually wants to be the sole publisher of a work.  Might need to re-word slightly?
Slide 40 - Need rewording?  Don't think we offer training on Cite Them Right.
Slide 44 - Needs reformatting as copyright details look like the AL contact.

# data[].attributes.headline
Agree with comments above.  Latest thought is Research Support website will be out at the end of Sept. Thanks

# data[].attributes.subject
Agree with comments above.  Latest thought is Research Support website will be out at the end of Sept. Thanks

# data[].attributes.headline
Looks fine to me. Thanks. Just one petty point about Slide 43 - Not sure we officially call the data repository Loughborough's figshare (even though that is what it uses) - may be check this with Gareth so we are consistent?  Thanks.

# data[].attributes.subject
Looks fine to me. Thanks. Just one petty point about Slide 43 - Not sure we officially call the data repository Loughborough's figshare (even though that is what it uses) - may be check this with Gareth so we are consistent?  Thanks.

# data[].attributes.headline
Looks good. Like the new slides and examples.

# data[].attributes.subject
Looks good. Like the new slides and examples.

# data[].attributes.headline
I really liked the new Boolean operator image. The proximity slide is much clearer now. Also, very useful to include search tips for Google Scholar.

# data[].attributes.subject
I really liked the new Boolean operator image. The proximity slide is much clearer now. Also, very useful to include search tips for Google Scholar.

# data[].attributes.headline
Good spot on the London link! I've changed it now.

# data[].attributes.subject
Good spot on the London link! I've changed it now.

# data[].attributes.headline
Have added bullet point on Google dataset search

# data[].attributes.subject
Have added bullet point on Google dataset search

# data[].attributes.headline
Thank you for the feedback about Slide 43,  yes you are right.  I've updated this now.  CG 

# data[].attributes.subject
Thank you for the feedback about Slide 43,  yes you are right.  I've updated this now.  CG 

# data[].attributes.headline
I'm due to teach this session so I was pleased with the clean fresh visual appearance of the sides and selected new images. So glad you have used the Marx* example instead of Analyse.  Due to the length of this session I think the number of slides is about right.  Thanks CG 

# data[].attributes.subject
I'm due to teach this session so I was pleased with the clean fresh visual appearance of the sides and selected new images. So glad you have used the Marx* example instead of Analyse.  Due to the length of this session I think the number of slides is about right.  Thanks CG 

# data[].attributes.headline
Something that strikes me straight away.  The width of the presentation slides are wider than the format usually used and the L'Boro logo looks stretched.  Thus, the slides may not display correctly. CG 

# data[].attributes.subject
Something that strikes me straight away.  The width of the presentation slides are wider than the format usually used and the L'Boro logo looks stretched.  Thus, the slides may not display correctly. CG 

# data[].attributes.headline
Visually there is a lot of text, which is quite small, on the first few slides (3-5) and slide 21.  Perhaps use larger text over more slides or edit.  Also if the text could be made bigger on slide 30.  Perhaps a few more images  to break up the text on the slides mentioned above. CG 

# data[].attributes.subject
Visually there is a lot of text, which is quite small, on the first few slides (3-5) and slide 21.  Perhaps use larger text over more slides or edit.  Also if the text could be made bigger on slide 30.  Perhaps a few more images  to break up the text on the slides mentioned above. CG 

# data[].attributes.headline
Ditto the previous comment about needing to know what has changed. If there are wholesale changes then a note to this effect would be fine. Otherwise, it's helpful to have the changes highlighted and explained. 

# data[].attributes.subject
Ditto the previous comment about needing to know what has changed. If there are wholesale changes then a note to this effect would be fine. Otherwise, it's helpful to have the changes highlighted and explained. 

# data[].attributes.headline
Activity 1: The Mentimeter code is incorrect (I think it changes each time). I'm also not sure about the value of asking attendees to respond to two questions at once. Maybe better to split them or just ask one question? The code is also wrong for Activity 2.

# data[].attributes.subject
Activity 1: The Mentimeter code is incorrect (I think it changes each time). I'm also not sure about the value of asking attendees to respond to two questions at once. Maybe better to split them or just ask one question? The code is also wrong for Activity 2.

# data[].attributes.headline
I hadn't realised the session was being increased to 2 hours. Is there a reason for this?

# data[].attributes.subject
I hadn't realised the session was being increased to 2 hours. Is there a reason for this?

# data[].attributes.headline
I don't see anything about Turnitin and detecting plagiarism. I think this should at least be mentioned. Good that self-plagiarism has been given more emphasis.

# data[].attributes.subject
I don't see anything about Turnitin and detecting plagiarism. I think this should at least be mentioned. Good that self-plagiarism has been given more emphasis.

# data[].attributes.headline
Very happy to present this. Really like the changes. Much clearer for students and easier for presenters to follow. Minor typos on slides 9, 11, 22, 35 and 39. 

# data[].attributes.subject
Very happy to present this. Really like the changes. Much clearer for students and easier for presenters to follow. Minor typos on slides 9, 11, 22, 35 and 39. 

# data[].attributes.headline
The wording on slide 2 is a bit clumsy. Agree with previous comment about slides 3-5 and the size of the text. Could it be rewritten or just the salient points provided with more detail in the notes field? Slides 3 and 21 have variable font size. Not sure why slide 3 (What is a systematic review) from the previous presentation has been removed / replaced (though there may be a good reason for this). 

# data[].attributes.subject
The wording on slide 2 is a bit clumsy. Agree with previous comment about slides 3-5 and the size of the text. Could it be rewritten or just the salient points provided with more detail in the notes field? Slides 3 and 21 have variable font size. Not sure why slide 3 (What is a systematic review) from the previous presentation has been removed / replaced (though there may be a good reason for this). 

# data[].attributes.headline
Nicely merged. Will be happy to present this. The number of slides seems appropriate given the length of the session and the fact that it now covers both the theory and the practical. Not sure how the concepts / themes (as opposed to the keywords which lend themselves to this approach) will be tackled with the padlet activity. Will these be discussed and added in by the presenters before the attendees start adding their keywords?

# data[].attributes.subject
Nicely merged. Will be happy to present this. The number of slides seems appropriate given the length of the session and the fact that it now covers both the theory and the practical. Not sure how the concepts / themes (as opposed to the keywords which lend themselves to this approach) will be tackled with the padlet activity. Will these be discussed and added in by the presenters before the attendees start adding their keywords?

# data[].attributes.headline
Re. padlet activity- yes, have to discuss the concepts and themes before asking them to go on and add keywords. Seemed to work ok in July session. JDL

# data[].attributes.subject
Re. padlet activity- yes, have to discuss the concepts and themes before asking them to go on and add keywords. Seemed to work ok in July session. JDL

# data[].attributes.headline
Quite a few changes - a list would have been useful to work from. I agree with previous comments e.g. re. Turnitin, Cite them right, AL/Copyright blog etc.

# data[].attributes.subject
Quite a few changes - a list would have been useful to work from. I agree with previous comments e.g. re. Turnitin, Cite them right, AL/Copyright blog etc.

# data[].attributes.body
Not sure about black background creeping in, slides 7-10, 24. Also ordering of slides on reasons and consequences of plagiarism a bit mixed up.  After activity 3 on slide 17 nothing more until 27-. Should a mention be made of different referencing styles (around slide 32)? CRAAP diagram omitted - can we add it in. I find it useful (2017 master slide 42)
Also, do you explicitly cover numeric styles too? That was one of the comments made in feedback. I liked 2017 slides 37-40 but it seems like you go straight to secondary referencing.

# data[].attributes.headline
This looks fine, I like the questions and examples

# data[].attributes.subject
This looks fine, I like the questions and examples

# data[].attributes.headline
Happy with changes. May just need more slides earlier on for wording but like additional explanations. 

# data[].attributes.subject
Happy with changes. May just need more slides earlier on for wording but like additional explanations. 

# data[].attributes.body
We may need to add a slide on Nvivo!

# data[].attributes.headline
Agree with earlier comments about slides 3-5 and I think it would be good to mention Nvivo but not sure it needs a slide on it's own

# data[].attributes.subject
Agree with earlier comments about slides 3-5 and I think it would be good to mention Nvivo but not sure it needs a slide on it's own

# data[].attributes.headline
I like the flow and happy to present and train on this. On slide 37 it says 'come along to a Mendeley session' . Should this point them to the material on Learn and say we are running DRop-ins if they have problems using it?

# data[].attributes.subject
I like the flow and happy to present and train on this. On slide 37 it says 'come along to a Mendeley session' . Should this point them to the material on Learn and say we are running DRop-ins if they have problems using it?

# data[].attributes.headline
I've not delivered this before and I think the flow needs to be reviewed as it jumps around . As this is for DRs I would definitely include numeric examples and include Latex as one of the Ref Mgt tools as we know this used in STEM.

# data[].attributes.subject
I've not delivered this before and I think the flow needs to be reviewed as it jumps around . As this is for DRs I would definitely include numeric examples and include Latex as one of the Ref Mgt tools as we know this used in STEM.

# data[].attributes.headline
Good point. I will amend accordingly. JDL

# data[].attributes.subject
Good point. I will amend accordingly. JDL

# data[].attributes.headline
Typo on slide 32 : 'payed' instead of 'paid'

# data[].attributes.subject
Typo on slide 32 : 'payed' instead of 'paid'

# data[].attributes.headline
Examples are clear and realistic. i.e. likely to be faced by the DRs. They should generate some discussion. 

# data[].attributes.subject
Examples are clear and realistic. i.e. likely to be faced by the DRs. They should generate some discussion. 

# data[].attributes.headline
Good comprehensive overview that feeds into other workshops. (NR)

# data[].attributes.subject
Good comprehensive overview that feeds into other workshops. (NR)