, 10am-4pm
UCSF Mission Bay, Mission Hall, Room MH 210

Call-In Instructions

Join the web meeting

Audio Only Dial-In:    +1 415-514-1000 (Toll)
Access Code:              996 311 652
Password:                   This meeting does not require a password.


Discussion items

  • Introductions
  • Collection Development Policies
  • I – more examples of what they want to collect, what to transfer/not to transfer; developing coll dev policies for faculty papers
  • SF – similar situation; posted on website
  • B – included in formal campus coll dev policies; website includes some details about what they are looking for; fac papers included in manuscript collections; guidelines for fac papers on UCAC website
  • D – similar situation; spec coll has internal guidelines, not posted; UA in separate unit now; used UCAC docs to develop libGuide for public guidelines; web archiving guidelines as well
  • SC – developed a coll dev policy based heavily on B policies, but not public facing; has LibGuide public doc with guidelines; also has flyer for fac papers; interested in seeing how the policy can be incorporated into records management policies
  • M – recently hired rec manager; beginning effort to deal with departments, retention schedule, etc.; has bits and pieces from retiring faculty;
  • R – basic description of coll deve policy; just got new director for distinctive collections; working to update policy with new website;
  • Why not post policies public facing? B – Document too lengthy, outdated; public facing is easier for users; D – internal workflows may need to be sorted out
  • Do these policies work for format agnostic? B – digital archives have survey document for digital materials
  • Transfer forms – group has shared transfer forms on wiki; many of the campuses have been borrowing from each other, but rather than having a uniform form, we can look to documents on the wiki;
  • PII line on transfer form? – could be easily checked off; SF asks what type of PII is included in collection, helps identify things that shouldn't be sent;
  • transfer of digital material – SD reviewing for to expand details about the digital collections being transferred; D – looked at online transfer form which includes electronic materials
  • How do you transfer data? – D primarily uses physical means of transfer; SF uses UCSF Box and Secure Box for transferring
10:45amWeb Archiving 
  • Web Archiving using Archive-It
  • D – adds 1-1.5 Tb/year; reviewing what they are archiving; has internal working document with "purpose statement" - will become public facing coll deve policy; focus on domain, UC Davis history, events & culture, focus around particular individuals; subject areas of disctinction, include subject specialists; regional historical i.e. local government; websites with eye toward curriculum to support teaching needs; is the collection at risk; considers preservation, education/outreach, developing QA, evaluating success of program
  • how are you dealing with access and rights to web archvies? Access: uses references in finding aid, catalog; hasn't been implemented at scale. Rights: try to contact rightsholders and seek release, have a solid take-down statement
  • Guidelines and training are needed to help have a focused collection
  • Web archiving costs are going up; we need to develop a sustainable method for funding the services; UCs have special pricing for first 3 years, but prices will be rising
  • Preservation – Duracloud/CDL partnership is available; anything else?
  • UC/UCOP web archiving? – Berkeley is doing LAUC systemwide; UC has 15 Archive-It accounts
12:45pmRound Robin Updates/Questions 
  • M – collecting as possible before things get lost; working with new records manager and would like to develop paths for bringing records into the archives; expecting to grow and develop as a university archive over the next year
  • B – Bancroft has launched Aeon as of last week; LAUC archives task force submitted report; National Writing Records Project exhibit, "New Favorites" exhibit involving all curators = top 15 objects that came in since Bancroft retrofit
  • D – developing suite of faculty focused services; trying to bring up back end of digital asset management system; focusing on web archiving; looking at ePADD in the next 2 quarters. One-off projects – working with Google Project to digitize back issues of dissertations and theses; doing a lot of outreach regarding climate change data sites
  • SC – library focusing on digital strategy, establishing workflows for digital materials; some web archiving; outreach with various faculty, departments, and student groups. Questions: had digitized floor plans for admin and chancellor's house - how are these being served to researchers? (SF turned floor plans over to Capital Planning to provide access to current buildings. Blue prints for buildings that no longer exist reside in Archives); Who is working with ePADD? (Irvine); Chancellor's Office is ready to release some of their email
  • SF – new digital archivist and planning for digital forensics lab; will be developing policies and web archiving; NHPRC grant to process AIDS research collection; interviewed 3 candidate for new UL in December, hopefully decision will come soon; received money for scanning equipment (Historical Patients Lab)
  • I – Audra in talks with Law School to fund .5 time processor (temp) for law school and dean's records; involved in SNACK (EAC) tool, have interface that allows editing; working more with student affairs to collect more student organizations; ePADD only able to test appraisal and ?? modules; has asked Born Digital CKG to help with testing of modules, Laura will send more details; working on digitization collection development policy - how they select their digital projects and prioritize
  • SD –
1:30pmResearch DataUCAC/RMC

With Records Managers Committee (RMC) and Wendy D. Streitz, Executive Director of Research Policy Analysis & Coordination

  • Developing policy for handling research data and what happens to data when someone leaves the university. Some awards require research data plans; it has been suggested that it stay with the university. What happens to it? Who keeps it? have looked at Merritt, but it isn't HIIPA compliant
  • Harvard Research Record retention policy released recently
  • RMC will develop tools to help point people to the right place
  • Born digital materials (e-mail, web-sites, etc.)
    1. How to transfer to the archives
    2. How are records managers dealing with born digital records?
    3. What are they telling units to do with these records?
    4. Share challenges, success stories, etc.
  • How privacy protection/access is handled in the archives
  • Question 1: RMC – SC: training to deal the same as paper; preferred format for long term storage, figuring out how to transfer; still figuring it out; email - saving as PDF, but not yet transferred to UA; individually assessing correspondence chancellor's email. SD: providing UA access to chancellor's record; email stored as msg files, also translated in PDF behind the scene; OP: see tips also message management on right side bar with more info; I: using archivematica tool to create access copies
  • How do e-records get transferred to UA?
  • How is privacy protection/access handled in the archives?
  • What is the plan on each campus for chancellor and cabinet email? SD: might be to schedule a meeting to review correspondence in various areas, retention varies in units; understanding was lasted established in 1999. OP: capture significant email in Document Central (president's office decides?);
  • Web archiving – Archive-It established on each campus and capturing elements of the website. Check with UA for details of what is being captured.
3:30pmWrap-up including logistics for next meeting 
  • proposed that we meet face-to-face annually with RMC (around january)
4pmMeeting Adjourn  

Action items

  • @

Agenda Building

  • Next meeting: March 15, 1-2:30pm
  • Minutes: Heather Briston
  • Potential Topics:
    • UC Sesquicentennial Exhibit plans
    • Chron files
    • Retention schedule
    • Collection development policies