JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for RECORDS-MANAGEMENT-UK Archives


RECORDS-MANAGEMENT-UK Archives

RECORDS-MANAGEMENT-UK Archives


RECORDS-MANAGEMENT-UK@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

RECORDS-MANAGEMENT-UK Home

RECORDS-MANAGEMENT-UK Home

RECORDS-MANAGEMENT-UK  August 2020

RECORDS-MANAGEMENT-UK August 2020

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Retention of chat messages in Teams

From:

Nicki Hargreaves <[log in to unmask]>

Reply-To:

Nicki Hargreaves <[log in to unmask]>

Date:

Tue, 4 Aug 2020 16:17:19 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Yes, agreed! 



I do have concerns on the SAR/FOI side and also that once we've agreed and implemented 12 months it will be incredibly difficult to reduce it if we later think it is necessary. But I am starting to see that there are very different use cases in place for professional services areas and the teaching side, which I perhaps hadn't considered in enough detail previously.



We've had to find a balance somewhere, and hopefully this will work for everyone. 





Nicki



Nicki Hargreaves

Information Records Manager











-----Original Message-----

From: The Information and Records Management Society mailing list <[log in to unmask]> On Behalf Of Zoe Cooper

Sent: 04 August 2020 17:00

To: [log in to unmask]

Subject: Re: Retention of chat messages in Teams



Hi all, 



I'm seeing that it's hard for Universities to find a balance here as they need to service academics and students as well as professional service staff. The 3 days that Fife has wouldn't be right for us. 



It's interesting to hear about the feedback you had on the 90 days Nicki, as that's one of the options I put forward. I know academics are finding Chat a really useful platform for providing one-to-one teaching support and it is reasonable that they would want to refer back to ongoing chats over the year. 



I would be concerned about the amount that might come back for requests. But from a Retention Schedule perspective it would work as we state 1 year maximum for general requests or enquiries.  



Best wishes all,

Zoe



Zoe April Cooper

Corporate Records Manager

Legal and Governance 

University of Central Lancashire











-----Original Message-----

From: The Information and Records Management Society mailing list <[log in to unmask]> On Behalf Of Donald Henderson - CHX

Sent: 04 August 2020 15:49

To: [log in to unmask]

Subject: Re: Retention of chat messages in Teams



12 months feels very long - FOI requests and SARs could be problematic...



-----Original Message-----

From: The Information and Records Management Society mailing list <[log in to unmask]> On Behalf Of Nicki Hargreaves

Sent: 04 August 2020 13:05

To: [log in to unmask]

Subject: Re: Retention of chat messages in Teams



Hi all,



This is an interesting thread, and a discussion we’ve been having at MMU recently, as we’re also implementing Teams at the moment and facing a lot of similar questions.



In terms of chat retention, we initially proposed a 90 day retention rule on chat messages, with all the guidance around it being intended for informal discussions and nothing with a long term value. Similar to what both you and Zoe have said – that if it needs to be retained, it should be elsewhere. The 90 days was based on guidance I’ve read on this list and knowledge of what other sectors are doing, but at the time I wasn’t aware of what any other Universities had done.



Once the message got to academics however there was reluctance to accept that 90 days was enough, based on their belief of how students will use chat.



So, following a number of meetings/discussions around it all, we’ve increased the chat retention period to 12 months – still with the exact same usage guidance. I’ve also been emphasising the functionality in chat: for example sharing documents or adding them onto their own tab and using that as decision logs or similar to record key decisions being made, as well as use of the ‘meeting notes’ tab in a meeting (we also had push back because chats in meetings are treated the same as other chats and people might want to refer back, especially for recurring meetings). Any files or meeting notes managed in this way are saved in OneDrive so unaffected by the deletion policy.



We accepted the view from academics, however that 12 months fits with the new block teaching models, and will be enough for them to support students doing dissertations.



We’re not implementing Teams as a replacement for anything else, so I’m trying to stress that just because we may now be able to record every single interaction everyone has doesn’t mean that we should – because the more we have, the less value it has and we should concentrate on ensuring that the important stuff is properly managed. It’s a behavioural question as much as anything, but I want people to treat chat as unstructured and unmanaged and more of an instant comms tool that nobody will need again. If a record was ever made of a face to face meeting/phone call then this should still happen if it takes place in Teams chat, but if that record was never needed before, why would we keep it now?



I’d thought about whether having more than one chat retention policy would work best as a sort of Capstone like approach – so perhaps for the more senior staff only, but we’ve not gone for that, we’ve implemented a blanket 12 months for all users. At the moment we’re in the fortunate position of not having many users on Teams yet, so we’re focusing on getting everyone using it in the right way.



I was initially very reluctant to accept that the 90 days needed to be increased, because it seemed to be very much a ‘just in case’ request based purely on speculation that people might use chat differently to how we’re saying they should, and I don’t think that’s enough. It was academics who proposed 12 months and gave the block teaching and dissertation support examples and I think those are justified, and at least this way we have got the support of the academics too so it is hopefully more likely to be successful.



