Date

 

Attendees

Goals

  • Review, next steps

Discussion items

TimeItemWhoNotes
25 minReview interviews and next stepsAll

What did we learn? What must still be done? How do we "finish" the asset inventory?

25 minRecommendation ProcessAllHow will we develop recommendations?
10 minNext meetingAllWhen do we meet again? What do we need to have accomplished?

Notes

  • Updates on the asset inventory, questions, and/or work still to be done
    • Mike – waiting to hear back from Chris, Lauren from Kristi, Alex from Stephen, and Jon from Miles; Jim interviewing Ted tomorrow
  • Recommendations – what might become of some of these things, with the general notion that a little less would be a lot more
    • General notion - abandoned sites are not good to leave up
      • some can just go away
      • others will have to be harvested before moving
      • leaving a breadcrumb trail may be necessary in some cases, but with Google may not be necessary
    • Sourceforge repository
      • move to GitHub? eventually shut it down and move the whole thing – just moving files, and we're not encouraging people to use the old releases - more for us than for the community at that point
        • use search functions
        • better than having to poke around more than one site
    • Listservs – the CRM
      • several of them are most likely useful as CRM material – who had been engaged, when, for what – a tag in a CRM system
      • but we need to know what the Zoho CRM and Constant Contact do and why both are being kept active (syncing and management) – figure out what we are going to use them for on the VIVO project for use cases we have
        • want a universal list of people and organizations that we can tag and make useful lists
        • if there is a notion of a communication, may have tags there, too
      • can list archives be moved from one platform so they could stay searchable?
      • need a good public name for the list – e.g., vivo-tech
      • need to be able to authorize people to work on them, find out who's on them – has been largely opaque – there should be one way to manage in an agile way
      • Discourse – an alternative to StackOverflow by one of their developers to suit a different purpose, namely keeping a threaded community conversation versus having the most popular answer bubble up to the top
        • needs an infrastructure – a commodity like Confluence or JIRA
        • internally, DuraSpace is looking at similar things for distributed virtual work teams – Slack.com
        • Paul – uses Slack a lot but it's more like next generation IRC – not good for capturing historical stuff
        • Discourse would be $100/month for a hosted version (check)
          • 5 power users
        • We don't want anything with a head count type licensing model – should be open to anyone in the community to use, if not to administer
      • Goals – to not have posts on the message board lost, and to have previous conversations on the same or related topics accessible and searchable
      • Other new generation tools emerging – Vanderbilt tried Rocket but it didn't catch on
      • Are we alone in having this issue?
        • other projects are using Google Groups – e.g., Fedora – and we should talk with them
        • can also talk with the Hydra people – both very active and have infrastructure that works the way they want
        • should we invite Andrew Woods to one of these calls? could be helpful– Mike will contact him
    • Conference resources should be largely separate
    • Marketing – a whole slew of resources – DuraSpace has a bunch of resources that we have never become that comfortable with
      • generally want as many channels as you can, but need to understand the channels and how to use them
      • e.g., a newsletter to 8,000 people – has VIVO items in it, apparently
      • may be more of an operational issue than an asset issue
      • they have a Youtube channel for VIVO with 2 videos they made for marketing
        • we also want instructional videos/screencaptures
        • also have recorded apps&tools calls elsewhere on YouTube
    • One domain we don't even have - material for end users
      • minimal information distributed with the software
      • to tell them what they can do with VIVO
      • where should that live?
      • e.g., a 2-minute video on how to use faceted search
        • see suggested assets
        • Alex – saw a longish video that Duke put together but is now out of date – would be good to have shorter segments that could more easily be updated
        • Mike – RedCap has 20+ short videos offering end users basic instruction
    • Implementation – where the real complexity begins
      • our technical installation documentation has come a long way, but going beyond that to data implementation issues is where we fall down

Next steps

  • each of us completes our interviews
  • a conversation with Andrew Woods about Fedora community infrastructure
  • invite anybody from Hydra? DSpace?

Next meeting

  • Wednesday, May 6 at 3 pm ET/ 1 pm MT

Action items

 

2 Comments

  1. Addendum: I spoke to Ted Lawless. He was not able to identify any additional assets. He suggested that:

    Fewer on-line sites means less chance of duplication, less chance of neglected resources, easier to find what you are looking for. Fewer is better.

  2. I spoke with Chris Barnes.  He identified three additional assets.  I added them to the inventory.