Technically, this is easy - we can make a swift account and away you go.

I don't want to tie anyone up in red tape, but I think it'd be good to have a lightweight process to ensure this doesn't just become a dustbin - so maybe we could have a wikitech page where we record for each dataset stored thus something like: (briefly) what it is; how long we should keep it for; who should have access; how big it is?

+1

In T350924#9323184, @MatthewVernon wrote:

I don't want to tie anyone up in red tape, but I think it'd be good to have a lightweight process to ensure this doesn't just become a dustbin - so maybe we could have a wikitech page where we record for each dataset stored thus something like: (briefly) what it is; how long we should keep it for; who should have access; how big it is?

Sounds good to me but access is always limited to DBAs (if you mean who DBAs can hand it over to, it gets complicated in some cases)

In T350924#9326604, @Ladsgroup wrote:

Sounds good to me but access is always limited to DBAs (if you mean who DBAs can hand it over to, it gets complicated in some cases)

I did mean the latter - presumably we're keeping these because we think they might be useful to someone in the future, and it'd be useful for future-us to know straightforwardly if there are restrictions on who we could show the data to.

The biggest problem for that is the reorgs, a lot of teams we set to own something might not exist in a couple of years, generally I think it's better to keep at the discretion of the DBA when the time comes I think.

What should we do to move this forward?

I think we've broadly agreed the "process"; do you want to put a wikitech page together with that (and the initial data set(s)) on? And suggest a name for the swift account and I'll get it made for you.