Pam D.

I’d like to chime in with agreement. A few years ago, my organization made a strategic decision not to handle data privacy a certain way because we expected, based on everything we had been hearing, that privacy features would be coming. But instead, they are gate-kept at the enterprise level, which we cannot afford. It’s incredibly disappointing, and just one of many reasons I do not have the faith or enthusiasm with Dovetail that I did a few years ago.

I love this idea. How are you defining first-hand and second-hand data? I think I get the gist, but would love to hear more detail about how you both conceptualize and classify these differences in data.

My best guess is it’s handled by your PEI admin and Dovetail can’t help. But that’s just based on my own experiences, I could be wrong.

I think you need to get permission from whoever is the admin of your Slack workspace (PEI) to enable it?

I do see that. Is that supposed to be where to filter?

I believe it, Emi. We have 60 users and 15+ teams. It’s not sustainable, and I will be looking for options for next year.

I did this recently and it was not fun. I had to pull together my own documentation to understand what was changing and what the impacts were, and I still ran into knowledge gaps that I could not proactively fix. The big ones being access control (despite being a “manager” I could not reset access controls on behalf of others, and I could not get a high level overview of which projects became read-only) and communicating the impact of losing workspace tags. It created a lot of work for me that is still ongoing. I wish the documentation had been better, but I also wish the entire migration experience had been better. Although I wish ultimately that we could have kept our Legacy plan, as losing these key features seriously hamper all the plans I had to shepherd our large and disparate research community.