Page Comparison

...

1. It's our understanding that Diamond users are already downloading data from the datastore and uploading it to ECHO in a manual process.

   1. Who exactly is doing this?

   2. How are they doing this?

   3. Why are they copying data to ECHO, what project need? programmatic access?

2. In a world where there is a button next to the download button where users can “copy the data to ECHO”,

   1. What access requirements does Diamond need, who can copy data to echo?

   2. Is the ECHO storage based on user or investigation?

      1. If it's based on an investigation, then should we add the ECHO location to ICAT?

      2. If it's based on an investigation, then it wouldn’t be transferred to ECHO more than once.

   3. Whoever can copy data to ECHO, presumably these users would need ECHO access/credentials as well? Who manages these credentials?

3. What space quotas are needed:

   1. What quotas are in place on ECHO at the moment?

   2. How might this change going forward?

4. I’m aware that Diamond wants a “spinning disk cache” for quicker access to data.

   1. How does this relate to this project?

   2. How do we stop the abuse of the system where the whole catalogue starts creeping over to ECHO?

5. How long does the data need to stay on ECHO for?

6. As far as i’m aware, there is no data monitoring going on in ECHO. Would it make sense for users to be denied write access to ECHO, so only data from the catalogue ends up there?

...