Joss Winn wrote:
> Firstly the AD accounts are not unique in perpetuity,
> i.e. John Smith (jsmith) works here, leaves, then Joan Smith joins, her
> account will also be jsmith. Will the repository show all Johns
> submissions as hers. This also means that the Email address for deleted
> accounts should be removed.
If you are looking for PERSISTENT user ids, then your out of luck: there
is no simple technological solution.
The only advice I can give you is to hack the eprints database once a
Let is assume that John Smith has a login of 'jsmith', matching a userid
of '3' (all eprints are stored against a userid, which helps here)
Once John Smith leaves, you will need to edit the database so that the
userid of three has a username of 'thispersonhasleft123'.
When Joan Smith starts, they get a new user account, with the now-free
username 'jsmith', but with their own userid (say '4567')
One thing to remember is that the name of the depositor is not the name
of the author - they are completely separate things!
(that is not to say that author-as-depositor is not a desirable
position, rather that experience is that most deposits are no by the
author [in practice] )
> Secondly, name changes, how will they be handled ie
> when Joan marries F Bloggs, how will any submissions she made as jsmith
> be shown.
The "name" of the user is separate from the username (the username
'edina23' can have a displayed name of Ian Stuart, or Code Gorilla, or
Fred Flintstone... and the user can edit that on their "Modify Profile"
> These problems are not unique to the repository, we are currently
> working through the same issues for Blackboard as we move to using the
> AD as our source for staff accounts.
If there is a premis that LDAP usernames can be recycled, then you are
on a hiding to nothing
(which is why EDINA requires institutions to guarantee *persistent*
unique IDs for users for some of its services)
Developer for the Depot
The University of Edinburgh.