Page History

...

1. Re-evaluation of 1.10 branch. (Testing) 

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

   
   

   1. Create a new release candidate

   2. We will be testing vivo-ontology-lab pull request. https://github.com/vivo-project/VIVO/pull/63

   3. Is it good to go in production?

   4. Preparing documentation for release

   5. Team: Mike Conlon (VIVO) Muhammad Javed (Cornell) Benjamin Gross (Clarivate) Ralph O'Flinn (UAB)

   6. DELIVERABLES:

   1. Pull request merge in dev (and merge to master??)

      
      

2. Elastic Search 

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1423

   
   

   1. Decompose the task into smaller sections and focus on what can be achieved in two weeks time.

   2. Team: Benjamin Gross (Clarivate), Jim Blake (Cornell), Don Elsborg ( CU Boulder )
   3. DELIVERABLES:

   
   

3. VIVO ontology & Ontologies.owl file update

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

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

   
   

   1. Replacing multiple vivo ontology files with a single one vivo.owl ontology task force group created.

      1. We will test if vivo.owl contains all entities (classes/properties) that exist in current VIVO software.

      2. We will test if ontologies.owl file is complete. All ontologies are mentioned in siteAdmin page. (ontologies.owl)

   2. Team: Muhammad Javed (Cornell), Mike Conlon (VIVO), Marijane White (OHSU)
   3. DELIVERABLES:

   1. A decision that changes are good to go in production or not ready (with comments)

...