Yeah, I like the functionality! Much more useful, and avoids problems with fuzzy matches and renaming the wrong people. It's rejecting my edits for some reason, though, after I dismiss the warning sheet.
I wonder if the filtering would be more clear as a browser/tree view? On second thought, maybe that doesn't make sense... It's not clear at first glance what the relationship between the tables would be. On Jan 12, 2008, at 2:03 PM, Christiaan Hofman wrote: > Tell me what you think about my latest additions. It still needs some > more work. E.g. should only selected names be changed by an edit? We > could also allow editing in the names table, and then replace only > persons with that name. Also changes to the person fields may have to > be noted. And selection in the name table may be preserved when the > names change. > > Christiaan > > On 11 Jan 2008, at 6:39 PM, Adam R. Maxwell wrote: > >> >> On Friday, January 11, 2008, at 09:24AM, "Christiaan Hofman" >> <[EMAIL PROTECTED]> wrote: >>> >>> On 11 Jan 2008, at 5:13 PM, Adam R. Maxwell wrote: >>> >>>> >>>> On Jan 11, 2008, at 2:40 AM, Christiaan Hofman wrote: >>>> >>>>> It was displaying only the pubs for the author. That does not make >>>>> sense when you are showing an editor. >>>> >>>> Oh, I thought it was displaying all pubs that a person was >>>> associated >>>> with as author/editor/other. Didn't it use -[BibItem >>>> allPeople]? I'm >>>> pretty sure we added that for display and testing membership. >>>> >>> >>> No, it used -[BDSKPublicationArray publicationsForAuthor:], which >>> used -pubAuthors. ON the othr hand changing the name changed every >>> author in every field, with the comment that it did so because there >>> was no way to get the field. >> >> I'm not sure why that comment was there, since it sounds like >> expected behavior in retrospect :). Being able choose fields as >> you say is probably better. I guess the support for arbitrary >> person fields wasn't as finished as I thought. >> >>>>> I was thinking about making it more useful by adding a control >>>>> (table >>>>> or popup) to choose the fields to display. That could work as a >>>>> filter on the displayed publications, and also on where a name is >>>>> replaced. Similarly, I think it can be useful to display (and >>>>> filter >>>>> by?) all different forms of the name, so you can easily see if a >>>>> name >>>>> is spelled consistently or whether we have collapsed too many >>>>> names >>>>> (I'm thinking of Alexander and Alexeev Zamolodchikov). But I did >>>>> not >>>>> want to do anything like that before the release. >>>> >>>> Yeah, displaying all forms of the name would be useful. Grouping >>>> by >>>> any person would be useful as well (I thought we could do that, but >>>> apparently not). >>> >>> I was wondering if it should be any normalizedName (which is used >>> for >>> isEqual) or any originalName. >> >> What "it" would that be? >> >>> What do you mean by 'any person'? You mean any person field? >> >> Yes, using a set of all of the persons in a document. It might not >> be worth the hassle, though. > > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Bibdesk-develop mailing list > Bibdesk-develop@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bibdesk-develop ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Bibdesk-develop mailing list Bibdesk-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
