Skip to content

Mapping full text search results onto scanned documents

While adding full text search to Gawati we also chose to implement highlighting search results using an overlay for scanned documents. This also works for historic documents that have not been created with digital tools to begin with and independent of the arrangement of fonts and content areas. You may have already come across this feature on Google Books.

In the example shown below, we searched for the word "school" within a document and consequently all of the search results in the main text and additional notes were highlighted. This example was chosen as it is a document that in addition to the main text body, also has additional notes of alternate spacing at its side:

Highlighting fulltext search results in document


We will also soon be publishing the first version of Gawati that includes components for editing library content. This large single step change will include user management, authorisation and other additional features.

Custom search filters

Customizable search filters, a feature we have been looking forward to is being introduced.
As it's very flexible and easy to use (like building blocks in a construction game) but hard to explain in words (like what you can do with building blocks in a construction game), Gawati lead developer Ashok volunteered to put together a video, demonstrating its use:



Why you will want to use Gawati

Open Source end-to-end:
- Uses Open Standards
- Open Source platform developed on top of Open Source components
- Developed live on Github, you have access to the source code and a chance to be part of the community


Convergence of Legal and Technological best practices:
- Based on standardised XML format in FRBR structure
- Akoma Ntoso XML legal document standard
- Built with Legal and Legislative Data in mind


Flexible Deployment:
- Multiple Formats, supports wrapping content in XML metadata
- Modular, flexible architecture; use what you like
- Customizable publication workflows for both internal processing and for web publication requirements

Frontend Engine upgrade

Throughout the previous development steps, we had concentrated on backend technology. As part of this, we have defined a document store, as well as refined metadata retrieval and management.

We have also implemented a simple frontend for the technology to validate and demonstrate its operation. Subsequently, we laid the foundation for a highly interactive and performant fronted user interface.

I would like to introduce you to Gawati Portal v2, which was deployed to our demo server earlier this week. You can find it in the link list in the right hand menu of this page.

Portal v2 is implementing the AJAX approach and will allow for client side resources to interact with Gawati to reduce the dependence on the connection to the server side infrastructure.

This approach also allows for much more flexibility implementing features that will make delivering the information users are looking for much more practical and easy.

This initial version of the Portal V2 based user interface is not much more than a reimplementation of the v1 interface on the new technology.

Over the next couple of weeks, you will find more visible, and newer features added that make use of these efforts. Even more, the benefits will shine on the side of data administration and contribution.

More on that though in a later post.

For now, we are proud to showcase our client side of the Gawati engine.