2018-02-26 Meeting notes

Date

Attendees

Meeting notes

Updates

  • AJ reminded us that this is Fair Use Week. RA and GG's blog post on fair use and the DPLA was recently posted to the Scholarly Communication @ Temple blog. Tabling is all ready to go for Wednesday and Thursday: posters and handouts have been printed; candy has been purchased; gift card is ready. RAL inquired about table setup logistics. AJ noted that materials will be in a cart located in Paley 132. AJ will setup the table on both days. KD will send a reminder message about the ACRL copyright webcast across the LIBSTAFF listserv on Wednesday.


ET Update on Website

  • ET checked in with CS regarding whether they is anything we can do as a team in preparation for the new website. It was noted that we can begin discussing, outlining, and writing content for the new website regarding what services and resources (which would not already be going into a corresponding LibGuide) we might provide.
  • AJ asked about the best way for our team to begin that. We considered the benefits of creating another inventory of scholarly communication-related webpages and LibGuides; we also questioned whether there was content of which we were not aware. ET pointed out that there has already been an inventory of the Libraries' web content; she volunteered to obtain a working list of related scholarly communication content items and pointed out that any inventory we create we could prioritize.
  • AJ showed us the scholarly communication page she worked on previously, and there was discussion regarding who would have control over the kinds of content that can and cannot appear on the new website. There was further discussion about what would be linked to what, in addition to identifying related entities (e.g. DSC).
  • ET noted that she believes the desire for new website is to move away from creating laundry lists and, instead, make something more dynamic. ET mentioned that perhaps by sometime in April there may be some additional information regarding governance and/or organization of the new website.
  • AJ summed up: regarding scholarly communication-related content on the Libraries’ website, we should not concern ourselves about structure (e.g. what the page(s) should look like) but instead think about services that would be provided. ET will start a Google doc as well as go back through her prior inventory.


Upcoming Joint Meeting w/ RDS SST

  • AJ asked what we wish to discuss with the RDS SST. She pointed out that our two teams have some similarities and overlap regarding education and the institutional repository. We discussed issues related to how the two teams might coordinate, work, and effectively communicate with one another. AJ mentioned that the team leads meet with NT every two weeks and tend to discuss broader, process-oriented issues. It was mentioned that SW is considering creating a shared Google calendar for highlighting public programming events -- this might be a way for increasing awareness and coordination among teams. Another topic brought up for possible discussion was the (new) library website.


IR documentation

  • AJ provided a brief overview of the history of an institutional repository at Temple. There were some questions and discussion. AJ asked SR and KD to review their older documentation and/or notes from their time serving on the LRDS Service Implementation Team (SIT) subgroup and determine if there is anything worth sharing. RA noted that she can review some of the documentation that Delphine shared with her as well.