Applies to: Details Mode
The behaviour of families when merging jobs is a key differnece when comparing Families to Folders.
When merging folders, folders with the same name
are always merged
When merging families the name of the families is irrelevant
Families with the same key are merged
Families with different keys are added
Example 1 - Families with the same key
This situation will arise when the jobs to be merged have the same origin. Consider the following workflow
An SQL job is created and since the families to be photographed are known beforehand they are added to the job. The screen grab below shows such a job.
The job is then exported to tnj for use with CapturePost. The screen grab below shows the Smith family in the tnj files.
Importing (merging) the tnj file into the original SQL job will merge the Smith family
Example 2 - Families with the same name but different key
There will be occasions where families in two different jobs (be they SQL jobs or tnj files) have the same name but different keys. In this case the families will not merge but will instead be added.
This approach caters for situations where different families may legitimately have the same name. In these cases families should not be merged.
The following three screen grabs show the folders and families for two jobs and the result of merging one into the other.
Note the Smith families in the two preceding screen grabs. Despite having the same name they are different families (different key). As a result a merge of these two jobs will result in two different Smith families as shown in the final screen grab below.
- Folders with the same name have been merged
- Folders (staff) not in the first job have been added
- Families with the same name but different keys have not been merged but have instead been added
End of article