...
Faceted browsing using Solr. Facets on the right side of the page. Clicking on entity type links (e.g. Person) on front page leads to search results with facets visible. Facets seem to include both high level class groups as well as options such as department, affiliations, roles, keywords for skills, etc. (not being fluent in Italian, I’m guessing)
Tabs on profile page also include ability to search the properties/values list as well as order by ascending or descending mode. Pagination is also included under the property/value list. (In VIVO speak, these are the property group tabs, and for an individual property, you can search, sort, and page through results).
Publications example shows ability to further filter publications list (and all entities).
When searching liver, why is the first result at the top? VIVO’s AllText field (where all keywords from different properties are added) brings this person back but if you click on a link under the person result, the system shows the result executed across all the entities related to the person, showing that this person has many publications.
...
Andrew: Other implementations of faceted browsing.
Cineca: Code Code is from scratch also for faceted interface. For the interface, based on Clarivate’s faceted browsingAll the theme of our VIVO starts from Clarivate Responsive demo theme.
Andrew: Internationalization.
...
Cineca: On version 1.9.2. We use blazegraph and some problem with this kind of back-end. With pull request, we fixed this problem and can move to a newer version. Use BlazeGraph with Jena but not MySQL (instead RDF native database). Load with Pentaho because don’t use editing part of VIVO because have CRIS system where publications (DSpace), and others (resource module). CRIS for loading data and then push into VIVO using our ETL based on Kettle? (please correctPentaho Data Integration (also known as Kettle) .
Huda: Interface features for faceted browsing and search through properties are great. Search relevance is a more involved issue so as long we as keep that configurable/testable would be good (so each installation can define what relevance means to them and how to test it). With respect to code, would need to review but if it is extending the code within VIVO itself, seems like a good candidate to review.
...