Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

erase/delete files from disk

axel corjon
Hi,

the first time i remove a file from capture one (the photo was on a regular folder, not the catalog), it asked me if i wanted to remove from capture one AND remove the file from my disk, or just remove from capture one. I answered "just capture one" (it was what i was looking for this time). but now i'd really like to have pictures send to my computer trash when i remove them from capture one... any idea how to do that ?

thanx
axel
0

Comments

11 comments

Date Votes
  • Peter Sidell
    Within a C1 catalog create a separate trash or trash files folder on your desktop or a memorable spot.
    Move the files you wish to delete.
    select and delete the files within C1
    Delete the folder in the finder along with its contents
    Don't believe you can delete from disk from withinC1.
    0
  • BeO
    Top Commenter
    [quote="Peter762" wrote:

    Don't believe you can delete from disk from withinC1.

    Well, you could delete raw files from within C1 v8 (windows) which was part of my workflow. Just tagging them e.g. red and then delete all red variants incl. raw files. You were asked to either delete the variant from the catalog or also delete them from disk.

    Now I guess you have to move them to a folder which you can easily find and drop all images in that folder. Not handy.

    Cheers
    BeO
    0
  • RichardT
    [quote="BeO" wrote:
    [quote="Peter762" wrote:

    Don't believe you can delete from disk from withinC1.

    Well, you could delete raw files from within C1 v8 (windows) which was part of my workflow. Just tagging them e.g. red and then delete all red variants incl. raw files. You were asked to either delete the variant from the catalog or also delete them from disk.

    Now I guess you have to move them to a folder which you can easily find and drop all images in that folder. Not handy.

    Cheers
    BeO


    Using V9 with a catalog on Windows I still get the option to either delete the image from disk or just remove the reference from the catalog.

    I notice that in the Library tab, under the Recent Imports and Recent Captures icons, there is a Trash icon showing zero entries. I can click on it which makes it highlighted, but I have not found a way to move any image into it when working in a catalog - perhaps it only works with sessions?
    0
  • BeO
    Top Commenter
    I've just tested this again. Using V9.0.3 with a catalog on Windows I get the option to move it to the Trash when using the context menu > Delete. FOr a single image I am not asked, for mutiple images I get a message dialog beforehand.

    In the trash collection, when using selecting images and using menu>Delete, I am asked if I want to permanently remove it from catalag and remove from disk. Click on "delete"does empty the trash collectioin but not remove the files from disk.
    Referenced catalog.

    Seems like a bug.
    EDIT: No it isn't, it was a user error.

    cheers
    BeO
    0
  • RichardT
    In Preferences -> Warnings what options do you have ticked in the "Deletion" section at the bottom of the list.

    I currently have them all ticked.
    0
  • BeO
    Top Commenter
    I have them all ticked as well. I am fine with the warnings and the trash collection, but I want to have the files deleted from disk (when deleting from trash) when C1 says so 😕
    0
  • SFA
    Tricky decision on policy to delete from disk files that are Referenced.

    Files inside the catalogue - easier decision since it could just be assumed that the action was self contained.

    But referenced files may be in shared "ownership".

    Nevertheless I suppose it should be a decision of the user once they have been fully appraised of the effects of what they are about to do.



    Grant
    0
  • BeO
    Top Commenter
    Hi.

    I made a mistake. After installing v9 I did not realize that C1 did not use my previous v8 settings in the import dialog (which was "current location"). Instead it was set to "inside catalog". Setting it back to "current location" is works as in v8, i.e. it askes me to either remove the reference or remove from disk. No trash collection involved.
    So all seems fine.

    Cheers
    BeO
    0
  • BeO
    Top Commenter
    Hi Grant,

    imo, even with referenced files it should be the choice by the user. In case several users are working in a shared environment the workflow set up by this work group should be designed to reflect the risk of unintentional raw file deletions, if they want to, there are a lot of possibilites outside and inside of C1, e.g. "backup" during import.

    Cheers
    BeO
    0
  • RichardT
    [quote="BeO" wrote:
    Hi.

    I made a mistake. After installing v9 I did not realize that C1 did not use my previous v8 settings in the import dialog (which was "current location"). Instead it was set to "inside catalog". Setting it back to "current location" is works as in v8, i.e. it askes me to either remove the reference or remove from disk. No trash collection involved.
    So all seems fine.

    Cheers
    BeO


    Hi BeO,

    thanks for clearing that up, I was really puzzled why we were seeing different behaviour 😊

    Richard
    0
  • SFA
    [quote="BeO" wrote:
    Hi Grant,

    imo, even with referenced files it should be the choice by the user. In case several users are working in a shared environment the workflow set up by this work group should be designed to reflect the risk of unintentional raw file deletions, if they want to, there are a lot of possibilities outside and inside of C1, e.g. "backup" during import.

    Cheers
    BeO


    I was thinking more in terms of the use of multiple applications and the potential for deleting a file that one may have forgotten one is using with another application, also "referenced".

    Or even, say, working with a file that is Asset Managed by a different application.

    C1 does not really have a DAM but a PAM - Photo Asset Management - of sorts and for it's own use. A Document AM, in my opinion, should be an application that manages all document types (or at least all document types that are not incredibly specialised or obscure).

    A full DAM might also know which applications "have in interest in" each of the documents managed and therefore be in a position to provide warnings for attempted deletions. In effect it should be independent of any other application although there may be some grey areas in which it would be expected to support functionality from other applications owned by the same company. However I would not necessarily see that as something that would eliminate a requirement to check co-ownership of a file before deleting it.

    Having written all of that I don't use catalogues (avoiding their pseudo DAM roll) anyway. That makes my image management decisions somewhat clearer - apart from managing the various backup locations!


    Grant
    0

Post is closed for comments.