...

1. TAMU Scholars Demo

   Texas A&M University will be demonstrating work that has been completed on their replacement for the VIVO user interface front end (TAMU Scholars). This replacement front end is based on Solr, Spring Data, and Angular Universal. The basic goals of this front end are:
   
   

   1. Align the technology stack as much as possible with the existing VIVO stack to assist with ease of implementation by others if they choose especially smaller libraries.
      Read only UI. 

   2. NO updating back to the triple store.

   3. 100% Search Engine Optimization. IE: A person / crawler does not need JavaScript enabled for page rendering. Server side, and Client side rendering if needed. 
      
      

   TAMU Scholars follows much of the same ideas of the VIVO Scholars Task Force but with a slightly different technology stack.  (GitHub Repo)
   
   
   TAMU Scholars Link
   Spring Data Solr API Link

Tickets

1. Status of In-Review tickets

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=14416 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

2. Received

   Expand

   Expand Jira server DuraSpace JIRA jqlQuery filter=14802 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1666 (re-)Raises interest in reconsidering first-time, every-time, tdbconfig design Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1665 Should be low-hanging Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1663 Where does this stand? What is needed to add more person identifiers to VIVO? Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1644 Mike Conlon : thoughts on where this stands?

   
   

3. Bugs (1.11)

   
   

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=14702 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

...