I think the memorial number *should* be in the Source Detail's File ID field. FAG is a source and that information is part of the source to help others readily find it.
I never have understood the need for yet one more number on the Individual's Information window. Sherry On Tue, Jul 11, 2017 at 8:09 PM, CE WOOD <wood...@msn.com> wrote: > Mine are in the Source Detail. It helps because I can also list the name > of the contributor of the memorial, which is *essential!* > > Over time, you begin to learn which contributors are diligent and which > just contribute to pad their numbers. > > And, very few do the requisite checking for alternate names or in the > cemeteries to see if the person already has a memorial. FAG has a totally > deficient search algorithm for cemeteries and people. It is not easy, but > it can be done if one is willing to take the time before contributing. > Alas, not everyone is. There are many duplicates and triplicates with > varying information about the same person! > > There is an incredible number of memorials just lifted from totally > unsourced websites; ones that have zero reputable sources (a website is *not > *a source). *No one* monitors the accuracy of the data. You *must* double > and triple check. > > CE > > > ------------------------------ > *From:* LegacyUserGroup <legacyusergroup-boun...@legacyusers.com> on > behalf of Ian Macaulay <macau...@icmac.ca> > *Sent:* Tuesday, July 11, 2017 3:38 PM > *To:* Legacy User Group > *Subject:* Re: [LegacyUG] New features suggestion > > But some of us kept the FAG numbers in a different place, and your > solution would not help. > I put mine is an event. > > On Tue, Jul 11, 2017 at 5:58 PM, Scott Hall <seh0...@gmail.com> wrote: > >> I submitted this through Milennia's suggest feature on their website, but >> also thought I'd post it here. >> >> It's great that Milennia keeps adding feature to LFT, but it would be >> really useful if you also added a way to convert existing data to take >> advantage of new features. >> >> For example, Find-a-Grave has been added to the SourceWriter, but no way >> has been provided to convert/update existing data using a different source >> template to the new one. This leaves the users either having to keep two >> sources for the same source, or manually identify and update the records -- >> for users with large files, that's a pain. >> >> In my case, given that LFT had no dedicated place to record Find-a-Grave >> memorial I use the flexible field "UserID" BUT ... when v9 added a >> dedicated field, there was no easy way to convert all the data in the flex >> field to the new field. >> >> In other words, we need some simple database tools added to the program. >> Perhaps not as much as the old LTools provided, but enough to be able to >> have a clean, consistent database that takes advantage of new features. >> >> For reference, my database is 102,100 individuals and growing. Manually >> moving data around is onerous. >> >> Thanks, >> Scott >> > >
-- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
