Problem with deleting and labelling JPG and RAW

[cerp]

Dear all,

We use digikam to manage our photographic assets.

One issue we have is that when we are on an assignment we normally  
shoot RAW + JPG, like most photographers.

When we go back, we then download photographs from the camera in a  
buffer disk, we first look quickly at the JPG to decide quickly which  
one to keep and which ones to throw away, then we take the one we keep  
and we categorise them (with labels) work on the RAW to obtain exactly  
the cuts and feel we need, then we move everything to archive.

One of the two big problems we have is that when we scan the JPG to  
decide what to keep and what to throw away, deleting the JPG does not  
delete the RAW, and marking the JPG does not automatically mark the  
RAW, so you haev to carry out every operation twice, which requires  
twice as much time. That is a huge problem.

How do we solve it?

PS: Separate email for the other problem.

Best Regards
Corrado & Rina

[AndriusWild]

Hello Cerp 

Please take a look here:

https://discuss.pixls.us/t/culling-process-in-digikam/3000/5

Hopefully it works.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: cerp <[hidden email]>

Date: 2017-01-13 8:56 AM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Problem with deleting and labelling JPG and RAW

Dear all,

We use digikam to manage our photographic assets.

One issue we have is that when we are on an assignment we normally 
shoot RAW + JPG, like most photographers.

When we go back, we then download photographs from the camera in a 
buffer disk, we first look quickly at the JPG to decide quickly which 
one to keep and which ones to throw away, then we take the one we keep 
and we categorise them (with labels) work on the RAW to obtain exactly 
the cuts and feel we need, then we move everything to archive.

One of the two big problems we have is that when we scan the JPG to 
decide what to keep and what to throw away, deleting the JPG does not 
delete the RAW, and marking the JPG does not automatically mark the 
RAW, so you haev to carry out every operation twice, which requires 
twice as much time. That is a huge problem.

How do we solve it?

PS: Separate email for the other problem.

Best Regards
Corrado & Rina

[cerp]

It does work, but it seems a bit convoluted .... it is quite standard  
behaviour that is used for DAM, I believe.

Best,


Quoting Andrey Goreev <[hidden email]>:

> Hello Cerp 
> Please take a look here:
> https://discuss.pixls.us/t/culling-process-in-digikam/3000/5
> Hopefully it works.
> Sent from my Samsung Galaxy smartphone.
> -------- Original message --------From: cerp <[hidden email]> Date:  
> 2017-01-13  8:56 AM  (GMT-07:00) To: digiKam - Home Manage your  
> photographs as a professional with the power of open source  
> <[hidden email]> Subject: Problem with deleting and labelling  
> JPG and RAW
> Dear all,
>
> We use digikam to manage our photographic assets.
>
> One issue we have is that when we are on an assignment we normally 
> shoot RAW + JPG, like most photographers.
>
> When we go back, we then download photographs from the camera in a 
> buffer disk, we first look quickly at the JPG to decide quickly which 
> one to keep and which ones to throw away, then we take the one we keep 
> and we categorise them (with labels) work on the RAW to obtain exactly 
> the cuts and feel we need, then we move everything to archive.
>
> One of the two big problems we have is that when we scan the JPG to 
> decide what to keep and what to throw away, deleting the JPG does not 
> delete the RAW, and marking the JPG does not automatically mark the 
> RAW, so you haev to carry out every operation twice, which requires 
> twice as much time. That is a huge problem.
>
> How do we solve it?
>
> PS: Separate email for the other problem.
>
> Best Regards
> Corrado & Rina

[Simon Frei]

What is convoluted?
If it is having to group them manually, that could be solved by an
option on import to group by name. That would be a very useful feature
indeed. There is already a more broad feature request about grouping on
import: https://bugs.kde.org/show_bug.cgi?id=121310

On 13/01/17 17:23, cerp wrote:

> It does work, but it seems a bit convoluted .... it is quite standard
> behaviour that is used for DAM, I believe.
>
> Best,
>
>
> Quoting Andrey Goreev <[hidden email]>:
>
>> Hello Cerp
>> Please take a look here:
>> https://discuss.pixls.us/t/culling-process-in-digikam/3000/5
>> Hopefully it works.
>> Sent from my Samsung Galaxy smartphone.
>> -------- Original message --------From: cerp <[hidden email]> Date:
>> 2017-01-13  8:56 AM  (GMT-07:00) To: digiKam - Home Manage your
>> photographs as a professional with the power of open source
>> <[hidden email]> Subject: Problem with deleting and labelling
>> JPG and RAW
>> Dear all,
>>
>> We use digikam to manage our photographic assets.
>>
>> One issue we have is that when we are on an assignment we normally
>> shoot RAW + JPG, like most photographers.
>>
>> When we go back, we then download photographs from the camera in a
>> buffer disk, we first look quickly at the JPG to decide quickly which
>> one to keep and which ones to throw away, then we take the one we keep
>> and we categorise them (with labels) work on the RAW to obtain exactly
>> the cuts and feel we need, then we move everything to archive.
>>
>> One of the two big problems we have is that when we scan the JPG to
>> decide what to keep and what to throw away, deleting the JPG does not
>> delete the RAW, and marking the JPG does not automatically mark the
>> RAW, so you haev to carry out every operation twice, which requires
>> twice as much time. That is a huge problem.
>>
>> How do we solve it?
>>
>> PS: Separate email for the other problem.
>>
>> Best Regards
>> Corrado & Rina
>
>
>

