Week 7 is mainly about resolving the existing bugs and issues within our newly added functions. After the discussion with my mentor, we are specifically looking for 3 improvements to our current owl search:<\/p>\n
1. Currently, in the search result the user would get a list of urls of the owls or the entities after keyword search. But we can also generate\u00a0some important metadata that can be provided to the user such as it’s type, label and name. We aim to provide user with\u00a0a detail page to each result by adding a button like “See details”\/”Detail info”.<\/p>\n
2. Similar to many other search tools, our owl search api is also facing\u00a0keyword stemming problem. For example, if we want to search for an owl related to woods, but incorrectly typed in “wooden” or “woody”, no result would be returned since our api is doing absolute keyword matching. Here we aim to take advantage of\u00a0some NLP technology to enable query expansion for the user. Currently I’m aiming at giving user alternative keyword suggestions when no result is returned.<\/p>\n
3. We are expecting a smooth merge of the codes newly added to the annotator. I and Katie would need to sit down next week to resolve potential conflicts and catch up on other stuff too.<\/p>\n","protected":false},"excerpt":{"rendered":"
Week 7 is mainly about resolving the existing bugs and issues within our newly added functions. After the discussion with my mentor, we are specifically looking for 3 improvements to our current owl search: 1. Currently, in the search result the user would get a list of urls of the Continue reading Week 7 \u2013 Debug and Improvements<\/span>