-
- The Enterprise Search is an exciting activity for us, information architects. I realize that this subject (keyword: SEO) as part of my projects gets a now increasingly important role. And I'm looking forward to exactly these challenges. Some time ago I was involved in a classic "search & findability" project from which I could take some important lessons for future projects.
- as the project develops
We specified the requirements for the search in connection with the following methods / deliverables in a specification:
Concept Model
wireframes (start search, search results, contribution, ...)
use cases
Taxonomy
Meta Schema
data model
- learning
- - Choosing the right communication is very critical to project success: Since we were dealing here with the classical "iceberg" principle (ie customer wants, " implementation of a search field with all kinds of search qualities "), it was of paramount importance, that we the customers everything behind it, the decisive factors for the later success of the project have had. I decided to create a concept model, which communicates in a simple, abstract and narrative way. However, this need not be in every project the appropriate communication method.
-
- User Requirements: The tend to go beyond the project scope if they are fully taken into account in a single project. It is therefore advisable to separate them into functional and future requirements. - - Search strategy: Since search should generally run through a long-term search optimization, it makes much sense to develop a strategy for this model and this into account in the project versions or iterative project processes.
- I am engaged just a deeper SEO issue and will therefore soon tie again from this point at ...
-
interests me: What do you are connecting with the topic of Enterprise Search?