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
{{ message }}
This repository has been archived by the owner on Sep 11, 2019. It is now read-only.
I have been thinking about scenarios to use stitching on the GrAMPS-level, and the only use case I can come up with is when I want to stitch to another datasource. However, to keep datasources as independent as possible, I would like to add the feature to:
Specify which datasource I want to stitch to (based on its unique namespace)
Only apply that stitching if the datasource is part of my collection of datasources
To achieve this, I propose adding a key to the stitching object like this:
I have been thinking about scenarios to use stitching on the GrAMPS-level, and the only use case I can come up with is when I want to stitch to another datasource. However, to keep datasources as independent as possible, I would like to add the feature to:
To achieve this, I propose adding a key to the
stitching
object like this:So if I setup my GrAMPS like this:
That only the stitching on
myDatasource
toxckd
is applied, and not tomyOtherDatasource
, because those types, and that data, is not available.The text was updated successfully, but these errors were encountered: