Last week’s webinar seemed to go very well. It’s a whole different experience for me, making a presentation in a format which makes it impossible for me to see or hear the audience. There were apparently 83 people in attendance, and the feedback I’ve received both from bepress and via email has been positive.
Plus, my sign totally worked:
If you’re interested in what I had to say about getting faculty involved in a digital repository, but weren’t able to attend, there are a few ways you can check it out. First, here are the slides from Prezi:
Or, you could watch the video of slides with voice-over:
Both of those, plus a PDF of the slides, are available here.
Overall, I’m pretty pleased with how this went. I probably talked too long,* and so we didn’t have as much time for questions as I’d like.** But I thought the questions I did get were good, and I’m hopeful that folks might send me more.
I enjoy talking about this stuff, and I try to frame the conversation in terms of relationships: both between the folks who work at libraries and the folks who make content, and between the material within the repositories and its users/creators.
Back when I spoke at an IR Day in April, the one piece of negative commentary I received was that I didn’t use the DigitalCommons software at any point in my presentation. Frankly, I can’t imagine giving that kind of presentation outside of training folks within my library or school to use the software, and one of the reasons I’m glad give webinars or presentations in conjunction with bepress is that I don’t have to frame my presentation in a DigitalCommons-specific way.***
I try to make this stuff generally applicable, regardless of what kind of repository software you use (and maybe even to digital library projects beyond repositories). Hopefully, I succeeded this time around.
** I can’t really fault bepress for cutting things off right at an hour, though; I actually needed to end the webinar and start a chat reference shift.
*** I did talk a bit about the upload interface, I believe, but even then I tried to frame in the context of how much you could expect folks outside the library to contribute to repository workflow.