writing policies for a data repository: experiences at temple university

11
Margaret Janz, Science & Engineering Librarian Gretchen Sneff, Head of Science & Engineering Library Leanne Finnigan, Cataloging & Metadata Services Librarian Fred Rowland, Reference & Instruction Librarian Policy Writing for a Data Repository Experiences at Temple University Image by LaurMG: https://commons.wikimedia.org/wiki/File:Frustrated_man_at_a_desk_(cropped).jpg

Upload: margaret-janz

Post on 15-Apr-2017

346 views

Category:

Education


1 download

TRANSCRIPT

Page 1: Writing Policies for a Data Repository: Experiences at Temple University

Margaret Janz, Science & Engineering LibrarianGretchen Sneff, Head of Science & Engineering Library

Leanne Finnigan, Cataloging & Metadata Services LibrarianFred Rowland, Reference & Instruction Librarian

Policy Writing for a Data Repository

Experiences at Temple University

Image by LaurMG: https://commons.wikimedia.org/wiki/File:Frustrated_man_at_a_desk_(cropped).jpg

Page 2: Writing Policies for a Data Repository: Experiences at Temple University

Background

Page 3: Writing Policies for a Data Repository: Experiences at Temple University

Technical DevelopmentDigital Library Initiatives

Service ImplementationVarious Librarians

Teams

Delphine KhannaHead

Katherine LynchSenior Applications Developer

Steven NgApplications Developer

Leanne Finnigan Cataloging & Metadata Services

Stephanie GeffertBiomedical & Research Services

Fred RowlandEcon & Religion

Kristina DeVoeJournalism & Communication

Page 4: Writing Policies for a Data Repository: Experiences at Temple University

Other People’s Policies

◉ File sizes for self-deposit◉ Embargoes◉ Withdrawal◉ Viruses◉ IRB approved◉ Publishing journals

Katherine OrzeVirtual Intern

Page 5: Writing Policies for a Data Repository: Experiences at Temple University

Employee Manual

11.20 Policy for Misconduct in Research and Creative Work “…Interfering with, misappropriating, stealing or destroying equipment, supplies, or other information including, but not limited to: data, text, works of art or authorship or databases, which either belong to others or over which others have primary usership….”

Data Ownership Policy

Union Contract

Side Letters

2. Intellectual Property…“The University and TAUP agree to meet and discuss regarding issues related to copyright.”

Serendipity

Page 6: Writing Policies for a Data Repository: Experiences at Temple University

Policy Wish List Meeting

(I used this to click anyone who went off

topic)

Page 7: Writing Policies for a Data Repository: Experiences at Temple University

Should we allow

embargoes?

How is this different from Computer Services

options?

Policy Wish List Meeting

But don’t increase barriers to adoption!

Let’s encourage good practice!

How much space do we have?

Should be cap individuals’ space?

Should we cap individual file size?What can the Press

do with what’s deposited?

We should get more cross-campus

administrators on board!

Page 8: Writing Policies for a Data Repository: Experiences at Temple University

This Is Not Legal Advice

◉What rights can we assign the things deposited?

Whatever we want to do

◉What can we do with what’s deposited?Whatever we say we’ll do

◉What legal obligations for preservation/long term?

Whatever we say we’ll do

◉Does Legal Counsel need to approval final policy?

Probably

Page 9: Writing Policies for a Data Repository: Experiences at Temple University

◉ Draft of Pilot Policies & Terms complete!

◉ Send to all the groups for review

◉ Get test group in there

Where We Are Now

Page 10: Writing Policies for a Data Repository: Experiences at Temple University

Lessons Learned

Every question answered leads to more questions.

Uncertainty will never go away completely

That’s what pilots are for!

Page 11: Writing Policies for a Data Repository: Experiences at Temple University

Thank you!

Questions?