Page History

...

• keep it simple – have all the tools we need, but not multiples
• characteristics
  • name | URI/locator | purpose sentence | date information (date recorded; last updated) | owner/stakeholder/stewardship | public/private
    
    • if we don't know the steward that's a red flag
    • if private, logins required– move toward single sign-on with VIVO account that can be passed from person to person
  • do we want a category?
  • assign a status and/or recommendation
    • archive, update, or current, with a reason for recommendation

Wiki – for communication within the project

• there's the main wiki space, then a set of other spaces
• pages in the wiki are not assets – too much detail

vivoweb.org – for communication beyond the project and for outright newcomers

• is the blog a separate asset? inclined to think of vivoweb.org as one asset that is managed as a communications tools

conference-related assets

• probably has several parts
  • mailing list/CRM
  • archive of presentations (presently on vivoweb.org)
  • website
  • mobile app
  • sponsor materials
  • photos
• sometimes these overlap VIVO project assets – e.g., a list of prospects

things we think we are not using

• vivo.ideascale.com
• sourceforge wiki (no longer linked from the vivo.sf.net landing page)

things we have too many of but still need

• a CRM that all project staff can contribute to
• lists of VIVO sites
  • vivo.vivoweb.org
  • a list in the wiki

things we think we need and don't have

Action items