Support the CC file manager (integrate it into the UI)

[hackartisan]

Once we have nested works, we want to be able to order objects within works.

Blocked by #2199 and #2243.

[mjgiarlo]

Related to (and blocked by) #2243.

[mjgiarlo]

This may be an epic.

[hackartisan]

We also need to be able to order files (FileSet objects) which I gathered is part of the file manager, as well. My understanding is that Works and FileSets can be ordered (and intermingled) on a given parent.

[mjgiarlo]

@HackMasterA This would be good to verify in the latest release of CC.

[mjgiarlo]

@HackMasterA A good first bit of work for this ticket would be to spin up CC and see what all tools it provides around ordering (of collections, works, and filesets). A follow-up would be to see how we might enable these same features in Sufia.

[hackartisan]

Messed around with curation concerns.

Works: There's a link on a work view page 'File Manager'. The file manager (see screenshot) allows you to drag/drop reorder files and works. Each File(Set)/Work object has a little box with thumbnail, editable title, 'edit' link going to e.g. /concern/parent/p5547r588/file_sets/vq27zn652. Thumbnail links to e.g. /concern/file_sets/vq27zn652. Both links take you to identical pages except the route; I don't understand this.

There's no ordering on Collections or FileSets. FileSets also don't appear to allow manual additions at this time.

[hackartisan]

file_manager exists in sufia but looks a little wonky.

[hackartisan]

There's no drag/drop functionality in the sufia page. probably missing javascript. I guess the question is do we want this functionality separate or do we want it as part of our works edit form? In UI discussions i recall an assumption of the latter. but since ordering can intermingle files and nested works I'm not sure that's possible; they're under different tabs. Maybe that decision should be revisited, even.

[mjgiarlo]

@HackMasterA Great, thanks for the investigation so far!

Re:

I guess the question is do we want this functionality separate or do we want it as part of our works edit form? In UI discussions i recall an assumption of the latter. but since ordering can intermingle files and nested works I'm not sure that's possible; they're under different tabs. Maybe that decision should be revisited, even.

what do you think about raising it on tomorrow's Hydra Tech call?

[hackartisan]

@mjgiarlo sure I'll add it to the agenda for tomorrow. see also #2432

[mjgiarlo]

@HackMasterA yep, just dropped a comment there too. 😄

[hackartisan]

Tech call revealed no strong feelings on the location of this functionality, but support for providing it.

[mjgiarlo]

@HackMasterA If you have strong leanings, I'd encourage you to follow them, then! Barring that, we should look to better align Sufia and CC by having Sufia use/link to the file manager in the same place(s) if that sounds reasonable to you.

Thanks for running that by the tech call folks.

[hackartisan]

Here are the different options for this, UI-wise.

1. Integrate child works and filesets into a single list/tab on the edit page.
   1. Integrate drag/drop functionality directly into this list.
      1. pros: Most consistent UI/UX; the approach discussed in Sufia UI working group
      2. cons: Probably will take the longest. Sufia codebase drifts from cc.
   2. Put a button linking to the filemanager near this list.
      1. pros: At least the button leading to this functionality is near the list when it's being edited
      2. cons: You're linking to a form from within another form. Confusing for developers and users to sort out the implications of this.
2. Link to fileset manager from work show page for logged-in users with edit permission.
   1. pros: More achievable
   2. cons: not consistent with our UI/UX strategy. users wanting to order at upload time may be confused.

I believe 1(i) is the correct approach, but I do not have the time to make it happen. Therefore, in service of getting something working at all, I'll go for 2.

[mjgiarlo]

@HackMasterA sounds good.

to confirm, 1(i) is #2459?

[hackartisan]

@mjgiarlo no, I didn't ticket 1(i). #2459 is something we have to do on the show page side regardless. because once we have these things ordered there's no view that shows their order unless we do that.

[mjgiarlo]

Ah, duh. OK!

[hackartisan]

blocked by samvera-deprecated/curation_concerns#896

[mjgiarlo]

@HackMasterA unblocked by samvera-deprecated/curation_concerns#898, yay!