I’d also be very happy to hear about the approach that others have taken and how it has been received.



Thanks,



Nicki



Nicki Hargreaves

Information Records Manager | Manchester Metropolitan University







-----Original Message-----

From: The Information and Records Management Society mailing list <[log in to unmask]> On Behalf Of Meic Pierce Owen

Sent: 03 August 2020 13:35

To: [log in to unmask]

Subject: Re: Retention of chat messages in Teams



Hi Zoe and Sian



Fife Council has 9000+ users on its M365.



We operate a 3 day retention on chat in teams.  This is draconian and we understand it as such. Its purpose is to restrict the Info requests risk and resource exposure.  It is explained to staff that they need to capture any key decisions- screenshot, copy/paste, confirming email.



I understand that mbe 'next midnight' deletion is now possible?  If so, we will go for that and replicate SFB deletion- which we have been very comfortable with. Mbe Rob or Andrew or similar could advise on this?



Channels chat is different.  This can be valuable so where we have that, we are looking at 2 years' retention. In looking at Pilot Project use of this, it does seem to be strongly business focussed so we are more relaxed about this.



Hope this assists



Meic



Meic Pierce Owen FIRMS FIIMA AMIRMS

Fife Council Records Manager



-----Original Message-----

From: The Information and Records Management Society mailing list <[log in to unmask]> On Behalf Of Zoe Cooper

Sent: 03 August 2020 13:23

To: [log in to unmask]

Subject: Re: Retention of chat messages in Teams



CAUTION: This email originated from outside of the organisation. Do not click links or open attachments unless you recognise the sender and know the content is safe.

________________________________



Hi Sian,



I don't have any great advice but wanted to comment as we're having the same discussion at UCLan. We want a short retention on the majority of chats but there are conversations which record key decisions and one-to-one student support, which could be lost too soon.



We're considering implementing a 6 month rule and raising awareness that chat is an informal platform and any exchange which needs to be retained longer should be recorded elsewhere, as we might have done following a phone call or in-person conversation. I realise this isn’t ideal.



I'm interested to hear the responses to your question.



Zoe



Zoe April Cooper

Corporate Records Manager

University of Central Lancashire



-----Original Message-----

From: The Information and Records Management Society mailing list <[log in to unmask]> On Behalf Of Sian Astill

Sent: 02 August 2020 15:37

To: [log in to unmask]

Subject: Retention of chat messages in Teams



Hello all



We have recently introduced Teams at the University of Huddersfield and have hit a potential snag relating to chat retention policies. I’ll give some background below, but my questions in short are:



1) Has anyone implemented more than one chat retention policy (or one policy applicable to one group only, with remaining users having no policy)? Could you possibly tell me about your approach?

2) For universities, how long would you keep interactions between staff and students in Teams chat?

3) Any other advice on the issues raised below will be much appreciated!



We were intending to implement a retention policy of something like 6 months on chat messages for staff in Teams (not channel messages), with guidance given that chat is for informal conversations only and anything important that is said there should be moved to a more appropriate location within the 6 months. This was prompted by concerns about the chat messages otherwise being retained forever, which, in addition to just getting unwieldy, has implications for things such as Subject Access Requests.



However, we’re a university and our students will soon be getting access to Teams. As well as students chatting to other students, they would also be able to interact with staff. Andrew Warland very kindly tested for me what would happen when a retention policy is applied to one person in a chat conversation (ie if we apply a short chat retention policy to staff, but not students). Alas, what happens is that the chat messages are removed for both sides of the conversation – that is, neither staff nor student can see either the messages they sent or the messages they received.



Therefore, in order to retain interactions between staff and students for longer, we couldn’t apply the short chat retention policy to any members of staff who interact with students. But, because chat retention policies are based on the user and not the purpose, this would mean that all their informal chats with other staff were also retained for that extended retention period.



On a related note, we are also uncertain about how long to retain interactions between students and staff in Teams chat in any case. The intention would be that Teams chat messages were only used for informal discussions and formative feedback (as might have occurred in person), but with the whole idea of using Teams for teaching being so new, it is very difficult to be certain about what staff and students may find useful and what practices they might want to adopt. Would we therefore need to retain staff/student chats for completion of student’s programme + 6 years? We would really appreciate information on what other universities may have chosen to do.



My feeling is that retention policies based on the user are less than ideal. Retention policies should be based on the purpose/content of the messages, not who sent/received them. However, I’m not sure how that would ever be possible without the user have to select the retention policy themselves for each chat, much like applying a retention label. I wonder if the limited options for chat retention is something that could be raised with Microsoft as part of the roundtable discussions that have happened/are planned, but I’m not sure what the solution would be.



Please reply either on- of off-list; to email me directly, use s.astill at hud.ac.uk.



Thank you very much



Sian



Sian Astill

Assistant Records Manager and Archivist

University of Huddersfield



