Web Governance Roles and Best Practices
David T: Safety and humanity. Avoid dangerous patterns.
Can we clarify the questions that we can ask?
What are the pain points?
Orphaned websites - how do we deal with those?
Do people understand what they are committing to when they ask to build a website?
What do the ongoing conversations look like when handing over a website for day-to-day maintenance?
How do we define roles and responsibilities in a human-friendly way?
Should our designs indicate an hierarchy of ownership, and who is responsible for what?
Standardize a practice of ownership, last modified date, report an error, and contact information
Are there any policies about ownership of websites? Is there any mechanism to get that website taken down or transfer of ownership?
There are policies for security, accessibility, and branding/identity. There are not policies for ownership or upkeep.
There are very outdated websites that still have academic value. That academic value has outlasted the technology upon which it has built.
At Harvard they built a SaaS product that spun off into a research-focused application. Open Scholar, https://openscholar.harvard.edu/
How do you report issues to get them to the person who actually can resolve them?
Has anyone looked at Collibra? (sp?) https://www.collibra.com/
Resource: https://stanfordwhat.stanford.edu/
What are the primary things that will make this easier for web groups on campus?
Written policy about ownership of websites: when no owner has been identified, it gets taken down.
Everyone should be working with the SUL Web Archiving team to crawl important websites so that we can shut them down.
More automated retirements
When someone leaves the University, why doesn't their boss get a report of the things that they own or have access to?
