Date

Call-in Information

Time: 11:00 am, Eastern Time (New York, GMT-04:00)

To join the online meeting:

Slack

Development Process

Attendees

(star) Indicating note-taker

  1.  Ralph O'Flinn

  2. Jim Blake

  3. Huda Khan (star)

  4. Tim Worrall 

  5. Aaron Collier 
  6. Don Elsborg 
  7. Kitio Fofack 
  8. Michael J. Giarlo 
  9. Qazi Asim Ijaz Ahmad 
  10. Benjamin Gross 

Agenda

  1. Mailing list queries

  2. Sept sprint planning

  3. Tickets In-Review

    type key summary assignee reporter priority status resolution created updated due

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

  4. Improving Accessibility
  5. Modularizing VIVO
    1. Search index
    2. Triplestore
    3. Frontend UI
  6. Ingest tooling
    1. https://github.com/vivo-project/VIVO-Harvester
    2. https://github.com/vivo-community/VIVOPhotoDataGenerator
    3. OpenHarvester
    4. https://github.com/alexgarciac/share2vivo-cli
    5. https://github.com/mconlon17/vivo-pump
    6. https://github.com/wcmc-its/ReCiter
    7. https://github.com/usc-isi-i2/Web-Karma
    8. https://github.com/gwu-libraries/orcid2vivo
  7. ...

Notes

Draft notes in Google-Doc

  • Mailing list queries

  • September Sprint planning

    • Only shows 3 participants currently, but know there should be more.  Please look at the proposed tasks wiki page and put your name down on the list.

      • Solr, ElasticSearch, Blacklight

      • Capability map

      • Abox/Tbox rdf loading (clarification)

    • If you don’t have access to the wiki or you don’t want to edit the wiki yourself, please let Ralph know.

    • Questions?

      • Quiet due to heat and cold based on wherever you are

  • Tickets in review

    • Multiple issues regarding multi-language support

      • Kitio: work in tickets is done but one last one has to be completed in order to be integrated into feature in capability map

        • Graham said the way things are done would have issues with existing systems (please correct if I get this wrong) - with no data in the system, people would not see what they see right now

        • Perhaps there are tickets we can commit now (some of the issues which are independent)

    • Ralph: Was multi-language support discussed in ontology group?

      • Kitio: Internationalization task force?

      • Ralph: yes

      • Kitio: Tried to do this work in the capability map to see what would come out as challenges, which resulted in the creation of these tasks

  • Accessibility compliance

    • Looking at in general across the board

    • Looking at Wilma and other templates: some obvious places where it needs work

    • Ralph plans on working on it

    • Ralph: Anyone else interested in working on accessibility issues?

      • To see if people are interested in general working on accessibility and then would generate a list of issues and then assign those issues

      • If people have had experience in this area, it would be helpful to get their feedback

      • Tim: Some accessibility issues will take substantial amount of time to correct

        • E.g. doing all the navigation using the keyboard

        • Given amount of pages and time, and given that there is the product evolution task force and other discussions regarding reworking the front-end, how much does it make sense to commit time to this if the current front-end is going away in the near future?

        • Ralph: Doesn’t seem like it WILL go away in the near future.  Haven’t heard anything about stopping on-going work in VIVO core.  People already use it and we continue to support it, so don’t see any reasons to stop working on it at this point

        • Kitio: Had concerns too with working on the internationalization task force.  Templates: lots of work to change that. Moving away from Freemarker does not seem to be something on the short-term and long-term roadmap.  Still don’t have anyone with enough interest to put work effort to move away from Freemarker templates. Time being, decided to move on and work on internationalization templates, but feel confident they are not going anywhere.

        • Tim: Not presenting myself as proponent of eliminating Freemarker. Seems there are people who want to either move away from it or substantially reduce it.

        • Ralph: Alternative and not replacement.  Many people out there already invested in Freemarker and customizations.  More about presenting alternative or way to get something up and running.

          • Continue to work on bootstrap

          • Keep publishing updates

          • Will incorporate work into Wilma  as well

  • Decoupling architecture

    • Mike submitted a JIRA issue that puts forward components that we can explore decoupling

    • Thoughts and comments?

      • Jim: Huge task represented by a single JIRA issue.  What is intended?

        • Code is in place which enables triple store is a plug-in module and people have experimented with different triple stores.

        • Search indexer is also a module

        • Drawing a clean line between the interface and the rest of the code would be challenging

        • Should we be thinking beyond actual code and if Mike has more in mind a functional modularization (e.g. you have a search engine and here is how you would set it up)

        • Ralph: Could you go to the issue and leave a comment with info about what the current architecture provides with respect to plugin info (i.e. documentation about what we have and where we can go from there)

        • Don: Important to couple the search engine/indexer with the sprint tasks and richer documents

  • Don: any work on working with an external Solr?

    • Ralph: Later versions of Solr in their own container and not within Tomcat.  Has been looking at different versions

    • Huda: Has been experimenting with setting up a Solr 7 instance and what it would take to get that to work.  Got past the smoke tests but Solr4J and Solr 7 have differences so need to see how to handle that.

      • Jim: having an external Solr that is not within the same VIVO tomcat has already been done (i.e. same Solr version as in VIVO)

  • Ingest tooling

    • VIVO harvester.  Wanted to do it in 1.10 release but couldn’t get a tester for it.  Where does harvester stand currently?

      • Don: C.U. Boulder is a user of harvester and have it working against 1.9.3.

      • Ralph: Have you tested it with current version?

      • Don: Too much effort getting it to 1.9.3 so shifted to other work right now.  Recalls that perhaps John Fereira had it working with 1.10. There is a 1.10 rc-1?

      • Ralph: Yes, but Ralph and Andrew weren’t able to compile it and couldn’t get someone to test it

      • Benjamin: John has maintained it in the past and seems to be the main person working on it

      • Don: Weill on call? May want to check with sarbajit?

      • Benjamin: Think he wrote something different (jena connect?)

      • Ralph: Hopefully can get something for 1.10 release and get it validated and get install process documented to the point where we can compile it and get it published.

    • Photo generator

      • Ralph loves it and uses it every week.  

    • Don: Some place on the wiki to show what institutions are using what forms of ingest?

      • Ralph: Not that we know.  

      • Huda: Good suggestion though.  Useful to know what’s going on

      • Ralph: Page on wiki to keep track of this? Symplectic users use their connector.

  • TDB vs. SDB

    • Don: With TDB, can use more optionals and move away from large constructs (specifically for custom list view pages)

    • Ralph: Perhaps in sprint, one of the issues is to move from SDB to TDB.  On wiki, might be useful to add information about purpose and questions to answer.  

    • Huda: JIRA issue with comments regarding this issue

    • Ralph: Would need to link related JIRA issues to the sprint topics

  • Ralph: Got back from Symplectic conference. New VIVO installation PoCs.


Previous Actions

Actions

  • ...


  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.