Versions Compared

Key

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

...

  • 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 city and country is your institution located?
  • Do you anticipate using VIVO to connect more than one campus or location?
  • Would you like your submission using this survey to be anonymized?
  • Is your VIVO in production?
    • Yes
    • Yes, but it's in a public beta
    • Yes, but it's in beta .and only visible behind a firewall
    • 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 beta, what will it be once public?)

Server and application configuration

  • What version of VIVO are you currently running on in production?
  • How much memory is allocated to your production instance of VIVO?
  • What database do you use?
    • MySQL
    • PostgreSQL
  • Do you use a triple store other than Jena SDB? if so, what?
  • Do you use HTTP caching?

Personnel

  • (If in production), how many full-time equivalent or FTE-years were needed to get VIVO ready for production?
    • For example, if three two people worked on VIVO for three years 18 months that would be 9 3 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 did 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 any? If one person does multiple roles below, divide the FTEs between people.his or her effort among the roles
    • Project executive
    • Project manager or coordinator
    • Developer
    • Business analyst/information architect
    • Ontologist (e.g., for local ontology extensions)
    • Marketing/outreach
    • Project executive
    • person
    • IT systems engineer (e.g., for installation, configuration, and tuning)
    • Programmer/ETL specialist (e.g., for writing scripts to ingest and update data or to re-purpose data from VIVO)
    • Web developer (e.g., for branding & customization)
    • Other role (please list)Ontologist

Content captured

  • Which of the following person types do you capture?
    • If in academia
      • Tenure track faculty
      • Instructors, lecturers, and other longer-term academics
    • Faculty
      • Postdocs/fellows/visiting faculty
      • PhD students
      • Other students
      • Extension educators and/or research staff
      • Technicians and lab/facility staff
      • Other staff (list types)
    • If in government or non-profit sector
      • Researchers
      • Administrators and managers
      • Technicians
      • Affiliates
      • Other staff (list types)
  • Which of the following data does your VIVO capture using other local or external sources?
    • Preferred name
    • Preferred title
    • Positions
    • Educational background
    • Publications
    • Artistic works/performances
    • Consulting/professional practice
    • Certifications
    • Professional service
    • Community service/outreach
    • Honors and awards
    • Teaching
    • Advising
    • Grants, agreements, and contracts
    • Positions
    • Educational background
    • Certifications
    • Professional service
    • Datasets
    • Academic departments (usually having degree-granting authority)
    • Academic programs (often less formally constituted)
    • Labs, facilities and equipment
    • Research centers
    • Degree programs
    • Student organizations
    • Research services
    • Other research resources (e.g., seed banks or other genetic resources)
    • Events
    • News releases (written at your institution)
    • Media coverage (articles written elsewhere about people/events/programs/publications/grants at your institution)
    • Impact statements/extension success stories
    • OtherHonors 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
    • Internal organizations
    • 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

...