Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve the "replacing and deleting file" experience #1564

Open
mjordan opened this issue Jul 20, 2020 · 3 comments
Open

Improve the "replacing and deleting file" experience #1564

mjordan opened this issue Jul 20, 2020 · 3 comments
Labels
Subject: User Experience Related to a user’s experience with the software.

Comments

@mjordan
Copy link
Contributor

mjordan commented Jul 20, 2020

This issue comes out of #1208, which was about documenting how replacing and removing files and media works. In both cases as described below, the file and its metadata are removed from Drupal but persist in Fedora.

This issue suggests how we could implement a UI for replacing and removing files and media that is consistent with users' reasonable expectations (i.e., from both Drupal and Fedora). Any UI for also acting on resources in Fedora should take account for the case where Fedora is not present in the Islandora stack bento by not showing UI elements that purge content from Fedora.

Replacing a file

Currently, if you want to replace a file using the "Remove" button in the file's media entity, the replaced file is removed from the media in Drupal, but is not removed from Fedora.

It would be useful to be able to choose whether the replaced file is retained in Fedora, whether it is entirely expunged, or whether a new version of the file and its metadata are created, as illustrated here:

replace

Deleting a file

Similarly, for media deleted from Drupal at http://localhost:8000/media/X/delete, the binary and its metadata persist in Fedora. The only way I've found of verifiably deleting a file and its metadata is to run the "Delete media and file(s) action" in the general media list (http://localhost:8000/admin/content/media).

It should be possible to add an option to this form that executes the code in the "Delete media and file(s) action" so that the user doesn't have to go to http://localhost:8000/admin/content media to actually delete a file and its media but instead can do it closer to the node the file is associated with. For example:

remove

@mjordan mjordan added the UX label Jul 20, 2020
@wgilling
Copy link
Contributor

Should there also be a "Default purge action when deleting" checkbox at the Islandora | Core Settings? or even to control these defaults per content-type -- of course, the default action could be overridden at the node/delete stage.

@seth-shaw-unlv
Copy link
Contributor

If the setting was part of the widget it would set per media type.

@skaught
Copy link

skaught commented Dec 21, 2023

Original ask here:

  • "checbox option to delete this and Purge 'fedora' as well; OR create NEW VERSION"
  • Config Delete screen: add option to purge.
    Certainly in Drupal the flow for deleting the Media Entity this way would normally not remove the file. As we are additionally talking around the use of 'Fedora' as a File System micro-service to store the media aid the persistence of these files (library content)

The media could also be linked within content in other wise too. Content Revision and any workflow also would have fallout around this.

A general mention: Entity Delete related hooks would be better off to look. Again, purpose & persistance of content/media, revision & workflow should be considered

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Subject: User Experience Related to a user’s experience with the software.
Projects
Development

No branches or pull requests

5 participants