Source Linker 95.5
The new source linker has been working well for all the work I have been doing recently attaching sources. I’m working in an area that has a good level of standardized places so had not noticed the current trouble with place names reported in the Family Tree help section here in Community. I hope that gets fixed soon.
Based on other remarks in Community that have helped crystalize my own vague thoughts, I do have three requests for the next major update of the Source Linker or sooner if possible.
1) Full display of the person’s Family Tree information after clicking Compare or when open by default rather than seeing only part of a person’s information on that view and only part of a person’s information under the Detail view.
Current:
Compare view vs Detail view
Requested:
Complete view
Reason: Many times a source will have duplicate information but will either have a different event type or an event type that can have multiple occurrences. When the person attaching the source cannot see the full information, it is easy to add duplicate, redundant information to the detail page that then just has to be deleted. For example, I often run across profiles where a mother will have eight identical residences because each one was added when a different child’s birth source was added. If the person attaching the source could have seen that the residence was already listed for the mother, he would probably not have moved a duplicate copy of the residence onto the detail page.
2) The ability to tag the source being attached to any piece of data currently on the person.
Current:
Requested:
Reason: Often a source should be tagged to a piece of information on the Family Tree information that does not have a corresponding item in the source. Expanding the tagging options would allow more efficient taking to all appropriate data. In my illustration, for example, it would be nice to be able to tag the duplicate residence to the existing, correctly spelled residence. (I’ll leave it up to the designers to figure out how to differentiate between data with the same title.)
3) The ability to drag and drop events to line them up correctly. This would also help n stopping the addition of duplicate information and in tagging efficiently.
Current with request (1) implemented:
Requested:
Before -
After -
Reason: There are various source collections where the indexed event type does not match correctly with the proper Family Tree entry. Being able to force the source data to properly line up with the Family Tree data would prevent unnecessary duplication of events and would assist in proper tagging of sources to events.