Versions Compared

Key

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

All questions are not required unless otherwise specified. Please submit no more than one survey per institution. (Need a form tool that allows saving and passing among different people.)

Background

  • What is the name of your institution?
  • How would you describe your institution? (Check all that apply.)
    • research university
    • undergraduate college
    • medical school
    • governmental organization
    • non-governmental organization
    • non-profit
    • other (please specify)
  • In what country is your institution located?
  • Would you like your submission using this survey to be anonymized?
  • Is your VIVO in production?
    • Yes
    • Yes, but it's in beta.
    • No, but our institution has made a commitment to VIVO and we're in the development stage.
    • No. We still haven't decided whether to adopt VIVO, but we're in the exploratory stage.
  • If yes, what is the URL for your VIVO?

...

  • (If in production), how many FTE-years were needed to get VIVO ready for production?
    • For example, if three people worked on VIVO for three years that would be 9 FTE-years.
  • What is the average number of FTEs that have worked on your VIVO implementation in the last year?
  • Before starting on VIVO, do any of your developers have experience with semantic applications?
  • In the last year, how many FTEs do you have for each of the following? If one person does multiple roles below, divide the FTEs between people.
    • Developer
    • Business analyst/information architect
    • Marketing/outreach
    • Project executive
    • Ontologist

...

  • Which of the following person types do you capture?
    • Faculty
    • Postdocs/fellows
    • PhD students
    • Other students
  • Which of the following data does your VIVO capture using external sources?
    • Preferred name
    • Preferred title
    • Publications
    • Grants, agreements, and contracts
    • Positions
    • Educational background
    • Certifications
    • Professional service
    • Honors and awards
  • Which of the following data do you allow users to manually enter?
    • Preferred name
    • Preferred title
    • Publications
    • Grants, agreements, and contracts
    • Positions
    • Educational background
    • Certifications
    • Professional service
    • Honors and awards
  • How many of each of the following does your VIVO have?
    • Internal persons
    • Publications
    • Grants, agreements, and contracts
    • Honors and awards
  • What is your source for disambiguate them?
    • End user
    • Administrator/developer
    • Symplectic Elements
    • ORCID
    • Custom workflow
  • What is your source for publications (check all that apply)
    • Medline
    • Web of Knowledge
    • Google Scholar
    • Scopus
  • Do you display non-federal grants?
    • Yes
    • No
  • How often do you update the following sources? (daily, weekly, monthly, variable)
    • Persons
    • Publications
    • Grants, agreements, and contracts
    • Positions
    • Educational background

Development

  • Has anyone from your site made core contributions to a software project before?
  • If any, how many people from your site have made contributions to VIVO core?
  • What are some roadblocks that have prevented developers at your site from making core contributions?
    • Failure to understand how the application works
    • Don't know where to start
    • Lack of perceived permission from the most common core developers
    • Competing projects
    • Decision makers don't see the value
    • Don't have any particular needs that could be addressed
  • Where do you maintain your code base?
    • Internal Internally hosted Subversion repository
    • Git-Hub
    • Git
    • Local copy of Microsoft Wordpad

...

  • How many custom classes does your VIVO use?

  • How many custom properties does your VIVO use?

...

Size, performance and caching

  • (If in production), how many rows are in your quads table? 
    • Run SELECT COUNT(*) FROM Quads;
  • When caching is not turned on, how long does it take your largest organization or person profile page to load?
  • On a scale of 1-10, how happy are key stakeholders with your institution with VIVO's speed?

...

  • On a scale of 1-10, please rate how effective each of the following methods have been for solving development roadblocks:
    • Trial and error
    • Email to the listserv
    • Searching the listserv archives
    • Bringing it up on the implementation/development call
    • Contacting one or more developers off-list
    • Long walk on the beach, staring wistfully into the surf
    • Using the wiki
  • How has the pace of development for your VIVO compared to other similar applications at your institution?
    • Much faster
    • Somewhat faster
    • About the same
    • Some slower
    • Much slower
  • How does VIVO's online documentation compare to other projects you've worked on?
    • Complete and useful
    • Decent
    • Has some gaps
    • Poor
  • Prioritize the following support materials:
    • Self-guided tutorials for data ingest
    • White paper highlighting use cases for how VIVO can benefit an institution
    • Detailed list of standard application and server configurations
  • What is the name of one other open source project that with documentation the VIVO community could do well to emulate? If answer, what does this project have that VIVO lacks?Please describe.
  • For those who represent institutions outside the United States, to what extent do you feel the VIVO community makes an effort to include you in its activities?
    • Definitely
    • Sometimes
    • Rarely
    • Not at all
  • In what ways can VIVO be better about support international sites?

...

  • On a scale of 1-10 how much of a challenge have each of the following been to date?
    • Getting adequate resources from administrative leadership to proceed
    • Cleaning up dirty data from institutional sources
    • Theming
    • Political: getting access to ingest data from institutional sources
    • Understanding VIVO's semantic data model
    • Ingesting data using Harvester or other similar tools
    • Language - English is not our first language

 

Sample questions

  • how many FTEs work on VIVO (and what is their domain expertise?)
  • what data are captured
  • what additional tools are used
  • can put the results in http://vivo.vivoweb.org 
  • perhaps do a dry run at the I-Fest
  • useful for DuraSpace to understand community growth, member prospects?
  • production environment specs/config?
  • platform details (maybe also some info on dev/test environment)
  • priorities for addressing gaps

...