CUNY Academic Commons

Steve writes:

"Thanks to you and Boone, Scott. I’d also suggest adding the functionality of being able to change file and folder names in the Files section, mostly for the same reasons as wanting to be able to edit something once you’ve committed to it.
Best,
Steve"

And also:
"One more thought: there doesn’t seem to be a way to create a folder structure for materials AFTER you’ve downloaded materials to the Files section. Can that functionality be added too?"

Thanks for passing this along, Scott. A complete overhaul of this section would be nice to do, but we'll have to talk as a team about how to align it with our other priorities, including a more dramatic redesign that may supersede our smaller changes.

Boone Gorges wrote:

Before diving into this too much, I wanted to post screenshots of what the interface looks like on the OpenLab. One screenshot shows the top-level view (not in a folder), and the second shows what you see when you click into a folder. We add a header (similar to on CAC, but more set off visually) and the delete button appears in that header. Sonja, when you have a chance, would you let me know whether you think this is an OK paradigm for us to follow? We don't really have conventions for float-right buttons like this, so I'd probably go for a text link instead. See mockup.

Sorry for my late response to this ticket. Yes this looks like a good solution. I agree that a "Delete" link on the folder level would work better than a button. Do you need me to design something for this?

If you're happy with something like the OpenLab screenshots, then no need for an up-front design - I can take a first crack at it.

Sounds good to me, Boone.

Boone Gorges wrote:

Added in https://github.com/cuny-academic-commons/cac/commit/eb5d750da9b8440d53e416c18a22ec0661824d8c. I've attached a gif of the link in use. This whole interface is pretty clunky (see #12091 and other tickets) but I think this is a useful addition for now.

Thanks Boone, yes the interface could definitely use an overhaul especially with feature requests like #12091 in mind. But for now I agree this would solve the issue at hand.