You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In many cases, metadata tagged persons within a collection of photos have well defined relationships to one another.
It would be useful if there was the capacity to define an overall relationship identification system for an image's metadata, a base reference, and then add a relative identifier to each tagged region.
So, let's say that I have a group of 1910 Family Reunion photos. All the tagged persons are descendants of a well-defined proband. The tagged person relationships in the photos can be identified with an arbitrary descendant numbering system. So I uniquely identify the Proband (as an example, a specific WikiTree or FamilySearch ID profile), reference the relationship numbering system (i.e., a Modified Henry defined at a URI), and include the numbering system identifier to each tagged region.
The numbering system could be calculated (like a Ahnentafel number) or more arbitrary (like an employee number, SSN, or a WikiTree ID).
Chances are that, with recent development of automation tools for virus contact tracing, other complex relationship identifier systems could be leveraged.
The text was updated successfully, but these errors were encountered:
In many cases, metadata tagged persons within a collection of photos have well defined relationships to one another.
It would be useful if there was the capacity to define an overall relationship identification system for an image's metadata, a base reference, and then add a relative identifier to each tagged region.
So, let's say that I have a group of 1910 Family Reunion photos. All the tagged persons are descendants of a well-defined proband. The tagged person relationships in the photos can be identified with an arbitrary descendant numbering system. So I uniquely identify the Proband (as an example, a specific WikiTree or FamilySearch ID profile), reference the relationship numbering system (i.e., a Modified Henry defined at a URI), and include the numbering system identifier to each tagged region.
The numbering system could be calculated (like a Ahnentafel number) or more arbitrary (like an employee number, SSN, or a WikiTree ID).
Chances are that, with recent development of automation tools for virus contact tracing, other complex relationship identifier systems could be leveraged.
The text was updated successfully, but these errors were encountered: