Versions Compared

Key

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

...

  • What version of VIVO are you currently running in production?
  • Do you run on
    • Dedicated physical server(s)
    • Virtual server(s)
    • Cloud service (please specify)
  • 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?

...

  • Which of the following person types do you capture?
    • If in academia
      • Tenure track faculty
      • Instructors, lecturers, and other longer-term academics
      • 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
    • Datasets
    • Research projects
    • Published datasets or databases
    • Departments (in academia, Academic departments ( usually having degree-granting authority)
    • Academic Sub-units or 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
    • Other (please list)
  • 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
    • Other
  • How many of each of the following does your VIVO have?
    • Internal persons
    • Publications
    • Grants, agreements, and contracts
    • Internal organizations
    • Honors and awards
    • Events
    • News items
    • Other (please indicate)
  • What is your source for disambiguate themdisambiguating the above?
    • End user
    • Administrator/developer
    • Symplectic Elements
    • ORCID
    • Custom workflow
  • What is your source for publications (check all that apply)
    • Medline
    • Web of Knowledge
    • CrossRef
    • Google Scholar
    • Scopus
    • SSRN
    • MLA
    • Mendeley
    • Local sources (e.g., personal CVs or departmental databases)
    • Other (please list)
  • 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

...

    • Events
    • News
    • other (please specify)

Community Participation

  • Has anyone from your site made core contributions to a software project before?
  • If any, how many people from your site
    • have contributed to listserv traffic?
    • have contributed to demos or webinars?
    • have contributed to wiki pages?
    • have submitted or commented on the JIRA issue tracker?
    • have participated in sessions Implementation Fest(s)?
    • have contributed to conference workshops or presentations?
    • have participated in hackathon event(s)?
    • have shared scripts or code for VIVO-related apps and tools on GitHub or elsewhere?
    • 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 developersor encouragement from current developers/contributors
    • 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?
    • Just on a local server or desktop
    • Internally hosted Subversion repository
    • Git-Hub
    • Git
    • Local copy of Microsoft Wordpad

...

    • Internally hosted Git repository
    • GitHub

Ontology

  • Does someone from your institution participate in ontology calls?

    • if not, why not?
  • Have you included other established ontologies in your VIVO (e.g., VSTO)
  • Have you made any local ontology customizations or extensions? If so,
    • How many custom classes does your VIVO use?

    • How many custom properties does your VIVO use?
  • Do you consider the VIVO-ISF ontology
    • Impossibly complicated
    • More detail than I need but I can ignore what I don't use
    • About right
    • Lacking in areas we need (please specify)

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 in your institution with VIVO's speed?

...

  • How would you characterize your users' response to VIVO?
    • engaged
    • engaged but highly critical
    • apathetic
  • In what ways have you reached out to your users?
    • Online documentation
    • Video tutorials
    • Trainings
    • Focus groups
  • On a scale of 1-10, please rate the frequency with which you receive the following complaints:
    • My data is wrong.
    • Key data of mine is missing.
    • I don't want VIVO to replace my institutional website.
    • I'm not allowed to edit certain data from external sources.

Marketing

  • Who first learned about VIVO?
    • developer
    • librarian
    • provost or dean
    • chief information officer
    • other (please specify)
  • On a scale of 1-10, what level of interest would your institution have in the following?
    • support contracts
    • canned hosting
    • on-site training
    • start-up consultations
    • intensive development help from an experienced VIVO developer
  • On a scale of 1-10, which of the following messages would be most successful in marketing VIVO to your users
    • VIVO saves you time.
    • VIVO helps you find collaborators.
    • VIVO promotes your work and makes you more competitive.
    • Other (please specify)
  • On a scale of 1-10, which of the following messages would be most successful in marketing VIVO to your stakeholders
    • VIVO meets an adminstrative need
    • VIVO saves staff and researcher time
    • VIVO helps researchers find collaborators
    • VIVO promotes your institution's work and makes you more competitive.
    • Other (please specify)
  • On a scale of 1-10, why do you suppose end users do not interact with their VIVO profile?
    • Lack of time
    • Too many competing places they are expected to provide and update informationThey have better things to do.
    • Too many options on the VIVO profile
    • Marketing needs to be better
    • Other (please specify)

...

  • Which of the following apps and tools do you use?
    • Ingest tools originally developed elsewhere (e.g., Harvester, UF tools, Brown tools, Karma)
    • OpenSocial gadgets
    • Duke widgets
    • VIVO-Drupal integrations
  • On a scale of 1-10, how interested would your institution be using the following apps and tools?
    • Export to CV/biosketch
    • VIVO Dashboard, a tool which allows user to create multi-faceted reports using publication metadata from VIVO
    • ORCID integration
    • Duke's HTML embeds of SPARQL queries
  • In what ways do your institution reuse your VIVO data?
    • Data dashboard
    • Business intelligence
    • Other institutional sites
    • Custom visualizations
    • Faculty review tool
  • Do you have a SPARQL endpoint?
    • Yes, and it's publicly available
    • Yes, but it is not publicly available
    • No
  • (If you have a publicly available endpoint), what is the URL?
  • (If you have an endpoint but it's not publicly available), why not?
    • Takes time to set up
    • Worried about performance
    • Concerned about sharing institutional data

...