Automatically attach source to supplied events/facts
Howdy,
When a source provides an event or fact, would there be a reason to NOT automatically attach the source to that event or fact? For instance, if I e.g. attach an 1840 U.S. census to a profile, and that census adds/provides an 1840 residence entry and a race, why would it not tag that/those event[s]/fact[s] with the supporting source evidence, the same as the source can do for name, birth, gender, death, burial, etc.? What is the rationale behind forcing an ensuing manual task to go attach the source? What is different about these items than the ones which DO automatically tag, such as birth, death, gender, name, burial?
의견
-
Just another user here. This has been requested frequently and I also hope the gets developed at some point.
What we were told here in communities by the designers when the new source linker was first released is that source tagging currently is dependent on there being a data field to tag the source to. For all the information in Vitals, that is, birth, etc. as you listed, the data field always exists whether it contains any data or not. So that data field can be tagged.
However, in the Other Information section, there are no data fields until we create them. This prevents the current method of tagging through the source linker. The source linker can't tag the source because there is nothing to tag with the current flow of the programming when the tagging should occur. The other complexity, is that if there are several residence fields in existence and you are attaching a source with a residence, the source linker cannot determine which residence the source should be tagged to.
With all the intricate programming of Family Tree, I'm sure the software engineers will get this figured out sooner or (more likely) later and just didn't have the opportunity to do so since they had to get the very old software of the source linker replaced before it died.
2 -
Rather astonishingly, today it appears that the source linker IS now attaching the source to supplied events/attributes. Thank you!
1 -
To events in Other Information?
0 -
Uh, nope, not for me: I just tested it by taking Source Linker up on its offer of adding a baptism (even though the event was already there under christening), and it showed up as an untagged custom event, as usual.
0 -
So far, I observe events and facts getting the auto-attach; specifically, adding residences and race from U.S. Census sources. I'll watch for other source types.
0 -
I specifically looked in the discussions in this group today to see if there had been an announcement about this apparently new functionality. I have noticed this happening over the last week or so. I've seen it happening for, among the "Other information" events, the following:
- "Voter Registration" custom events created when attaching a source from the dreaded "New Zealand, Electoral Rolls, 1865-1957" collection.
- "Occupation" events created from England and Wales census sources."Probate" and "Residence" events created from New Zealand probate sources.
- "Emigration" custom events and "Immigration" native events created from New Zealand passenger list sources.
- "Birth registration" custom events created from the "England and Wales Birth Registration Index, 1837-2008" collection.
You can see when this is happening in the source linker by clicking the "SHOW ALL" button before you click the "ADD" button; this will cause the appropriate checkbox to be displayed and ticked once you click "ADD".
0 -
Grr, I need pictures…
Adding a baptism is as aggravating as ever: the tags list even includes "christening", but the event is put under Other, untagged.
Adding an event indexed as a death registration, on the other hand, was surprising in a good way: the tags list included both "death" and "death registration"! Ditto for adding (the same person's) birth registration: when I clicked "add" on the "birth registration" event, it added "birth registration" to the list of tags.
It's not a matter of the age of the index, because I was working in Szarvas, which is all Lutherans, and those church records have only been indexed in the last two years, three max. It may still be dependent on the structure/setup of specific indexes/collections (in this case, the church register indexes versus the civil registration indexes), rather than on the specific fields involved — as in, the baptism-versus-christening problem may be just coincidence — but I can't figure out a way to test that: besides baptism/christening, the church registers only ever record events that have always been taggable (death, burial). Well, or marriages, but that's a whole 'nother kettle of fish.
0 -
I just checked using the "England and Wales Birth Registration Index, 1837-2008" collection example and indeed, as I would show if I could post an image, using the source linker for that collection does provide automatic tagging.
When the birth registration information is just on the left, under Automatic Tags it just has Name. After moving the information from left to right in the source linker, the Automatic Tags changes to show Name and Birth Registration. When attaching the source is completed, going to the Details tab shows the new Other Information of Birth Registration and it is tagged with the source.
This makes me wonder if this is something that needs to be enable on a collection by collection basis or if it needs to be enabled on a field by field basis. If either of these, I imagine it will be months before it is generally available for all fields in all collection.
Automatic tagging works for the United States 1930 Census.
It also works for the Norwegian Census of 1865.
In both of these cases, the automatic tag does not show until the information is moved from the left to right.
So maybe this is now working for everything. They really should trumpet when a long requested feature is released and working.
But back to the baptism/christening event. I have to say that I really like how they implemented this feature for baptism. The automatic tagging feature tags the baptism source to the christening field even when the christening field is blank. You can't see it until you add a christening, but it is there.
This will be my new work flow for christening record source hints that is efficient enough that I will go back to tagging christenings rather that just not bothering which is what I have been doing recently:
- Click the hint.
- Review the hint.
- Click to attach the hint.
- Move the baptism information from left to right so that the automatic tag to Christening appears.
- Click to finish attaching the source to the record.
- Go to the detail page.
- Copy the christening information from the Custom Other Event Baptism field to the Christening field where it belong. The source will already be tagged to that field and the tag will appear as soon as the information is copied in.
- Delete the baptism event.
Moving the baptism event information over in the source linker then deleting it is more efficient than using the current tagging technique from the detail page.
0 -
In my experience, baptisms have always tagged the christening field. They just never fill it.
Ah, I see: not quite, in the new linker.
In the old linker, the "christening" tag is available regardless of whether the "baptism" event has been added or not. In the new linker, that tag only becomes available if you take it up on the offer of the misfiled event.
I think I will continue to not take it up on that offer. It's faster/easier for me to tag the source to the christening at the same time I do so for the death, from the Sources page rather than the badly-disimproved ultra-click-happy conclusion end.
0 -
Another wrinkle: a marriage registration event doesn't offer a tag.
I'm attaching a marriage record in which, as usual for these Hungarian civil registrations, the index only has the marriage date, not the place, and has separate fields for the marriage registration's date and place. Naturally, there's no tag for the marriage event; that's off in its segregated section that Source Linker just barely manages to communicate with. However, the marriage registration event goes only in the current spouse's Other Information section, not the couple relationship section, so it should be able to be tagged exactly the same way as a birth or death registration — but Source Linker is not offering that option.
Once again, I can't tell whether the problem/difference is the specific field, or the particular index entry, or what.
0 -
About the "baptism" - it's a problem, I had to move the baptism stuff to christening box because that is what it is really in Deutschland.
infant christening and infant baptism are same, yet the one marked as baptism in index get booted down to "Facts". That render the person's ordinances unavailable.
0 -
All non-vital facts ('Other' or not birth, marriage, death fact) should be auto-tagged if:
- the user adds the non-vital fact to the person
- the two nonvital facts align on the right and left side
The list of facts that are not considered auto-tagged (because they are relationship facts):
Marriage, Common Law Marriage, Divorce, Annulement
0