Google Search Appliance Deployment Governance and Operational Models - Manual (Page 15)

15
A primary goal of indexing application content on the GSA should be to increase user productivity with
that application. When
thinking about use cases or end user workflow, identify areas where the GSA
could simplify the process.
For example, in an application where documents can be edited, in addition to displaying the document in
search results, also include a link to the edit mode of the document, so if users want to edit content, they
can be taken
directly to the edit mode instead of having to click through an intermediate step. Any
optimization or simplification of user processes provided by the GSA will be a benefit.
Ongoing on-boarding and maintenance process
The GSA search solution will continue to evolve as your business evolves and more content is created
across the enterprise. An organization should be prepared for handling future requests for on-boarding
content onto the GSA after the first or initial deployment phases. The first deployment will teach you a lot
and will continue to serve as a framework for adding to or adjusting the solution going forward.
An elaborate process is not necessary, but we recommend having some template of a search
specification available that can be used to guide the design and implementation of the content integration.
The specification
document should contain functional and technical information about the integration.
Without some guiding document, the scope of the implementation may become unmanageable or
requirements may get lost and end up not implemented.
Google recommends the process phases described in the following sections:
1. Initial content analysis
2. Development/Configuration
3. Testing and roll-out
Please take note that the recommended process doesn’t take into account resourcing and project
management tasks that should be considered when taking up such an effort.