VIVO Scholars task force update: Started with TAMU middleware layer to see if we can add GraphQL endpoint to
7 Solr cores with separate set of queries possible for each core
Publications data in person Solr core is there for faceting and querying but does not reflect all of the data in the documents (which has all the publication info)
When looking at the person search results, you get publications information back when you want (e.g. user clicks on a publication or asks for publication info, request is sent to retrieve that info and render that info)
Ability to have server to do bundling of comprehensive object
If you want to power the front-end, you would want more publications data
Flexibility with GraphQL: can choose what you want
TAMU use case driving person/documents solr core distinction
GraphQL would be doing that in one request i.e. getting as much info as much as possible
Resolver to get data in shape
Define mappers and converters for GraphQL
Front-end in this case is completely run by GraphQL endpoint
Able to reflect back on what is in the Solr index and create GraphQL resolvers
Schema outlines structure of data
GraphQL configuration speaks to TAMU middleware which speaks with their Solr
Next steps: build GraphQL structure some more to get full-feature nested objects
Front-end piece: haven’t done much with that yet but do plan on it eventually
From Andrew’s email (copy/pasted)
The local VIVO installation can use TBD or SDB
VS (VIVO Scholar) extracts content from the VIVO triplestore via sparql-queries
The results of those queries go into an index (now Solr, ElasticSearch soon)
In any case, the VS frontend calls the REST API of the VS backend that exposes the indexed content via an API
I have updated the deployed VSTF (VIVO Scholar Task Force)/TAMU configuration to use OpenVIVO person thumbnails and have done some "quick and dirty" styling to make the site more reminiscent ofopenvivo.org.
For those who have not been working on the VSTF/TAMU application, my brief summary of the architecture is:
Updating VS configuration to support the OpenVIVO content was relatively straight-forward. It would be interesting to discuss other features that would be good to expose in VS.
Julia sent out email to community list and posted updates on wiki/mockups. Put some out there and collecting feedback by survey.
Profile page mockups, 3 different approaches
Also working on search page mockups and will put those out there
Also townhall on July 11th: open to everyone and hoping to get thoughts and questions
Take a look and give your thoughts and take the survey
Indicating note-taker
