Devam Ediyor

475124 Need Sharepoint site for Ad Submission

Need Sharepoint site for Ad Submission

-------------------------

** Overview **

-------------------------

Small ad agency needs a Sharepoint 2010 portal to keep track of ads. Clients will self-register and then log into the Sharepoint site and submit components of an ad (i.e. Text and/or Graphics). The Ad Agency will take these components and assemble the ad. The Ad Agency will upload the completed Ad to the Sharepoint Site. The client is notified (via automated email) that the Ad is available for proofreading. The client logs back into the site to view the Ad, and then approves it or makes additional changes.

-------------------------

** Roles Defined in the Scope **

-------------------------

"Client" refers to the clients of the Ad Agency. (i.e. the users who self-register, then log in and submit ads and changes to ads). When Clients log in, they can only see records that THEY submitted.

"Back-End User" refers to a staff member of the Ad Agency. When a Staff Member logs in, he/she can see ALL records.

"Admin" refers to a 'Super User' account with the same priviledges as a Back-End User, PLUS the ability to perform all Administrative tasks.

-------------------------

- This application MUST be written in [url removed, login to view] using C#

- No PHP, No ColdFusion, No ASP, No VB, etc.

- This is STRICTLY an [url removed, login to view] / C# / SharePoint / MS SQL Project.

- You must use Visual Studio

- You must use .NET Framework 4

- You must write clean, well-formed code

- You must include comments within your code

- All final source code must be turned over

- You must allow 3 days for me to test the application

- You must be available for support for 3 months after the project is signed off

-------------------------

I will provide domain name and Sharepoint server login info. It will be a Windows 2008 Server with Sharepoint 2010 and MS SQL 2008.

Here are the details:

-------------------------

** Login Page **

-------------------------

Client goes to website and sees login page.

Login page needs to provide the following functionality:

- Client enters their email address and password to log in

- After 5 unsuccessful login attempts, the account is locked and only admin can unlock OR the client can request to have a password reset link emailed to them. (This email can ONLY be sent to the email address associated with that account (i.e. the client's login))

- Clients can click 'forgot password' to have password reset link emailed to them. (This email can ONLY be sent to the email address associated with that account (i.e. the client's login))

- Password must be minimum of 6 characters

- Client can click 'register now' if he/she is a new user (see below for registration details)

A client will be logging into this website to SUBMIT an ad, to CANCEL an ad, to MODIFY an ad, to CHECK THE STATUS of an ad, or to VIEW a proof of an ad.

-------------------------

** Home Page **

-------------------------

After client logs in, the client can do the following:

1. View previously-uploaded files and/or ads

2. Submit a New Ad

3. Change an Existing Ad *

4. Cancel an Existing Ad *

5. View a Proof

6. Check the Status of a Submitted Ad or Change to an Ad

* Note: An Ad cannot be Modified or Canceled once the Status has been changed to 'Approved'

Each of these 6 options are described below:

----------

1. View previously-uploaded files and/or ads:

At the top of the home page the client will see a Sharepoint data grid.

The default view of the grid shows every ad submission they have made in the previous 90 days.

The client can specify a different date range to display more or less records.

The data grid will have the following columns:

- ID :: Each time the client logs in and submits the form, a record is added to the database. This is the unique integer ID assigned to that session. (An Integer, Auto-assigned by Sharepoint app). The client may log into the site one day and submit part of an ad. Then the client may log in a few days later and submit the rest of the ad (the SAME ad). Since the client logged in twice, they will see two rows in the grid (one for each form submission)

- Date :: Date the submission was made (Auto-filled by Sharepoint app. Defaults to the date/time that the client pressed the 'Submit' button. Cannot be modified)

- Client Name :: The name of the client who submitted the ad (i.e. the person who is logged in) (example: "Charlotte Smith")

- Student Name(s) :: The name of the student. (This info is captured when the Client registers for the first time)

- Payment :: Indicates whether or not the ad has been paid for. (This field can only be modified by a Back-Office User or an Admin. Default value is Blank)

- Ad :: Automatically set to 'Yes' if 'Ad Text' text box was not empty when the client pressed the 'Submit' button. Or, if the form is submitted and the client did NOT enter data into the 'Ad Text' text box, then the value is set to 'No'

- Uploads :: A list of files uploaded by the client during their login session. Each file name should be a link so that the client can click on it to view and/or download the file directly from my server.

- Status :: When the client submits an ad, the Status is automatically set to 'Submitted'. Only a Back-Office User (Staff Member) or Admin can change the status of an ad.

- Preview Text :: If the client entered any text into the 'Ad Text' field and submitted the form, this column will show the first 45 characters entered by the client

- Proof :: If a proof is available for the client to review, the file name appears in this column (as a hyperlink). Here's some more informaton about 'Proofs': As explained earlier, the client uses this website to submit content for ads. The client can submit text and/or images. The agency (back-end user) will take all of the parts submitted by the client, and assemble them into a final ad. A 'Proof' of the ad is simply a screen shot of the completed ad, with all of the components in place. When the agency (back-end user) has assembled an ad, he/she takes a screen shot and posts it back onto the Sharepoint site. (Details of this process are described below). When the Back-End User uploads a proof, the name of that file ([url removed, login to view] for example) shows up in this column as a hyperlink. Clicking on the link allows the client to view the .png file in their browser. All screen shot files are associated with a specific ID. Now the client can log back in and view a proof of their ad.

- User Notes :: This column displays any notes entered by the Client (when they submitted the form)

- Admin Notes :: This column displays any notes entered by a Back-End User or Admin. This field CANNOT be modified by a regular User.

Additional Criteria for Data Grid:

- Use Ajax for fast response

- User must be able to sort any column in the grid by clicking on a header name

- Initial view of data grid is sorted by ID in ascending order.

----------

2. Submit a New Ad

Below the data grid are a series of graphic images / buttons.

The first button is called "Submit a New Ad"

Clicking this will bring the client to a form, which asks for the following info:

- Your Name :: Pre-filled with Client Name

- Student Name :: [This is a drop-down list] The data from this list is populated from the Student Name(s) the client entered when he/she first registered. In addition, the drop-down should also include the word 'OTHER'. Selecting 'OTHER' will cause an extra text box to appear, where he/she can manually type in the name of the student(s)

- Ad Size :: This is a series of RADIO buttons:

( ) Love Note (text only) *

( ) Quarter Page ad

( ) Half Page ad

( ) Full Page ad

( ) Full Page ad (full color)

( ) Inside Front Cover (full color)

( ) Inside Back Cover (full color)

When the user clicks on any of the Radio buttons, some text appears off to the right of this list. The text contains info regarding the ad they selected: ad sizes, specs, etc.

- Ad Text :: This is a multi-line text box which allows the user to enter all of the text that should appear in the ad

- Image/Photo Upload #1

- Image/Photo Upload #2

- Image/Photo Upload #3 :: Users can upload up to 3 files.

* NOTE: If the user selects the 'Love Note' radio button, disable the three Upload buttons. (Love Notes cannot contain images)

----------

3. Change an Existing Ad *

As described above, when the client logs in, the home page displays all submissions the client made in the last 90 days. The client should be able to click on any record and view the details of that submission.

The client (or Back-End User or Admin) is able to edit the details of a record, if Status equals one of the following:

- Submitted: New

- Submitted: Changes

- In Progress

- Incomplete: Waiting on Text

- Incomplete: Waiting on Image(s)

- On Hold

- Waiting for Client Approval

- Declined with Changes

The client will not be allowed to make changes to any record whose status equals one of the following:

- Canceled by Client

- Canceled by Staff

- Approved with Changes

- Approved

If the user edits a record:

- The record ID stays the same

- The 'date' field is updated with the current date/time stamp

- The 'status' changes to 'Submitted: Changes'

- An email is sent to the Back-End User to let him/her know that a change has been made. The email should contain the old (previous) Ad Text AS WELL AS the new Ad Text

----------

4. Cancel an Existing Ad *

A client (or Back-End User or Admin) may cancel an ad submission if the status equals one of the following:

- Submitted: New

- Submitted: Changes

- In Progress

- Incomplete: Waiting on Text

- Incomplete: Waiting on Image(s)

- On Hold

- Waiting for Client Approval

- Declined with Changes

The client will not be allowed to CANCEL any record whose status equals one of the following:

- Canceled by Client

- Canceled by Staff

- Approved with Changes

- Approved

If the user cancels a record:

- The record ID stays the same

- The 'date' field is updated with the current date/time stamp

- The 'status' changes to 'Canceled'

- An email is sent to the Back-End User to let him/her know that a record has been canceled. The email should contain the details of the record, before it was canceled.

----------

5. View a Proof

A client may receive an email notification to let him/her know that a proof of their ad is available to view online. The client logs back into the site, and as described above, the home page features a grid which automatically shows evert submission the client made in the last 90 days, sorted by date. If a proof is available for the client to view, the entire row (in the data grid) is highlighted in green. (or the text in that row appears in green). In the 'Proof' column, the client will see a hyperlink.

Clicking on the hyperlink will allow the client to view the PNG file.

Directly under the PNG file are four buttons:

[APPROVED AS-IS] :: If the client clicks this button, the site will prompt the client "Click 'OK' to approve this ad as-is [OK] [Cancel]". If client clicks 'Cancel', the prompt disappears and no changes are made. If client clicks 'OK', then do three things:

1. Change Status to 'Approved'

2. Change Date to current time/date

3. Redirect client to Home page and display a message: "Thank You. Your ad has been approved!"

[MAKE A QUICK CHANGE AND THEN APPROVE] :: If the client clicks this button, the site will prompt the client "Click 'OK' to approve this ad with changes. After clicking 'OK' you will be asked to describe your changes. [OK] [Cancel]". If client clicks 'Cancel', the prompt disappears and no changes are made. If client clicks 'OK', then do four things:

1. Without redirecting the user to another page, make a multi-line text box appear, where the client can describe the changes that need to be made to the Ad. Also provide one Browse/Upload control in case the client wants to submit a new file.

2. Change Status to 'Approved with Changes'

3. Change Date to current time/date

4. Redirect client to Home page and display a message: "Thank You. We will make final revisions to your ad"

[MAKE CHANGES AND SHOW ME A NEW PROOF] :: If the client clicks this button, then prompt the client "Click 'OK' to decline this ad. After clicking 'OK' you will be asked to describe your changes. [OK] [Cancel]". If the client clicks 'Cancel', the prompt disappears and nothing happens. If the client clicks 'OK', then do the following:

1. Without redirecting the user to another page, make a multi-line text box appear, where the client can describe the changes that need to be made to the Ad. Also provide one Browse/Upload control in case the client wants to submit a new file.

2. Change Status to 'Declined with Changes'

3. Change Date to current time/date

4. Redirect client to Home page and display a message: "Thank You. We will review your changes and notify you when a new proof is ready"

[CANCEL THIS AD] :: If the client clicks this button, then prompt the client "Are you sure you want to Cancel this ad? [Yes, Cancel This Ad] [No, Do Not Cancel This Ad]". If the client clicks 'No', the prompt disappears and nothing happens. If the client clicks 'Yes', then do the following:

1. Change Status to 'Canceled'

2. Change Date to current time/date

3. Redirect client to Home page and display a message: "Thank You. Your submission has been canceled"

----------

6. Check the Status of a Submitted Ad or Change to an Ad

The client simply logs in and the status of each submission will be available on the Home page.

-------------------------

** Back-Office User Site **

-------------------------

The Agency (Back-office User) logs into this portion of the site to:

- View ALL submissions in a data grid. It can be the same exact data grid that the client sees when he/she logs in, except this grid shows ALL submissions in the last 90 days. (Again, 90 days is the default view but the user should be able to change this date range)

- Update the Status of any record.

'Status' is a drop-down and contains the following choices:

- Submitted: New

- Submitted: Changes

- In Progress

- Canceled by Client

- Canceled by Staff

- Incomplete: Waiting on Text

- Incomplete: Waiting on Image(s)

- On Hold

- Waiting for Client Approval

- Declined with Changes

- Approved

- Add NOTES to any record.

- Upload a Proof for the client's approval.

How the Back-End User Uploads a Proof:

1. Back-End User logs into site and sees data grid

2. Back-End User clicks on the 'ID' to view the details of that record

3. In the detail view, the Back-End User will see a link (or button) that says 'Upload Proof'

4. Back-End User clicks that button, browses their computer, and uploads the PNG file

5. Website now prompts User 'Notify Client That a New Proof Is Available' [Yes] [No]

6. If Back-End User clicks [Yes], and email is sent to the client. Email will have a specific 'From Address', 'Subject' and 'Body' (to come later). In the body of the email, the client will be able to click on a link that brings him/her to the png file on my server. (User will first be prompted to log in)

7. If Back-End User clicks [No], then the process ends

8. Status of the record changes to 'Waiting for Client Approval'

-------------------------

** New User Registration Site **

-------------------------

New User Registration Form must include the following fields:

- Your Name

- Your Email Address

- Choose a Password

- Re-enter Password

- Phone Number

- Student 1 First Name

- Student 1 Last Name

- Student 2 First Name

- Student 2 Last Name

- Student 3 First Name

- Student 3 Last Name

[Submit]

- When a user registers, he/she is automatically assigned the role of 'Client'. (Note: An admin can log in and change the user's role to 'Back-End User' or 'Admin' if necessary.

- User table should also keep track of user's "Last Login Date/Time"

-------------------------

** Admin Site **

-------------------------

The Admin can do anything a Back-End User can do, PLUS the following:

- Unlock a user account

- Lock a user account

- Edit a user account (Name, Email, Password, Status, etc)

- Change the value stored in the 'Paid' field

- Change the role of a user (change between Client, Back-End User or Admin)

Additional notes:

- An admin cannot change his own status (i.e. set to 'Inactive')

- An admin cannot change his own rol (i.e. change from 'Admin' to something less)

- An admin CAN change his own password

- In case the last remaining admin loses/forgets his password, he/she can retrieve it from the login screen (the same way a Client can retrieve their password)

- Passwords cannot be retrieved or reset for user accounts marked as 'Inactive'

-------------------------

- This application MUST be written in [url removed, login to view] using C#

- No PHP, No ColdFusion, No ASP, No VB, etc.

- This is STRICTLY an [url removed, login to view] / C# / SharePoint / MS SQL Project.

- You must use Visual Studio

- You must use .NET Framework 4

- You must write clean, well-formed code

- You must include comments within your code

- All final source code must be turned over

- You must allow 3 days for me to test the application

- You must be available for support for 3 months after the project is signed off

-------------------------

SERIOUS BIDDERS ONLY !!!

Beceriler: .NET, Her şey Kabul, C# Programlama, Sharepoint

Daha fazlasını görün: write three wants, write name photo website, write name love, write name body, hold domain name, place ads online, want windows back, waiting staff, use case include example, use case components, top radio ads, top programming, table top range, super source, sorted data set, site write anything, site graphics, sharp choices, sharepoint box, series application, self programming computer, self programming, scope programming, scope application form, person one photo

İşveren Hakkında:
( 1 değerlendirme ) Fort Lauderdale, United States

Proje NO: #2221029