Collaborative Workflows for Risk Management in Sharing Cultural Heritage Collections Online

Short Description:
Digitizing rare and unique historical documents so they can be shared online is mission-critical work for most cultural heritage institutions, but it can be difficult to complete this work, especially intellectual property rights management, at a scale that matches user demand. The authors of this open educational resource offer guidance for creating scalable, cross-functional workflows using a risk-management approach that increases efficiency and distributes responsibility for rights assessment work more equitably across stakeholders. It includes advice for navigating knowledge gaps, building an engaged team with the right skillsets, reimagining workflows, and rethinking traditional archival processing workflows to build capacity for rights analysis during arrangement and description. Each chapter includes a helpful exercise for implementing this guidance in your own institution.

Word Count: 28621

(Note: This resource's metadata has been created automatically by reformatting and/or combining the information that the author initially provided as part of a bulk import process.)

Library Carpentry lesson: An introduction to Git. What We Will Try to Do Begin to understand and use Git/GitHub. You will not be an expert by the end of the class. You will probably not even feel very comfortable using Git. This is okay. We want to make a start but, as with any skill, using Git takes practice. Be Excellent to Each Other If you spot someone in the class who is struggling with something and you think you know how to help, please give them a hand. Try not to do the task for them: instead explain the steps they need to take and what these steps will achieve. Be Patient With The Instructor and Yourself This is a big group, with different levels of knowledge, different computer systems. This isn’t your instructor’s full-time job (though if someone wants to pay them to play with computers all day they’d probably accept). They will do their best to make this session useful. This is your session. If you feel we are going too fast, then please put up a pink sticky. We can decide as a group what to cover.

9th edition

Short Description:
The MLA Style Citation Tutorial was created by librarians at the University of Alberta Library and NorQuest College Library to support students and faculty. The tutorial explores why citation is important and shows how to create citations for different types of sources, using the 9th edition MLA guidelines. This tutorial can also be used as a reference resource.

Long Description:
The MLA Style Citation Tutorial was created by librarians at the University of Alberta Library and NorQuest College Library to support students and faculty. The tutorial explores why it is important to use citations and how to create works cited list entries and in-text citations based on the 9th edition MLA guidelines. This tutorial can also be used as a reference resource. The MLA Style Citation Tutorial is an adaptation of the APA Style Citation Tutorial by University of Alberta Library.

Word Count: 4961

ISBN: 978-1-55195-478-3

(Note: This resource's metadata has been created automatically by reformatting and/or combining the information that the author initially provided as part of a bulk import process.)

This lesson is part of the Software Carpentry workshops that teach how to use version control with Git. Wolfman and Dracula have been hired by Universal Missions (a space services spinoff from Euphoric State University) to investigate if it is possible to send their next planetary lander to Mars. They want to be able to work on the plans at the same time, but they have run into problems doing this in the past. If they take turns, each one will spend a lot of time waiting for the other to finish, but if they work on their own copies and email changes back and forth things will be lost, overwritten, or duplicated. A colleague suggests using version control to manage their work. Version control is better than mailing files back and forth: Nothing that is committed to version control is ever lost, unless you work really, really hard at it. Since all old versions of files are saved, it’s always possible to go back in time to see exactly who wrote what on a particular day, or what version of a program was used to generate a particular set of results. As we have this record of who made what changes when, we know who to ask if we have questions later on, and, if needed, revert to a previous version, much like the “undo” feature in an editor. When several people collaborate in the same project, it’s possible to accidentally overlook or overwrite someone’s changes. The version control system automatically notifies users whenever there’s a conflict between one person’s work and another’s. Teams are not the only ones to benefit from version control: lone researchers can benefit immensely. Keeping a record of what was changed, when, and why is extremely useful for all researchers if they ever need to come back to the project later on (e.g., a year later, when memory has faded). Version control is the lab notebook of the digital world: it’s what professionals use to keep track of what they’ve done and to collaborate with other people. Every large software development project relies on it, and most programmers use it for their small jobs as well. And it isn’t just for software: books, papers, small data sets, and anything that changes over time or needs to be shared can and should be stored in a version control system.