the infrastructure needed to store thousands more incoming documents annually. Users also needed an interface that contained all the familiar features and functionality of the existing Oracle system. Answering these challenges required General Networks to create an easy-to-navigate folder structure and an equally familiar search experience that allowed users to query with complex metadata. Outlook plugins, the use of Kofax Capture (naming and tagging of documents), and integration with Office 365 all needed to be considered as part of the solution. The First Step The first step in addressing these challenges was configuring the SharePoint document library. All of the organization’s documents were associated with the same business process and user community, allowing for the design of a single library. The library contained a folder hierarchy to store the documents, and was configured with content descriptions and metadata to capture key search terms like “document category” and “project number.” A custom Outlook plugin was added along with Kofax Capture integration for consistent document tagging. Next Customizing the document upload form came next. General Networks created an application for easy and stable deployment that streamlined the upload process. The custom upload form was developed using the Provider-Hosted App model, and the App Web was created using the ASP.NET MVC template. Users simply needed to click a link on the home page to access the custom upload form. The custom form asks for the file, document category, and project number. The pick list is dynamically populated for the document category based on the content of the top-level folders in the document library. The app then uses the project number to query a project information database, retrieving related metadata like the proposal number and award number. Because the app automatically names the file based on the user name and upload timestamp, the risk of duplicate file names is removed. Finally, the document is stored in the appropriate folder based on metadata and current folder volume. Users reported the document upload experiences saved them time and frustration, as managing and balancing the document library became an almost fully-automated task. SharePoint Customized Search Experience Advanced search experience was customized based on the extensive feedback given by users during the environment assessment. The advanced search experience needed to allow users to enter a combination of keywords and metadata queries while giving them the ability to filter results by type and advanced property restrictions. This was accomplished by first configuring the document library columns as managed properties in the search settings. Next, Enterprise and Publishing features within the Site Collection settings were enabled. Then, the search page was created, which contained Search Web Parts. Finally, the XML properties were configured so the appropriate metadata to the property pick list could be added. 12 11 After all the steps were complete and additional user feedback was given, a fully customized search interface was developed. It can expand in functionality as the organization scales in document management complexity. SharePoint Customized Display Results Developing a custom search results display template was the final step in implementing the SharePoint solution. Users felt the out-of- the-box SharePoint search results were too generic and did not readily provide them with the information they needed. The customized display template developed by General Networks had a similar look to the document library, allowing users to quickly filter, sort and click to access documents. Using SharePoint Designer, a Custom Results Control template and Item Display template was developed and then tested by various users.