The website permission request has fields that need to be completed in order to process a request to link to external content. Completion of these fields allows the library to expedite your request.
- Task Name
- The task name should include the Website - or Video - or PDF - at the beginning, followed by the domain name and, if applicable, the page/content name preceded by a colon. e.g., Website - Value Penguin: Can You Use Health Insurance in a Car Accident?
- Assignee
- This field will be assigned out by a librarian
- Due Date
- We need to have this information to prioritize the permission requests (see FAQ below for additional information).
- Projects
- All requests must be added to the Content: External Website (Permissions) project and the corresponding course or project listed in order to auto-generate the fields.
- Dependencies Ignore
- Exists in DB?
- The requester must check the External Websites: Permissions Database to determine if the website has previously been reviewed and verify if any conditions exist for linking to it.
- DB Record Link
- If the website is in the database, add the task link from the database to the DB Record Link field (see FAQ below for additional information).
- URL (one per request)
- The https//: is needed in front of the address to make the page linkable from Asana. Additional pages from the same website only may be included in the Description field (see FAQ below for additional information).
- If unrelated websites are included in the same task, the requester will be asked to resubmit them as individual requests.
- Important: Does your link start with https:\\? If there is no "s" at the end of the http, the student may receive security warnings and browser errors when they attempt to access this site (see FAQ below for additional information).
- Content Type
- This field acts as an indicator of potential copyright issues/requirements.
- Both CC & Transcript
- Videos need both CC and transcript; audio files need a transcript.
- Integral to the course?
- If this is marked Yes, a written request may be necessary unless the TOU or copyright language allows for linking.
- Description
- Any context affiliated with the requested link assists the copyright reviewer in determining whether or not it is allowable, this includes any linking, embedding, creative commons usage, etc. Context is appreciated for linking only requests. Any requests that go beyond linking, such as for embedding, require context for us to secure written permission.
