> Related, while there's no interface for user buckets in the staff client at > the moment, there > is infrastructure to support them, and this would be a good way to expose > merge functionality > to the librarian, I think.
Another good place to expose this would be in the Patron->Other->Groups display, where folks associate users into groupings representing families, classrooms, etc. I believe this grouping mechanism is what folks have been using in the past to link duped accounts. > Anyway, there are my thoughts, just off the top of my head. Is that > heading toward what you were thinking of in terms of implementation? Mike, in the past, I know you were also musing using actor.cards as an indirect link to users in places where users are referenced. So, for example, transactions would follow the cards and not the users, and then, for duped users you could simply move their cards to the good users. Is this still viable/desirable? -- Jason Etheridge | VP, Community Support and Advocacy | Equinox Software, Inc. / The Evergreen Experts | phone: 1-877-OPEN-ILS (673-6457) | email: [EMAIL PROTECTED] | web: http://www.esilibrary.com
