Dsg 2015-01-08

From Digital Scholarship Group
Jump to navigation Jump to search

Introductions: New Staff

Julia announced new additions to the DSG:

  • Linda Moss, who begins work on Monday (1/12/15), who will be working with TAPAS and with the Library Technology Services Group
  • Jim McGrath, DSG Coordinator

Julia also mentioned that the DSG will be working / interacting with

  • Anna Spatz, a visiting graduate student who will be "embedded" in the DSG starting on Monday
  • David Castillo, a new intern from Simmons College

DSG Calendar Discussion

We discussed the perceived need for a shared calendar so that the DSG can keep better track of staff schedules, commitments, etc. in the interest of improving our scheduling. Jim will look into Podio's abilities on this front.

We also discussed the benefits of adding DSG events to the library's calendar. There may be an automated way to have calendar events listed on the DSG site cross-post to the library. Jim will also talk with Jen Anderle about the library's Spring 2015 schedule.

Phone Contact for DSG

The DSG will display a phone number in the area outside the DSC in the event that people can't get into the space. This number will route first to Jim's cubicle and then to Amanda's desk (the caller will then have the option of leaving a message with Jim if no one picks up). This number / set-up is in the works.

Semester Road Map

Julia asked us to begin compiling a list of tasks and goals for the Spring 2015 semester, as the dean is looking for DSG goals and action items.

Previous Accomplishments"

  • basic communication systems
  • web site
  • listserv
  • Twitter
  • policies for intaking DSG projects
  • tactical consequences of these systems


2015 Tasks and Goals (Summary of discussion)

  • what needs to happen every year to keep the DSG healthy, well-populated, paid, useful, etc.
  • continuing the data management and planning discussions we’ve been having
  • DRS Plus roll-out: the CFP, the project review process, and the work of getting the repository up and running
  • Assessment: how we describe and measure success and the implications for permanent funding from various channels
  • annual review process for projects
  • David (Simmons intern) will be handling a lot of DRS-Plus-related stuff
  • Outreach and Visibility: focusing on staff excellence
  • Idea of having an annual calendar (Syd): setting particular goals that don’t change for each time of year so that the DSG can better establish its working rhythm / keep track of recurring tasks
  • Updating the wiki with minutes


Discussion: Data on Use of DSG Projects / Items in DRS

We discussed current ways of tracking use of content items in the DRS and ways to refine / improve / organize analytics. Jim and Hillary will look into ways of tracking alt-metrics (Hillary mentioned Impact Story as a potential option). We also want to make sure that metrics will be accessible / not tied too closely to one particular staff member (in the interest of creating a system that will "out-live" any individual).

We also discussed canvasing current DSG projects to see what kinds of user metrics / data they presently keep an eye on.

There was an additional discussion of canvasing the web to see if we can track where particular projects are being referenced / used in classrooms, etc.


Discussion: What happens when someone contacts the DSG?

Julia led a general discussion concerning how to proceed when someone contacts the DSG with an idea for a project / a request for assistance. Topics covered also included a need to see where and how often the DSG is being written into grants. Julia encouraged DSG staff to feel free to meet with interested parties, and she also highlighted the importance of checking in with either her, Sarah (Sweeney), or Amanda when it came to questions of project scope / feasibility. We also discussed improving the DSG's current contact list.

Presenting DSG at all-staff Library Meeting in 2015

Patrick mentioned that he would like the DSG to present an overview of what the group has accomplished at an all-staff meeting during the spring semester. The discussion did not land on a particular meeting date, but this is on our radar now.