The purpose of this document is to establish and promote the ethical, legal, and secure use of computing and electronic communications for all members of Duke University and its affiliated entities.
Duke University and Duke University Health System (Duke) are dedicated to excellence in education, research, and patient care. Data is a vital component of Duke’s operations and it is important to ensure that authorized individuals can access data appropriately.
Social Media Guidelines for Communicators
The purpose of these guidelines is to help Duke communicators understand how Duke policies apply to using social media in their work.
Duke’s Media Policies
These policies are in place to support Duke’s primary mission of research, education, and healthcare. Our goal is for students, faculty and other members of the Duke community to carry out their activities with a reasonable expectation of privacy and normality while remaining free to speak openly with the media if they choose to do so.
All commercial, non-news photography or videotaping must be approved in advance by University Communications or the Health System News Office (for health system activities).
Vendors must work through Procurement and Supply Chain Management in order to establish a business relationship with Duke University and Duke University Health System. Communication vendors are vetted through the Office of Marketing and Strategic Communications.
Copyright laws were developed in the United States as a means of encouraging “progress of science and the useful arts.” Copyright laws grant the creator (or the owner of the copyright) the rights, within the limits of fair use, to do with their work what they please. The intention is that by creating a financial incentive for a limited time, creators will have a motive for producing more works which will enrich the public.
Any work being done through a contract organization – internal or external – is required to maintain a minimum service-level agreement of 10 hours per year. Due to the ever changing nature of the web and the need for version and security upgrades on our preferred platforms, site owners need to identify some portion of their budget and calendar for updates and patching. Without this, sites are subject to vulnerability and attacks. Should a security breach occur, the security office maintains the right to the remove the affected site until it can be confirmed as no longer a risk. IT organizations such as OIT and DHTS cannot be held responsible for things they didn’t participate in building and should not be expected to serve as quick fix in the event of a site being take offline.