Analyzer set recording

[alejoe91]

This is useful for example if the analyzer was set up and ran with a tmp cached recording, but later on one wants to set a lazy recording to perform additional operations and computations

[zm711]

I really like this idea because we often do the analysis and then move everything over to our server for long-term storage which means the recording-analyzer link gets broken. My only concern (and this is now from experience helping others) is that people forget what goes with what. So is there any way we can have a safety check? This is honestly the end-users responsibility not to mess up, but are there any attributes on the analyzer that could say help make sure the recording being temporarily used is reasonable?

[alejoe91]

I really like this idea because we often do the analysis and then move everything over to our server for long-term storage which means the recording-analyzer link gets broken. My only concern (and this is now from experience helping others) is that people forget what goes with what. So is there any way we can have a safety check? This is honestly the end-users responsibility not to mess up, but are there any attributes on the analyzer that could say help make sure the recording being temporarily used is reasonable?

I think that we could check that the recording has the correct recording attributes, i.e., channel_ids, locations, etc

[alejoe91]

@zm711 can you check this again after the last commit?

[zm711]

This is good by me once tests pass . Was @samuelgarcia going to do a final readthrough as well?