CUNY Academic Commons

Thanks so much, Colin. This is a great start.

The list is actually a bit more manageable than I thought it would be. Looking it over, I think it's likely that a tester could do everything on the list in, say, 30 minutes. This suggests to me that it's worth working through the exhaustive list when it comes to testing in the Reclaim environment.

I've just made some additions and edits to the doc here as per Boone's feedback. One thing I wasn't sure about was expanding on the testing steps for data export.

As far as I can tell on that screen in settings, you just click the button to export the data and that's that. Is there something else to test besides ensuring the exported file comes out well? There's no way to then import that file back into the Commons, is there?

As far as I can tell on that screen in settings, you just click the button to export the data and that's that. Is there something else to test besides ensuring the exported file comes out well? There's no way to then import that file back into the Commons, is there?

No, there's no import. You should just test that the data export request button works, and then I think you should get an email letting you know that it's ready for download (Scott, perhaps you can confirm this), and then confirm that it exports and that it contains your info.

I'm not sure that I want to pollute your workflows document with this, but I'd like to ask testers to do some additional pre-migration testing related to uploads and upload privacy. Here's a rough matrix:

Public sites vs private sites (Dashboard > Settings > Reading; the first two radio options are "public", the last three are "private)

Upload a new file (Dashboard > Media > Add New). The path of the uploaded file should be an S3 URL (either s3.amazonaws.com/files.commons.gc.cuny.edu or files.commons.gc.cuny.edu, depending on whether we're able to switch the latter on before launch).

If on a private site, the URL should have a bunch of parameters afterward (something like https://s3.amazonaws.com/files.commons.gc.cuny.edu/wp-content/blogs.dir/82/files/2023/12/joe-holland-80zZ1s24Nag-unsplash-edited-1-1536x1536-1.jpg?X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAZUO33UBRWHMWHNJB%2F20241230%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20241230T214059Z&X-Amz-SignedHeaders=host&X-Amz-Expires=21600&X-Amz-Signature=82cc23e08415bd154c54359cd055f3d97fabebf5bf5ac21a0c8ed13d081f5a9b) It should be possible to access the file at this URL, but impossible to access it at the version of the URL that comes before the question mark.

Find one or more existing sites you belong to on the production Commons (Dashboard > My Sites at the upper-left). If possible, find at least one that is private. Then, test that site on the Reclaim installation. Check whether existing uploads are accessible.

Create a new post or page on a private site and upload+insert an image. Test that the image is visible when loading the published page/post (the 'src' attribute should point to the "signed" version of the S3 URL)