IPTC (and other) token when importing such as 'Job identifier'
It would be nice to be able to define/edit such tokens at the import time, because i do not see how to pre-edit them otherwise, and there is no way to add the standard metadata tool in the import tool tools which contains only an extremely limited metadata tool capability (copyright and description).
As such token are also valid choices for other fields' definition such as the import folder location, those tokens are useless unless another tool is used to edit the photo beforehand which is simply inefficient. Most cameras do not allow editing such token excepted the copyright which is the one of the two metadata field that can be edited in the import tool.
A way to preset any of the token fields (which also should allow to keep the existing photo value) should be permitted at the photo import time for sake of simplicity.
-
Francois,
I am not sure whether this would fully cover your request for practical purposes but you can create "Styles" and "Presets" for Metadata content, allow them to be stacked and use them during the import process.
Of course this is mostly helpful for content that is always used - copyright and similar.
However, if there is a similar requirement on a per-shoot basis it may be a good way to apply some of the data.
I have looked at that for event shoots where all (or most) images will have common TPTC field entries in some fields. However usually I will decide to import first, select one image to create the entries for the common fields data and then simply select all of the other images and copy paste. In effect the result is the same and takes just a few seconds.
I could foresee some benefits for extending the concept to cover additional fields that are not common data values for all images but I have not convinced myself that, for my needs, I would be able to successfully control such data at the point of import. Or at least, if I could it would be just as much work - or more - than is involved creating the data after import.
For studio shoots involving tethering, the tethering functionality offers some options for dealing with such needs but I am not convinced that most other situations would benefit greatly from such a facility.
I would be happy to be proved wrong.
I could see the benefit of being to make use of other tools, for example the Metadata tool, when the Import process screen is active.
I think if you wish to modify Metadata entries as part of token use that should really only apply to IPTC fields.
I could see a case for Geo data changes as well but whether that would really be something that would make sense to change during an import process rather than after import is perhaps debatable. It would also be part of a requirement for functionality that C1 does not currently possess.
0 -
I agree with most of your remarks, however, there are parts that are job related and not photo related:
The import function serves multiple functions:
1/ save the capture photo to a specific location, basically storage classification
2/ backup the capture photo to a specific location, basically storage classification
3/ add possible information to the photo that depends on the capturing operation such as camera used, photographer that justify pre-set styles
4/ apply possible processing information in dependence of the capture process such as day/night/indoor that justify pre-set styles
Factors that impact related metadata settings are:
a/ the justification of the photo (customer, project, task…)
b/ the photo type (interview, show, landscape…)
c/ the subject (person, group, environment, specific setup…)
d/ the location(country, area…)
Some of the metadata information can have impact on some of the import functions. This is the liberty of C1 customer to decide this.
In the current C1 import processing, the automation is very limited because, while the token list is large, there is no way to update unfilled metadata until the photo are imported. This particularly stringent for the set a and d, and could also be the case of the b & c set in regard to the import function 1 and 2, but not only.
I may understand you do not want to update the official metadata in batch mode for various reason, but then why not allow the customer to add its own metadata fields which can then be used to parametrize the import function.
I have previously made a request to have import recipes like what exists in the output process, this all concurs to the same ideas.
The immediate key issue is the management of the photo storage location, backup location and initial automated photo pre-processing.
When the photo are imported in capture one, then of course, everything can be changed as desired.
0 -
Capture one doesn't have "Solution" to add/update metadata dynamically during import process similar to Photo Mechanic. Instead Capture one suggests "Work Around" by creating Presets ahead and use during import. So you have to update Preset prior to each import. So the solution is to use Photo Mechanic to update Metadata along with GPS coordinates during Ingest and then cull, tag and rate before import into Capture one.
As Capture One doesn't allow to update GPS coordinates even after import it has to be done ahead otherwise no way to update GPS coordinates inside Capture one.
I got frustrated with this 2 stage process, I have submitted detailed feature request including Import Image dialog Design while ago. As usual no visibility or feed back on the status of the request. Also I am not sure under which layer or their priority list it is sleeping now...
0 -
Hi François,
At the back of my mind from a long time ago I have some sort of recollection of being able to make use of the "Style" or "Preset" concept to both load the data into the specific fields AND have the values used for Token values and subfolder creation.
Maybe I have misremembered that as I cannot make the process deliver that result in one pass using IPTC fields populated by the "Styles" during current testing. The Styles work well enough, just not at the right time in the process to be available for setting folders, etc.
A 2 pass approach, firstly applying the metadata and then doing a second "import" to distribute and create the sub-folders, would work but it would be better if it was one pass.
If the order of processing in the import could be changed to build first the metadata fields in memory and then derive the folders to be used as well as write the metadata values the process could become one step.
In effect that would be the same requirement if the developers provided a metadata population window as part of the Import process as you have suggested.
In my typical use case, any "file system" grouping would usually be quite limited for the segregation of images because many images (the majority) will cut across such categorisation boundaries. It is better to use "smart album" type approaches to create the required grouping and that makes the segregation redundant.
I am less concerned about dealing with backup at that point, other than having copies of the images saved somewhere off the system. Later I will back up the session as it develops and that will usually be enough.
0
Post is closed for comments.
Comments
4 comments