[cerp]

I meant that in my opinion, the current solution, where you have to  
select and group manually is convoluted.

The solution you propose is better (automatic grouping), but in my  
opinion it would be better if JPG and RAW where linked automatically  
without using the grouping feature, so that we would still be able to  
use grouping for other issues.

Best,


Quoting Simon Frei <[hidden email]>:

> What is convoluted?
> If it is having to group them manually, that could be solved by an
> option on import to group by name. That would be a very useful feature
> indeed. There is already a more broad feature request about grouping on
> import: https://bugs.kde.org/show_bug.cgi?id=121310
>
> On 13/01/17 17:23, cerp wrote:
>> It does work, but it seems a bit convoluted .... it is quite standard
>> behaviour that is used for DAM, I believe.
>>
>> Best,
>>
>>
>> Quoting Andrey Goreev <[hidden email]>:
>>
>>> Hello Cerp
>>> Please take a look here:
>>> https://discuss.pixls.us/t/culling-process-in-digikam/3000/5
>>> Hopefully it works.
>>> Sent from my Samsung Galaxy smartphone.
>>> -------- Original message --------From: cerp <[hidden email]> Date:
>>> 2017-01-13  8:56 AM  (GMT-07:00) To: digiKam - Home Manage your
>>> photographs as a professional with the power of open source
>>> <[hidden email]> Subject: Problem with deleting and labelling
>>> JPG and RAW
>>> Dear all,
>>>
>>> We use digikam to manage our photographic assets.
>>>
>>> One issue we have is that when we are on an assignment we normally
>>> shoot RAW + JPG, like most photographers.
>>>
>>> When we go back, we then download photographs from the camera in a
>>> buffer disk, we first look quickly at the JPG to decide quickly which
>>> one to keep and which ones to throw away, then we take the one we keep
>>> and we categorise them (with labels) work on the RAW to obtain exactly
>>> the cuts and feel we need, then we move everything to archive.
>>>
>>> One of the two big problems we have is that when we scan the JPG to
>>> decide what to keep and what to throw away, deleting the JPG does not
>>> delete the RAW, and marking the JPG does not automatically mark the
>>> RAW, so you haev to carry out every operation twice, which requires
>>> twice as much time. That is a huge problem.
>>>
>>> How do we solve it?
>>>
>>> PS: Separate email for the other problem.
>>>
>>> Best Regards
>>> Corrado & Rina
>>
>>
>>

[AndriusWild]

Sometimes I delete DNG but keep JPG so I am not sure if the permanent link between RAW and JPG would work for me...

I am not an expert but I think the database might become pretty complex too.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: cerp <[hidden email]>

Date: 2017-01-13 10:10 AM (GMT-07:00)

To: Simon Frei <[hidden email]>

Cc: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Problem with deleting and labelling JPG and RAW

I meant that in my opinion, the current solution, where you have to 
select and group manually is convoluted.

The solution you propose is better (automatic grouping), but in my 
opinion it would be better if JPG and RAW where linked automatically 
without using the grouping feature, so that we would still be able to 
use grouping for other issues.

Best,


Quoting Simon Frei <[hidden email]>:

> What is convoluted?
> If it is having to group them manually, that could be solved by an
> option on import to group by name. That would be a very useful feature
> indeed. There is already a more broad feature request about grouping on
> import: https://bugs.kde.org/show_bug.cgi?id=121310
>
> On 13/01/17 17:23, cerp wrote:
>> It does work, but it seems a bit convoluted .... it is quite standard
>> behaviour that is used for DAM, I believe.
>>
>> Best,
>>
>>
>> Quoting Andrey Goreev <[hidden email]>:
>>
>>> Hello Cerp
>>> Please take a look here:
>>> https://discuss.pixls.us/t/culling-process-in-digikam/3000/5
>>> Hopefully it works.
>>> Sent from my Samsung Galaxy smartphone.
>>> -------- Original message --------From: cerp <[hidden email]> Date:
>>> 2017-01-13  8:56 AM  (GMT-07:00) To: digiKam - Home Manage your
>>> photographs as a professional with the power of open source
>>> <[hidden email]> Subject: Problem with deleting and labelling
>>> JPG and RAW
>>> Dear all,
>>>
>>> We use digikam to manage our photographic assets.
>>>
>>> One issue we have is that when we are on an assignment we normally
>>> shoot RAW + JPG, like most photographers.
>>>
>>> When we go back, we then download photographs from the camera in a
>>> buffer disk, we first look quickly at the JPG to decide quickly which
>>> one to keep and which ones to throw away, then we take the one we keep
>>> and we categorise them (with labels) work on the RAW to obtain exactly
>>> the cuts and feel we need, then we move everything to archive.
>>>
>>> One of the two big problems we have is that when we scan the JPG to
>>> decide what to keep and what to throw away, deleting the JPG does not
>>> delete the RAW, and marking the JPG does not automatically mark the
>>> RAW, so you haev to carry out every operation twice, which requires
>>> twice as much time. That is a huge problem.
>>>
>>> How do we solve it?
>>>
>>> PS: Separate email for the other problem.
>>>
>>> Best Regards
>>> Corrado & Rina
>>
>>
>>