Page History

• initially 12-20; in 2 years, 100; ultimately (say, 5 years – hard to say, because if that many universities want to participate, a commercial search engine company will jump in and do it better)
  • if we're talking about the CTSAs as an initial group, who would that be?
    
    • a couple CTSAs plus some of our existing VIVO adopters
    • jon – might want to address the needs of our non-CTSA partners, as well as a small CTSA expansion that would get us 2 more platforms – Iowa and Northwestern
    • jonathan – a need for a CTSA-only network, and a need for an open network
  • then subsequently could offer participation to a larger group of CTSAs
• we are trying to support anyone who will provide VIVO ontology RDF in response to linked open data requests (to be most compelling, the next phase must demonstrate harvesting data from VIVO, Harvard Profiles, SciVal experts, and Iowa's Loki. If promises to do the export happen, Pittsburgh's Digital Vita and Stanford's CAP systems may also be able to provide data; ideally an institution could also participate through linked open data requests to static RDF files in a web-accessible directory)
• will target a range of institutions including government (USDA), commercial (American Psychological Association), international (Melbourne, Griffith, Bournemouth, Eindhoven, ColPos, Memorial University of Newfoundland, etc), small (Scripps) and large (Florida, Colorado, Brown, Nebraska, Duke), and on diverse platforms (Harvard, UCSF, and Minnesota for Profiles, Northwestern for Scival Experts, Iowa for Loki)

We interpret this question as what people will be needed and what will their skills and effort level need to be:

1. an indexing programmer familiar with Java and Hadoop
2. a web developer experienced with Drupal or an alternative open-source content management system with an established infrastructure to support Solr
3. UI designer experienced with developing search interfaces and comfortable working in Drupal (or the chosen platform if different)
4. project manager to make the phase 2 pilot happen, document requirements and projected deliverables, coordinate the rest of the team efforts, and develop the business model for an ongoing service
5. a marketing person to write up public-facing documentation, recruit new organizations, collect and collate feedback and feature requests
6. ontologist/data curator to consult on issues that come up with people's data in indexing and and plan for version changes in the VIVO ontology with each new release
7. a system manager to provision, monitor, and troubleshoot the virtual machines needed to support indexing and the search website

Initially: DuraSpace might do marketing, and system administration/support, and VIVO ontologists and developers could rewrite the indexing code, update the UI and web front end, and review candidate data. Project management might need to be hired.

Colorado has expressed willingness to contribute to development efforts, but the project is big enough that at least some developer time will need to be budgeted.