To view the list archives go to: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.jiscmail.ac.uk%2Fcgi-bin%2Fwebadmin%3FA0%3DRECORDS-MANAGEMENT-UK&amp;data=02%7C01%7CMeic.PierceOwen%40fife.gov.uk%7C5ec6965443784bcd7e9008d837a82200%7Cf969a52f42c040f198badaed6c43087c%7C0%7C1%7C637320542548822260&amp;sdata=NfNeN%2FCKel1NS%2BJhKYeTCtyDYIrrt35BQurMOOEm1uA%3D&amp;reserved=0

To unsubscribe from this list, send an email to [log in to unmask] with the words UNSUBSCRIBE RECORDS-MANAGEMENT-UK



For any technical queries re JISC please email [log in to unmask] For any content based queries, please email [log in to unmask]

[University of Central Lancashire]

Please consider the environment before printing



To view the list archives go to: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.jiscmail.ac.uk%2Fcgi-bin%2Fwebadmin%3FA0%3DRECORDS-MANAGEMENT-UK&amp;data=02%7C01%7CMeic.PierceOwen%40fife.gov.uk%7C5ec6965443784bcd7e9008d837a82200%7Cf969a52f42c040f198badaed6c43087c%7C0%7C1%7C637320542548822260&amp;sdata=NfNeN%2FCKel1NS%2BJhKYeTCtyDYIrrt35BQurMOOEm1uA%3D&amp;reserved=0

To unsubscribe from this list, send an email to [log in to unmask] with the words UNSUBSCRIBE RECORDS-MANAGEMENT-UK



For any technical queries re JISC please email [log in to unmask] For any content based queries, please email [log in to unmask]

[Please remember to wash your hands.]<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.nhsinform.scot%2Fcoronavirus&amp;data=02%7C01%7CMeic.PierceOwen%40fife.gov.uk%7C5ec6965443784bcd7e9008d837a82200%7Cf969a52f42c040f198badaed6c43087c%7C0%7C0%7C637320542548822260&amp;sdata=R72Wf19YztLfudCJEct%2FzcwG31fhftlsVI1dtzqeZfI%3D&amp;reserved=0>

[Please remember to wash your hands.]<https://www.nhsinform.scot/coronavirus>



**********************************************************************

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed and should not be disclosed to any other party.

If you have received this email in error please notify your system manager and the sender of this message.



This email message has been swept for the presence of computer viruses but no guarantee is given that this e-mail message and any attachments are free from viruses.



Fife Council reserves the right to monitor the content of all incoming and outgoing email.



Information on how we use and look after your personal data can be found within the Council’s privacy notice: www.fife.gov.uk/privacy





Fife Council

************************************************





To view the list archives go to: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=RECORDS-MANAGEMENT-UK

To unsubscribe from this list, send an email to [log in to unmask] with the words UNSUBSCRIBE RECORDS-MANAGEMENT-UK



For any technical queries re JISC please email [log in to unmask] For any content based queries, please email [log in to unmask]

"Before acting on this email or opening any attachments you should read the Manchester Metropolitan University email disclaimer available on its website http://www.mmu.ac.uk/emaildisclaimer "



To view the list archives go to: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=RECORDS-MANAGEMENT-UK

To unsubscribe from this list, send an email to [log in to unmask] with the words UNSUBSCRIBE RECORDS-MANAGEMENT-UK



For any technical queries re JISC please email [log in to unmask] For any content based queries, please email [log in to unmask]



The information in this email is solely for the intended recipients. 



If you are not an intended recipient, you must not disclose, copy, or distribute its contents or use them in any way: please advise the sender immediately and delete this email. 



Perth & Kinross Council does not warrant that this email or any attachments are virus-free and does not accept any liability for any loss or damage resulting from any virus infection. Perth & Kinross Council may monitor or examine any emails received by its email system. 



The information contained in this email may not be the views of Perth & Kinross Council. It is possible for email to be falsified and the sender cannot be held responsible for the integrity of the information contained in it. 



General enquiries to Perth & Kinross Council should be made to [log in to unmask] or 01738 475000. 





To view the list archives go to: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=RECORDS-MANAGEMENT-UK

To unsubscribe from this list, send an email to [log in to unmask] with the words UNSUBSCRIBE RECORDS-MANAGEMENT-UK



For any technical queries re JISC please email [log in to unmask] For any content based queries, please email [log in to unmask]



To view the list archives go to: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=RECORDS-MANAGEMENT-UK

To unsubscribe from this list, send an email to [log in to unmask] with the words UNSUBSCRIBE RECORDS-MANAGEMENT-UK



For any technical queries re JISC please email [log in to unmask]

For any content based queries, please email [log in to unmask]



To view the list archives go to: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=RECORDS-MANAGEMENT-UK

To unsubscribe from this list, send an email to [log in to unmask] with the words UNSUBSCRIBE RECORDS-MANAGEMENT-UK



For any technical queries re JISC please email [log in to unmask]

For any content based queries, please email [log in to unmask]

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager