Front end Website build required, integrating with 3rd party Content Management system via .NET DLL. You will obvioulsy have questions but please send me a proposal with indicative costs and timescales and proposed solution. The site design will follow a standard (Net 5) layout, with â¢ Top banner containing clients logo â¢ Left Hand Menu (see 4.1) â¢ Footer containing T&Cs, contact details etc The navigation menu will appear on the left hand side of all pages, this will contain the following elements: â¢ Home link (back to page described in 4.2) â¢ Browse link (which takes users to the gallery page with a search result containing all items in the database) â¢ Links to the subject, index and advanced searches â¢ Text search (an edit box with a search button / icon) This element queries the index built by external party content manager in the underlying SQL database to return items including all the words typed in the box, except those that appear on the list of excluded words (e.g. THE, AND, OF etc. Excluded terms are listed in a table in the database). â¢ Other arbitrary links to existing content â¢ No data access required as all access will be via a 3rd party DLL written in C# home page will contain the following functional elements â¢ Login area containing e-mail & password boxes â¢ Link to forgotten password page â¢ Link to request password page If the user enters an incorrect password, they will be returned to the home page, but with a message displayed in the login area telling the user they have entered invalid e-mail address or password. If a user is logged in, the only difference is that they have access to the download functionality on the selection page and a range of record types as defined in the Content Manager. The forgotten password page allows the user to enter their e-mail address. This is then checked against the database and if it exists, the password for that account is mailed to the user. If the e-mail address does not exist in the database, the user is informed on the forgotten password page. The request password page should allow the user to enter an e-mail address, desired password and reason for needing such access (in a free text box), their first name, surname, telephone number and department / company. The contents of the form should then be e-mailed to the system administrator and logged in the database so the administrator can âactivateâ the account if they agree to the request. The users login determines whether on not they can download and which item types in Content Manager they can see (for example, there will be an item type called âPeopleâ that because of data protection will only be available to certain users). The subject search page displays the subject categories entered in Content Manager as a tree structure. Users can click on a leaf term to find images associated with that leaf, or on a branch (folder) to find images associated with any leaves in that folder and any leaves in any sub-folders. (NB It would not be unreasonable to assume / or put the constraint on this page that there will be no more than 4 levels in the Subject Hierarchy, in order that the search can be coded efficiently, rather than having to traverse down the tree) The search will only return items allowable by the userâs login. The index search displays all the leaf terms from the subject hierarchy. An alphabet navigation control should be displayed so the user can filter the list of terms by a particular starting letter (just like the index in a book). By default, when the page is first entered, the filter should be set to âAâ if there are more than 200 (or another appropriate number) terms in the list, otherwise all terms should be displayed in columns alphabetically. The user can click on a single term to view images associated with that term (in the gallery page) The search will only return items allowable by the userâs login. The advanced search page a number of âtabsâ allowing the user to search on the fields within particular item types in Content Manager. Which âtabsâ are displayed will depend on the users login. (if the user is not logged in only the default item type will be displayed). The tab will contain a fixed set of fields, determined in the project initiation document. The fields may include Text strings, numbers (as a range), and items selected from a drop down list (which are defined in the database). The user enters / selects values for one or more fields. On pressing search, the set of records containing all values entered should be returned. Wildcards should automatically surround terms entered in free text fields, e.g. if the user enters âflowerâ in the title field, the underlying code would search on â%flower%â to find records with flower anywhere in the title field (this is intended to be a description of functional requirements not a suggestion as to the actual implementation) The gallery page will display the results of a search as a sequence of pages. If a search returns no results, the âgalleryâ page should simply display a message indicating the no matching records have been found. The gallery will display a number of thumbnails (the actual number should be selectable from a drop down list which defaults to 8 (two rows of four thumbnails). Each thumbnail image should have a caption displayed underneath it, which will be drawn from a prescribed field in the database. A selection box (either a simple check box or image that toggles when clicked) should be available by each thumbnail. A navigation area should appear at the top of the page (below the banner) containing: Crumb trail indicating the search a user has performed (e.g. Subject search) and the term(s) that were searched on. The number of results found The current page and the total number of pages Navigation controls to move to the first, last, next and previous pages The number of images currently selected (Ideally a navigator like google so you can move to next and previous as well as jump to a specific page close to one you are on. This is useful if you want to flick back / forward a few pages to review an image you looked at previously.) Clicking on a thumbnail displays the item page for that image. The item page shows the details for a particular record, including: An image A number of data elements (this will be fixed at the time of specification) Links to any related items (this is a feature in Content Manager that allows cataloguers to link records together, for example the next page in a book, or the back of a painting) The list of subjects associated with the record. These should be hyperlinks that perform a search on the selected subject (just like the index page) A link to any video clip, sound file or other file associated with the record. A link to view the higher resolution image for the record (if one exists) Item pages should have static URLs, even if the URL contains more information (i.e. the current search / page etc.) as users frequently bookmark individual items and these links should still work even when the database is updated. (Except of course if the item is deleted) The zoom page should display the larger image for an item along with any copyright statement / credit line. The selection page is just like the gallery, except it shows the selected records instead of a search result. It should be possible to deselect items from the selection page. If a user is logged in, a link to the download page should be displayed. The download page offers the user the choice of resolutions to download (to be defined at specification time) and a text area where they must enter their reason for downloading the images, and a drop down list of categories for the download (e.g. presentation, PR). The list of download categories will be defined in the specification. As a general principle, users will only be able to download images that are copyright cleared (this will be determined by a particular value being set in the items data). When the user clicks download, the system should log in the database which images are being downloaded, by whom and the uses they have selected. Images will be downloaded in a zip file. 1 Configurable Elements The site will be delivered very much âas isâ, but we should be able to change the look and feel relatively easily, i.e. the pages should follow good design principles with layout, fonts colours etc specified in a style sheet. Adding new data fields to the item page / advanced search should be possible given knowledge of ASP.NET. 2 Standards The site should conform to Bobby AAA W3C CSS & XHTML 3 Support & Maintenance There will be no support for the code delivered beyond a 90 day warranty to fix any bugs in the delivered code. Support of the front end would then be entirely the customerâs responsibility. We would retain support obligations for the Content Manager application. 4 Integration with Content Manager Technical information will be provided about the concepts and database to enable a full costing to be provided. 5 Technical Environment The Web and Intranet services are hosted internally on three servers: â¢ Web server (dual processor) 2.8 GHZ Xeon â¢ Intranet server (dual processor) â¢ MS SQL- server. The Web and Intranet servers share the same data source using a MS SQL Server 2000 database. A separate Development server hosts the web, intranet and SQL Server 2000 in a test environment. The Intranet server, SQL- server and Development server sit within the network protected by a firewall. The Web Server lies within the DMZ with one port opened via the firewall to query the SQL- Server. The Web and Intranet server use IIS 5 to serve the sites and ASP pages are used to query the SQL-Web server database. Image data will be stored on a Network Attached Storage Device. The image library application (ASP pages) will be hosted on the Intranet Server with the database stored on the SQL- server. The application will support the existing Internet/Intranet facility provided by the client. The system must host sufficient functionality to enable it to be developed and embedded into the existing web site.