Duplicate Authors

NRAO Interactive Services Modification Request 2C109, February 2009



1. Introduction

There are currently many duplicate authors in the user database. We want to accomplish two things through this MR: 1) remove as many duplicates as possible with existing authors, and 2) prevent new users from registering duplicate accounts (which may include preventing collaborators from incorrectly registering a new stub for an author that's already in the database).

2. Background

The problem of duplicate entries makes it difficult for proposers to find their collaborators.

3. Requirements

There is flexibility in how this MR can be satisfied in the software.

  1. *Change text of email so that a user who ALREADY HAS an account First, we know we need to change the text of the email that goes out to users when a collaborator writes in their name without checking to first see if that user is in the database. We have found that many people don't even check - they expect the software to do it for them. From the email, the user can't tell what happened, and so they sign up again.

This is an email from the NRAO Interactive Services.
Please log into the NRAO Interactive Services using the account name and password provided below:
 
 	Account: ChristianFendt
 	Password: ******
 
This email was automatically generated by the NRAO User Database 
software, please do not reply to it; if you have trouble using the 
account name and password provided above to login, send email to 
udb-admin@nrao.edu and we will help you as soon as we can.
  • 2
  • 3

4. Design

  1. Build a view (or something comparable) in the database that includes the following: First Name, Last Name, Username, Default Email Address, VLA/EVLA User, VLBA User, GBT User, ALMA User. The purpose is to have a data structure that can be easily scanned for duplicates or used as the basis for a mailing list.

5. Deployment Checklist

6. Test Plan

6.1 Internal Testing

6.2 Sponsor Testing

6.3 Integration/Regression Tests


Signatures

APPROVED: I acknowledge that my request is fully contained in this MR, and if the Open Sky (or other NIS or PST developers) deliver exactly what I specified, I will be happy.

ACCEPTED: I acknowledge that I have validated the completed code according to the acceptance tests, and I am happy with the results.

Written - - - - -
Checked - - - - -
Approved by Scientific Sponsor - - - - -
Accepted/Delivered by Sponsor - - - - -

Symbols:
  • Use %X% if MR is not complete (will display ALERT!)
  • Use %Y% if MR iscomplete (will display DONE)


Discussion Area

-- DanaBalser - 09 Oct 2008
Topic revision: r5 - 2008-11-03, NicoleRadziwill
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding NRAO Public Wiki? Send feedback