...
- Acknowledge the problem – and try to explain briefly the nature and source of the problem.
- Correct problems at the source if at all possible – while sometimes you have to make an emergency correction or update, the problem may be reintroduced with your next update if it isn't fixed at the source.
- Every VIVO should plan for Emergency Removal of Data (Example of Policy) in response to legal or administrative action
- When errors originated in VIVO or will not get overwritten by later automated updates, empower and train people to correct them, either through self editing or proxy editing. Not everyone will, but those that learn how like having that level of control – and if it's an admin aide who's taken the brunt of a complaint from a faculty member, then he/she will be happy to be able to report an instant correction.
- Report bugs to the vivo-dev-all list, vivo-imp-issues list, or vivo-ontology list, or on the vivoweb.org contact formMailing Lists.
- Add principles based on your experience here
...