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 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 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 two people worked on VIVO for 18 months that would be 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, 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 his or her effort among the roles
- Project executive
- Project manager or coordinator
- Business analyst/information architect
- Ontologist (e.g., for local ontology extensions)
- Marketing/outreach 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)
Content captured
- 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)
- If in academia
- 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
- 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
- Other
- 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
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?
- Internally hosted Subversion repository
- Git-Hub
- Git
- Local copy of Microsoft Wordpad
Ontology
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?
Outreach and feedback
- 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, why do you suppose end users do not interact with their VIVO profile?
- They have better things to do.
- Too many options
- Marketing needs to be better
- Other (please specify)
Apps and tools
- Which of the following apps and tools do you use?
- OpenSocial gadgets
- 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
Support
- 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 with documentation the VIVO community could do well to emulate? 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?
Internationalization
- Do you use internationalization?
- If yes, which languages?
Challenges
- 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 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
Who wants to help?
Paul will facilitate a call to write out the questions and has a way to host it, and we can circulate it with this group and others enough by the I-Fest to solicit input
- Jon volunteers Kristi (and himself)
- Julia -- we have something to discuss on the last day of the I-Fest, but busy with the March 7 rollout and I-Fest prep before then
- Paul -- have a proposed outline/survey before IFest, and then discussed at IFest as Julia suggests
- look for one response per institution
