Drupal Extension

Integrating open.michigan license forms into Drupal
We have four forms at present. All forms require cosign or friend log-in for access. This page has some information about each form followed by notes on the functionality required/desired in a Drupal integrated version.

Permission to use material
There are two material usage permission forms.

Medical School

All other UM contributors

Differences between Medical School and General permission forms:
 * 1) The top of the Medical School form contains a description of the UM Med School OER initiative. There is an anchor link that skips to the form fields below the description.
 * 2) Faculty may decline participation by responding "No" to the "Faculty participation is voluntary. Will you participate?" question. If they select "No", we request an optional reason for their choice to not participate.
 * 3) The license calculator only appears if faculty members select "Yes" for "Faculty participation is voluntary. Will you participate?".
 * 4) A field for attribution to other authors (Sub Authors)
 * 5) A field for noting sequences from which material may have been used.

The email sent contains primary author information and specifies the CC license that corresponds to the answers to the questions in the forms.

Consent to Photograph or Record Electronically
Users are asked to fill out this form to grant permission to be photographed or recorded. The consent is granted on a per-event basis. Resources with multiple presenters require a separate form from each presenter.

Faculty Specifications for dScribe Materials and Interaction
Used primary by faculty who are opening up entire courses. This form is used:
 * 1) To provide metadata about the course, Instructor name, email, Course Title etc.
 * 2) Identify the dScribe
 * 3) Identify the dScribe2
 * 4) Select what materials are going to be published
 * 5) Choose how the faculty member would prefer to interact with the dScribe

Other relevant information

 * 1) Examples of emails generated are at CTools.umich.edu -> Enabling Tech Int -> Resources -> OER. Goes to dScribe.info@umich.edu mailing list and cc to person who submitted form. I'd like to keep this email notification even with the addition of storing it in a database.
 * 2) The form text may change from time to time. We're expecting to change the UMMS permission form and the permission to be recorded form this summer.
 * 3) These forms may be filled out by faculty, staff, students (for papers, presentations), or guest lecturers.
 * 4) All of the last of those 4 groups have U-M logins. We need to keep cosign login b/c the legal team wants us to be able to verify the identity of the person who submits the form. The check isn't in the code, but I do manually check that the person who logged in provided a matching umich email.
 * 5) We have paper (PDF) versions of these forms and the electronic. We need paper for convenience and non-UM people. In the future, we may have OM staff enter the paper ones in the system.

Versioning
Multiple versions of licenses should be storable in the system.

Perhaps a CCK license content type.

Content interaction
Should the license signed be a content owner define the default license for that content owner? Should a change in license affect the default license in the copyright holders works?

Granularity/Permission Inheritance
Are the permissions forms per rights holder or per resource. Not all resources are courses. Some are single items.

Single form for all subsequent material
Is it possible for a user to sign a single license for all subsequent contributed materials? How do we handle license changes in this case? Do we detect for version changes and prompt the user to sign an updated license?

Authentication
Kathleen noted that non-UM users will continue to sign paper forms which will be retained. So, non-UM users won't be completing the online license form. At least we won't require users to create UM Friend accounts just to sign a permission form. Can an admin "proxy" on their behalf?

Generalization
The current forms are very specific to the University. Should these forms be generalized so other institutions can use them too?