Reading Session #4: Digital Content and Infrastructure Needs of Research Faculty
Led by Jennifer Schaffner, Susan Kroll, Mackenzie Smith
Links: A Slice of Research Life available at http://www.oclc.org/research/publications/library/2010/2010-15.pdfhttp://www.oclc.org/research/publications/library/2010/2010-15.pdf.
Scholarly Information Practices from the Online Environment available at http://escholarship.org/uc/item/0kr8s78vhttp://escholarship.org/uc/item/0kr8s78v.
MacKenzie's objections to Kroll's Report:
- How valid is this research at your individual institution (each university is a snowflake...)
- There is tension but still trying to move ahead even though administration is telling you that you can't
- Senior Faculty behave differently than rank and file researchers
- Mission and marketing - how do we market what we are already doing
Other notes:
Coeus - MIT http://coeus.org/
Faculty want help with: structuring their notes and datasets, negotiating publication licenses, funding requirements, authority work, customizable personal webpages, and keeping up to date with their iterations.
Review Ithaka's faculty survey
www.rin.ac.uk - patterns of info use and exchange case studies
"pre-print is a more authentic representation of their work" - Kroll's study found that this is the feeling of faculty
Sustainability and Revenue Models
for Online Academic Resources
An Ithaka Report
May 2008
http://www.clir.org/dlf/forums/fall2010/sca_ithaka.pdf
Reimagining METS An Exploration
http://www.clir.org/dlf/forums/fall2010/METSNextGeneration.pdf
U.S. Government Printing Office’s Federal Digital System (FDsys)
http://www.clir.org/dlf/forums/fall2010/FDsysFactSheet.pdf
Closing the Digital Curation Gap
http://www.clir.org/dlf/forums/fall2010/CDCGflyer.pdf
Twitter summary:http://wiffiti.com/screens/41933summarized: http://summarizr.labs.eduserv.org.uk/?hashtag=dlf2010
Agile Project Management:
working software, customer collaborations, responding to change, individuals and interactions
Characteristics of agile:
plan as you go, feature-breakdown structure, user stories, release plan, story boards, deliver as you go, learn every iteration, adapt every thing, manage team
"Information radiators"
empowering and trusting people, providing a constant feedback
change happens frequently
requirements are not well-defined
new technology or public domain
customer isn't sure of what is desired
Delphine uses agile/scrum at Penn State - calls some members of her team "ingesters"
NCSU - refer to powerpoint for books to read
Greenhopper & JIRA
Google docs & JIRA