ADMIN & EMEDIA LABELS |
METADATA DESCRIPTORS |
METADATA ATTRIBUTES |
|
|
drml-What type of requirement |
|
[for cataloging] |
|
|
FOR THE LICENSEE... WHAT TYPE OF REQUIREMENT identifies the exact nature of what an end user must do to be able to use a media item while meeting the permissions and contraints associated with it. Use drm_lic_requirements_context to identify the specifics, amounts and parameters. |
|
The series of metadata fields tracking licensing arrangements assists the UEN DMS Service in managing and tracking compliance with distribution rights, repurposing rights, and expiration dates. FOR THE LICENSEE... UMAP takes into consideration the following components and analyses to assist the UEN DMS Service in managing and tracking compliance with distribution rights, repurposing rights, and expiration dates.... 1. Copyright (creation/publication dates & status, copyright owner), 2. Rights Stakeholders (creators, owners, vendors, licensees, and distributors), 3. Permissions (available rights to the licensees; "What end users can do with a media item?"), 4. Constraints (limitations on available rights to the licensees; "What end users can't do with a media item?"), and 5. Compliance Requirements/Obligations (licensee obligations in order to comply with Permissions and Contraints that are set forth; "What must an end user do to be able to use a media item?" ). 6. End Users (parties expected to consume or use the media items), 7. Citation (a bibliographic-like attribution associated with the origins of a content or media item) FOR THE LICENSEE COMPLIANCE REQUIREMENTS/OBLIGATIONS DISCUSSION... COMPLIANCE REQUIREMENTS/OBLIGATIONS typically include the following components... Compliance Requirements metadata specifies the obligations needed to exercise the Permission (e.g., Pay $5 each time you Play the video; or Publish an attribution or credit statement). The information found under "Compliance Requirements/Obligations" answers the question "What must an end user do to be able to use a media item?" 1. ASSET UNIQUE ID and TITLE 2. FEE - indicates a set of requirements for payments for usage. a. PrePay: The amount due prior to the granting/use of the rights. Use Payment entity. Temporal constraints may also be used. b. PostPay: The amount due after the use of the rights. c. PerUse: The amount due for each use of the granted rights. d. Payment: The amount due for each use of the granted rights. 3. INTERACTIONS - indicates a set of requirements on user interactions. a. Accept: User must view and agree to textual information. b. Register: User must register their details with a service provider. 4. USAGE - indicates a set of requirements on the use of the asset. a. Attribution: The use of the asset must always include attribution of the asset owners, e.g., used by permission of KUED-TV for non-commerical, educational purposes only. b. Tracked: The User will be tracked for their use of the asset. |
|
|
repeating |
|
255 |
|
FOR THE LICENSEE... Best practice is to select one or more terms from the picklist. Here is more info explaining what each term in the picklist means... |
|
Fee Waived: Articulates that no payment is required under agreed upon conditions, e.g., "Use fees waived because of restriction to classroom playback only" Fee Pre-Paid: Specifies the amount due prior to the granting/use of the rights. Temporal constraints may also be used. Fee Post-Paid: Specifies the amount due after the use of the rights. Fee Per-Use: Specifies the amount due for each use of the granted rights. Requires Attribution: Articulates that the use of the asset must always include attribution or crediting of the media item's owners/publishers/distributors (as specified under drm_lic_requirements_context). Requires Tracking: Indicates that the end user will be tracked for their uses of a media item, e.g., "8 downloads reported" or "10 plays reported" Doesn't Matter: Does not apply. Use drm_lic_requirements_context to identify the specifics, amounts and parameters. |
|
Fee Waived Fee Pre-Paid Fee Post-Paid Fee Per-Use Requires Attribution Requires Tracking Doesn't Matter |
|
The series of metadata fields tracking licensing arrangements assists the UEN DMS Service in managing and tracking compliance with distribution rights, repurposing rights, and expiration dates. |
|
The series of metadata fields tracking licensing arrangements assists the UEN DMS Service in managing and tracking compliance with distribution rights, repurposing rights, and expiration dates. |
|
|
See picklist. |