{"id":2310,"date":"2014-06-30T23:39:59","date_gmt":"2014-06-30T23:39:59","guid":{"rendered":"https:\/\/notebooks.dataone.org\/?p=2310"},"modified":"2014-06-30T23:39:59","modified_gmt":"2014-06-30T23:39:59","slug":"week-5-integration-new-feature","status":"publish","type":"post","link":"https:\/\/notebooks.dataone.org\/ontology-search\/week-5-integration-new-feature\/","title":{"rendered":"Week 5 \u2013 Integration & New feature"},"content":{"rendered":"
The past week we successfully resolved the cross domain issue which prevents us from displaying\u00a0the search results into the annotator main page. We also maintained & confirmed\u00a0that the individual facets are now working. (If there’s individual exists within a class or rdf). And I started on our expected feature 2 – ontology recommendation.<\/p>\n
For this coming week I’m expecting to work with Katie getting search results well-displayed meanwhile being able to analysis user&loaded csv data to enable recommendation functions. Currently I’m taking use of the idea from the Morph application on Dataone.org. The use case is that annotator would both analyze user history data and csv data (especially content) and return a recommendation result when the user do a right click on a specific column of the data he\/she had imported.<\/p>\n","protected":false},"excerpt":{"rendered":"
The past week we successfully resolved the cross domain issue which prevents us from displaying\u00a0the search results into the annotator main page. We also maintained & confirmed\u00a0that the individual facets are now working. (If there’s individual exists within a class or rdf). And I started on our expected feature 2 Continue reading Week 5 \u2013 Integration & New feature<\/span>