Sprint 1 - Proposed Tasks

Dates: April 23 - May 4

TEAM:

1. Muhammad Javed (Cornell)
2. Mike Conlon (VIVO)
3. Jim Blake (Cornell)
4. Benjamin Gross (Clarivate)
5. Marijane White (OHSU)
6. Tatiana Walther (TIB)
7. Kitio Fofack (UQAM)
8. Ralph O'Flinn (UAB)
9. Don Elsborg( CU Boulder )
10. Christian Hauschke (TIB)

TASK DESCRIPTIONS & DELIVEABLES

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

   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

   
   

   1. We will be testing vivo-ontology-lab pull request. <LINK TO PULL REQUEST>

   2. Is it good to go in production?

   3. Preparing documentation for release

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

   5. DELIVERABLES:

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

      
      

2. Elastic Search 

   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

   
   

   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

   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

   
   

   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)

1. VCARD ontology update (HomeWork)

   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

   
   

   1. Homework: Evaluation, what has been changed, what should be removed, what should be updated, building the VCARD ontology module file (Add/Retract).

   2. Team: Tatiana Walther (TIB), Muhammad Javed (Cornell), Mike Conlon (VIVO)

   3. DELIVERABLES:

   1. A file that contains list of VCARD entities that are used in vivo software but with a second column, specifying if the entity is current, changed or is deprecated (do not exist) in the current VCARD ontology. (current/deprecated/changed).

   2. A file that contains vcard graph that should be removed from vivo.owl

   3. A file that contains vcard graph that should be added in vivo.owl.

   
   

2. 
   

3. Preparation of ontology modules for the candidate ontologies/entities to be deleted. (Homework)

   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

   
   

   1. Homework: Preparing ontology module files for the candidate ontology entites to be deleted from vivo.owl

   2. Once re-organized ontology files are in place, next step is to clean ontologies/entities that do not sit well with VIVO. In this task, we will analyze.

   3. Which one of the ontologies are candidate to be removed.

   4. If removed, pull the graph out and make it available for those who would like to use It (in case).

   5. Team:Muhammad Javed (Cornell), Mike Conlon (VIVO)

   6. DELIVERABLES:

      1. Graph file(s) of the candidate ontology modules to be removed.                                             

         1. Updated vivo.owl file.

         2. Updated ontologies.owl file
            

   
   

4. Multi-Language Support

     Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   
   
   

   1. Implement this feature on Capability map as a proof of concept of this issue. A user should be able to view the capability map in the language selected switching languages should change the language in which the map is displayed. The scope include making modifications at all levels of the application including templates, Javascripts, Java code, SPARQL queries and Ontology.

   2. Team:Kitio Fofack (UQAM), Christian Hauschke (TIB)

   3. DELIVERABLES: