Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

QuestionResponse
How many institutions does the application currently support?8 – 7 VIVO sites plus 1 Harvard Profiles site
How many institutions will be targeted?
  • initially 12-20; in 2 years, 100; ultimately 1000(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)
  • 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 must represent VIVO, Harvard Profiles, SciVal experts, and Iowa's Loki, and hopefully . If promises to do the export happen, Pittsburgh's Digital Vita and Stanford's CAP systems may also be able to provide data; ideally one institution participating only through 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)
What are the roles?

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

  • an indexing programmer familiar with Java and Hadoop
  • a web developer experienced with Drupal or an alternative open-source content management system with an established infrastructure to support Solr
  • UI designer experienced with developing search interfaces and comfortable working in Drupal (or the chosen platform if different)
  • 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
  • a marketing person to write up public-facing documentation, recruit new organizations, collect and collate feedback and feature requests
  • 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
  • a system manager to provision, monitor, and troubleshoot the virtual machines needed to support indexing and the search website
project manager | ontologist/data curator | UI designer | web developer | indexing programmer | system manager
What will be the division of labor?

Initially: DuraSpace could might do project management 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 dataUtlimately: could become a division between all aspects of production support, including marketing, and development of new features based on input from subscribers and sponsors. 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.

What are the primary "keys to success"?going beyond providing the obvious first win (integrated search) to addressing some of the immediately visible disambiguation problems (the same persons, organizations, events, funding agencies, journals, etc. coming in from indexing with multiple different URIs from the different source systems, and offering services to support linking from one university's research networking system to another.
Is there a market to attract service providers for readying data at campuses/organizations?yes, including Symplectic, Recombinant, potentially others

...