+46
Planned
Andreas 2 years ago in Admin • updated by Pat 3 months ago 21

I think a feature for exporting all your data would make new users feel more comfortable committing to a product such as this so that they know they will not get completely locked in. It could also be useful if you want to be able to analyses your data for example to see how Ryver is being used.

+1, also related to some of the admin options in other suggestions... I'd vote for a full audit mode where everything can be downloaded including 1-to-1 chats private and public channels... Will help compliance requirements down the line

This looks like it's been in the works *planned* for 10 months. Any updates on when we might see this implemented; it's a pretty critical missing feature for compliance and archival purposes.

+1 this is something critical to our team as well - gives peace of mind and is a feature offered by competitors

+1 We just lost all of our conversations in the Unison chat application that abruptly closed it's doors. Before fully committing to a service like this we need to know that we can keep our conversations should we choose to move away or if Ryver decides it no longer wants to support this application.

+1 this feature is critical for widespread acceptance.

+1 We're now leaving Ryver, before is too late.

+1 This is needed for compliance. Many organisations need to keep records for long periods of time.

Any word on if/when this is being implemented. The choice for our non-profit was between this and Slack (obviously Ryver is free so that was awesome), but we absolutely need the ability to export data. Not having this is a huge compliance/auditing issue.

+1 while evaluating Ryver now. It would certainly give us peace of mind.

I'm now having an issue with a customer, hopefully the Ryver feed will prove him wrong. Thanks to this working feed, I have hope to be paid for half year of work if a court looks at my case. But if the data of the feed would disapear, I would loose all hope to not to be stolen. Exports can be delayed, limited to once a week or a month to reduce DB loads. Whatever text format is always ok.

+4

Someone just pointed me to this thread. I'm CEO/Founder of Ryver. When we did Slack import over a year ago we almost did the export then as well. But we deemed other things as more important. We saw the export as something that would indeed give people comfort that they could go back if need be. Reading these comments makes me realize we probably underestimated the benefit.


Does the fact that only public channel info could be exported to Slack make this less appealing? For obvious reasons private channel and DM info cannot be imported or exported into Slack or other.


Also, there seems to be 2 use cases talked about here. 1. Export for comfort reasons. 2. Export for compliance purposes. Am I reading that right?


Thanks much for your input.

Both, public and private are required to meet my organisational compliance needs (a research university with projects which manage and process sensitive data - often we have specific ethics committee requirements as well). This is just like organisation email. From a project perspective it is also very useful to archive with the project at it's conclusion.


Why not make it a configuration (none, public, all) option chosen by the account owner, and then for users who sign up, or when the policy changes, inform the them of this by email and a nag banner notification (latter must be acknowledged to get rid of the banner).


Export data should be machine process-able and filterable and (e.g. JSON). I guess you can skip the binary attachments (images) and just put in a reference to the fact it existed, and the metadata associated with the upload.


Thanks!

Also, there seems to be 2 use cases talked about here. 1. Export for comfort reasons. 2. Export for compliance purposes. Am I reading that right?

Almost yes, but I'd like to spot out some points: 1) private on site archiving of old, closed rooms 2) chance to offer customers the room log during project development in a standard format

We've gotten some good feedback here. Thank you! This is a tricky area given the potential security and privacy concerns once data has been exported. Our original thought was that only content from Open Forums would be exportable in the free service, with Compliance Audit Exports coming in a premium service later in 2017.


We are looking at what implications there might be if we also include a Private Team export option in the free service. Perhaps as Richard mentioned, with an option that is turned on by the Admin, and then notice is given to all of the users.

Actually this is quite blocking for me; I'd be delighted to pay for a premium version, but it still lacks. And I have to assure my customers and my organisation to have conversations at their disposal.


I'm glad you are looking into this, because your product is really attractive, but in order to be used on a work place it should grant some bureaucratic requirements :)


Cheers

+1 - for full compliance, HR, legal and ethics. we need full details for conversations not being to have an export format (irrespective of migration) that can be used for data mining / search / analysis is a problem. even if it doesn't go directly into another solution, this is needed for business reasons outside of the primary communications functionality.


+1:

The way I think exports should be: Every user should be able to export any content he has access to.

Why? Because he already has access to this messages, so nothing prevents him/her from screen printing all that information os simply copy-pasting it. Access control should not be an exporting issue, it should be handled way before.

Notes: a configuration option could be added to select who can export in the admin menu, all users, all but guests or only admins, but if given the right to export, that user should be able to export all the messages/images/files he can access normally.


About the format: exporting in JSON seems to be the most logical codification option. Creating a file for every day as Slack does may not be necessary, but there needs to be some kind of fragmentation that prevents huge files. Maybe a certain number of messages per file. Posts should probably be contained in separate files with the same fragmentation criteria. Using users id and generating a users.json at the root level with ONLY the relevant information (name, image-path) of JUST the relevant users may also be a good idea. Images (also avatars) and attachments should also be exported under request (ask the user if he wants images and/or attachments when he is going to export, avatars should always be exported) and the JSON should contain the relative path to the file.


TLDR: after being granted permission, any user could export every message, post, comment, image, file, etc he has access to.


Additional note: if implemented, extending the export feature into a backup feature should be easy, just giving admins the possibility to export the rest of the users information and the global configurarion settings. Obviously this would require an equivalent import system to apply backups.

Thank you for the additional feedback. It's good to hear people recognizing JSON data exports as being fairly standard these days. We're evaluating the various "flavors" of export (single user, whole organization, compliance) in order to hopefully knock off most or all scenarios at once.

Just wanted to express the need and urgency from my (company) side;


First I'll reply to Mr. Pat Sullivan's question;

Both and much more.
We require the export option for both comfort and compliance purposes, however, these two are not the most important for why we need Export functionality in RYVER.

I can completely understand why this feature hasn't been developed or released until now, i'm sure that here many business considerations and much more, however, please do consider the following: 

* Many of us are trying to find the best platform/tool/assistant for our organization. Some require it for a specific need and some are trying to improve collaboration and enhance communication in general.


* Those of us who are working in mid-large organizations might go through hard times when trying to bring in a tool like RYVER into the company. A lot of people are afraid of changes, especially if you are trying to replace current half-baked solutions which you are not happy from.


* These worries which are led by uncertainty are being fueled even further with the following excuse: "We can work on RYVER for a month, two or even three, but what happens if we decide it's not for us? how do we take our content, which we have placed into RYVER, export it, and later decide what to do with it?"


This excuse is currently standing strong, especially when trying to push it in companies which are less experienced with collaboration platforms like RYVER.


Think of us as your sales personnel, selling RYVER in our own company. We need the appropriate tools to sell...


Thanks again for an amazing product.

We all wish to see much more of it.



Best Regards,

Shay D.

+1

Shay,


We agree with your reasons as stated.  The plan for us is as soon as we release the Task Manager this month, work on the enterprise version will start back up.  Much of it is finished and we are adding a few new engineers as I write this. The enterprise version is very important to us as it is the next step in our monetization.  So I can assure you it will get done.  I am hopeful sometime early 4th quarter of this year.  


Thanks for your thoughtful feedback!


Pat