Context
Release 1.8 of VIVO includes a search indexer that has been substantially re-written. Compared to earlier versions, it is more efficient, easier to understand, easier to configure, and easier to evaluate.
This transition has not reached its logical conclusion, because of the time-pressure of the release. The three flexible components of the indexer are “excluders”, “URI finders”, and “document modifiers”. Of these, only the document modifiers have made the full transition to the new community-friendly style.
Even though incomplete, this increased level of visibility has made it obvious that the current configuration contains errors, redundancies, and omissions. It also brings this question to the forefront: what should the search index contain?
Objectives
To determine what data should be included in the standard distribution of the search index for Vitro. This should recognize that Vitro is ontology-neutral.
To determine what data should be included in the standard distribution of the search index for VIVO. This should be based on usage patterns and the structure of the VIVO ontology. It should recognize the tradeoffs between power and performance.
To develop a style for those configurations that is concise, easy to understand, and resistant to errors.
To make code enhancements that will support that style. This part of the effort should be minor, even trivial. In particular, this should permit easier configuration of the “URI finders”.
To document the configuration process so individual VIVO sites can easily customize VIVO to suit their needs.
To document the changes in content from previous releases.
Deliverables:
A configuration for the search indexer, for use in Vitro.
A configuration for the search indexer, for use in VIVO.
A document or Wiki page that describes to VIVO maintainers how these configurations differ from those of previous releases.
One or more Wiki pages that describe the configuration process.
An acceptance test procedure for the configured search indexer (VIVO). This will be based in Selenium, in the style of the existing VIVO test suites.
Suggested schedule:
Develop charter | 1.5 weeks | 2015-02-06 |
Solicit members and schedule first meeting | 1 week | 2015-02-13 |
Develop action items, assign to team members. | 2 weeks | 2015-02-27 |
Accomplish deliverables, preliminary review | 3 weeks | 2015-03-20 |
Revise deliverables, final review | 2 weeks | 2015-04-03 |
Members
Jim Blake (Cornell University) - task force lead
Layne Johnson (Duraspace) - ex officio
Don Elsborg (University of Colorado, Boulder)
others to be solicited from the VIVO Community
Meeting Times
TBD
Communication Channels
Distribute proposed charter and solicit participation from community via dev-all mailing list
Announce task force creation and progress on the weekly developer/implementation calls.
Create a page in the VIVO wiki (wiki.duraspace.org), with child pages for agenda, notes, and additional information
Agendas and Notes
Solicit agenda items from task force members 3 days before meeting
Prepare agenda and distribute no less than 24 hours before meeting
Use standard meeting agenda and notes format (see VIVO wiki Task Force Agenda Template here for example).
