On 25 June 2018 at 12:01, sebb <[email protected]> wrote: > I've been trying to check that we have files in member_apps for all > entries in members.txt. > > This is proving quite difficult, as there are lots of ways of spelling > names, for example: > > Joe Bloggs > Joe Bloggs, Jr. > Joe A. Bloggs, Jr. > Joseph Bloggs > etc. > > It occurs to me that members must have availids (*), so one possible > solution would be to use that as the file name (or perhaps as a > filename prefix?) > > AFAIK there are no duplicate names (yet) in members.txt, but that is > not impossible going forward. > > Of course, this assumes that availids are immutable and everlasting. > > Note: I am planning on committing some library code to handle all > access to the member_apps files so that apps all use the same methods > to find the files. > > Similarly for iclas, although we don't have the same problem with > matching file names, as iclas.txt contains the filename stem. > > > (*) There is one member without. The file could be left as is, or > prefixed 'notinavail' I suppose.
Actually there are 4 members without ids; these don't get extracted by the code so their membership app files (if any) are not matched. However I have managed to fix all the other mismatches by some renaming of the files. Sometimes the app file contains a name that does not exactly match the legal, public or members.txt name. In which case the filename does not exactly match the name in the file itself, but it does match one of the other 3 names. I still think we should consider using avail ids where they exist. Given that entries without ids don't currently get extracted, that would not affect the outcome.
