Chrome Extension for LinkedIn

Chrome Extension for LinkedIn The Chrome extension should link the following three platforms: - Google Chrome browser; - Webserver with MySQL database; - LinkedIn. -------------------------------------------------- The Chrome extension should do four simple things: 1. A button visible next to the address bar. 2. A user browses through LinkedIn profiles, and once on the profile, clicks on the button. 3. The profile is saved on the server (in the MySQL database). 4. Next time a user browses the saved profile, a notification appears on the button. -------------------------------------------------- DETAILS: 1. The standard icon as any other extension on Chrome. See for example “Go to IMDb” extension. 2. Once a user clicks on the button, a small pop-up appears with a list of categories (and the default category selected) and a “Save” button. Once the profile is saved, a green “yes” notification appears on the button (see point 4 below for details). After the page is saved, no other page should be opened, and no reload of the profile should happened. 3. The extension should extract specific information (as per [login to view URL]) and put them in the following columns: (a) first name; (b) last name; (c) country; (d) headline; (e) current company; (f) position (title) at current company; (g) an url to the profile (either public or “open” – depending on whether a user saved the profile while on the public profile or not). And also: (h) date of saved profile; (i) name of a user who saved a profile; (j) category. 4. Please check the extension “Go to IMDb” to see its behaviour. Whenever the extension is doing a search, moving dots appear. Once the search is completed, an appropriate notification appears. Similarly, whenever a user is on the LinkedIn profile, the extension would perform a search and alter user of this action (so that the user knows that something is happening, and the user has to wait). If the profile is saved in the database, a green “yes” flag should appear. If the profile isn't saved, a red “no” flag should appear. If there's an error with saving, connecting to the database, etc., an appropriate notification should also appear (for example, a red “exclamation mark”.) -------------------------------------------------- SETTINGS The settings page should be accessed both in the Chrome extension settings, as well as when a user right clicks on the button, a standard menu appears with a “Settings” option to select. A. Because the extension accesses the database, it has to have a simple settings page, where a user can put database details (name, host, username, password). B. Also, because of the column (i), it also needs to have a field to write a user name. IMPORTANT: Note that this extension will be assessed in real-time by a number of people. C. Also, as per column (j), there must be section in the settings, where a user can see the existing categories, modify them, delete, add new, and select the default category. Note that these categories have to be saved on the server in the database, so there are shared across all the users using the extension. Those categories have to been in real time, so that if one user changes a category, other user can have the update. However, unlike categories, the default category is specified to the specific user. It can be simply associated in the extension settings in the user's brower. -------------------------------------------------- VIEWER When a user right clicks on the button, a standard menu appears with a “Viewer” option to select. A simple page where a user can view the existing database in a table format, and save it to an Excel file on hard drive. -------------------------------------------------- IMPORTANT: Once the project is finished and we're satisfied, the extension will be released as an open source under our lead. The author of the software will be acknowledged as per common convention.