...

1. Sprint update (June 17th - 28th)

   1. External Search

      1. Merge 'sprint-search' (vivo, vitro) into 'develop'?

   2. Enable connection of decoupled, read-only "profiles" user interface to VIVO

   3. Define "shapes" of VIVO entities

   4. Dockerize appropriate components

2. Tickets in-review
   1. Needing one more review

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1687

   2. 
      

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

      
      

3. Working towards the VIVO 1.11.0 release
   1. Landing Design - External Search
   2. Other tickets we want to include?
      1. Docker work:

         1. Jira
            server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1679

             - Don Elsborg to review?

         2. Jira
            server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1680

             - Don Elsborg to review?

         3. Jira
            server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1682

             - Ralph O'Flinn to review? - Now in https://github.com/vivo-community/vivo-docker2

      2. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1670

          - mis-rebased

      3. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1415

          - appears to have an unrelated commit in pull-request

      4. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1692

   3. Release manager?

Tickets

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

   
   

...