Yale University Library Preservation Metadata Task Force

Home >

PREMIS Metadata Set

PREMIS Metadata Set

• Object Entity
  • objectIdentifierSemantic Unit: objectIdentifier
    Obligation (PREMIS): Mandatory
    Obligation (Yale Full Profile): Mandatory
    Responsibility: Repository
    Generation: Automated
    Rationale: Needed to identify objects and to relate them to other objects, events, and rights.
    Usage Notes: Combination of type and value should be globally unique.
    Data Constraint: Container
    Repeatability: Repeatable
    Applicable Object Categories: Representation, File, Bitstream
    
    • objectIdentifierTypeSemantic Unit: objectIdentifierType
      Obligation (PREMIS): Mandatory
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Repository
      Generation: Automated
      Rationale: Designates the domain in which the objectIdentifier is unique.
      Usage Notes: Use identifier automatically created by the repository as the primary identifier. Implement a handle system for use as the primary identifier within the repository, and use this value: handle. The handle syntax should include a substring for the collection and sequential suffixes to indicate structural or derivative relationships among objects (e.g., yale.dp/ydc2593-001 where dp indicates the repository, ydc indicates the collection, and 001 indicates that the object is the original object submitted to the repository).
      Data Constraint: Controlled Vocabulary
      Repeatability: Not repeatable
      Applicable Object Categories: Representation, File, Bitstream
      
    • objectIdenifierValueSemantic Unit: objectIdenifierValue
      Obligation (PREMIS): Mandatory
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Repository
      Generation: Automated
      Rationale: Designates the value of the objectIdentifier.
      Usage Notes:
      Data Constraint: None
      Repeatability: Not repeatable
      Applicable Object Categories: Representation, File, Bitstream
      
  • preservationLevelSemantic Unit: preservationLevel
    Obligation (PREMIS): Mandatory
    Obligation (Yale Full Profile): Recommended
    Responsibility: Repository
    Generation: Semi-automated
    Rationale: Allows a range of local policies and practices to be applied differentially to objects or collections within the repository.
    Usage Notes: Use a controlled vocabulary. Assign at the repository or institution level rather than at the object level. Determine according to one or more of the following factors: cultural value, uniqueness, preservability, costs, etc. (e.g., Rutgers Libraries uses two different sets of values: (1) high, medium, low, or none and (2) full, or bitstream). Associate each value for preservationLevel with a profile that designates which semantic units are mandatory and how their values should be recorded. Profiles for higher preservation levels would have more stringent requirements. Requires policy decision by DPC.
    Data Constraint: Controlled Vocabulary
    Repeatability: Not repeatable
    Applicable Object Categories: Representation, File
    
  • objectCategorySemantic Unit: objectCategory
    Obligation (PREMIS): Mandatory
    Obligation (Yale Full Profile): Mandatory
    Responsibility: Repository
    Generation: Semi-automated
    Rationale: For repositories concerned with not only bit-level preservation, but also maintaining usable versions of intellectual entities over time, permits designation of significant properties of one or more sets of digital objects that make up an intellectual entity.
    Usage Notes: Use these values: Representation, File, Bitstream.
    Data Constraint: Controlled Vocabulary
    Repeatability: Not repeatable
    Applicable Object Categories: Representation, File, Bitstream
    
  • objectCharacteristicsSemantic Unit: objectCharacteristics
    Obligation (PREMIS): Mandatory
    Obligation (Yale Full Profile): Mandatory
    Responsibility: See components.
    Generation: See components.
    Rationale: Needed to describe such characteristics as composition level, fixity, size, format, significant properties, and inhibitors.
    Usage Notes: Used to record technical properties. Format-specific properties are out of scope for PREMIS.
    Data Constraint: Container
    Repeatability: Repeatable
    Applicable Object Categories: File, Bitstream
    
    • compositionLevelSemantic Unit: compositionLevel
      Obligation (PREMIS): Mandatory
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Creator or Submitter
      Generation: Semi-automated
      Rationale: Needed to decode or unbundle the object if it is compressed or encrypted.
      Usage Notes: Supply value even when object is uncompressed and unencrpyted, e.g., assign 0 for base level, 1 for compressed file, 2 for compressed and encrypted file.
      Data Constraint: Non-negative integer
      Repeatability: Not repeatable
      Applicable Object Categories: File, Bitstream
      
    • fixitySemantic Unit: fixity
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Creator, Submitter, or Repository
      Generation: Automated
      Rationale: Needed to guarantee object authenticity.
      Usage Notes: Investigate cost to generate and maintain message digests calculated by one or more algorithms. The PREMIS Data Dictionary recommends using two or more message digests calculated by different algorithms. Requires policy decision by DPC.
      Data Constraint: Container
      Repeatability: Repeatable
      Applicable Object Categories: File, Bitstream
      
      • messageDigestAlgorithmSemantic Unit: messageDigestAlgorithm
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Creator, Submitter, or Repository
        Generation: Automated
        Rationale: Needed to understand the digest value.
        Usage Notes: Use registry. Until a global registry becomes available, create and maintain a local registry of encryption algorithms by type: hash algorithms, symmetric algorithms, asymmetric algorithms. Use entries in the hash algorithm registry to populate this semantic unit. Requires policy decision by DPC.
        Data Constraint: Controlled Vocabulary
        Repeatability: Not repeatable
        Applicable Object Categories: File, Bitstream
        
      • messageDigestSemantic Unit: messageDigest
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Creator, Submitter, or Repository
        Generation: Automated
        Rationale: Required for comparison with value obtained in previous or subsequent fixity checks.
        Usage Notes:
        Data Constraint: None
        Repeatability: Not repeatable
        Applicable Object Categories: File, Bitstream
        
      • messageDigestOriginatorSemantic Unit: messageDigestOriginator
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Optional
        Responsibility: Creator, Submitter, or Repository
        Generation: Automated
        Rationale: Used to validate authenticity of message digests.
        Usage Notes: Record in Object entity or in Event entity.
        Data Constraint: None
        Repeatability: Not repeatable
        Applicable Object Categories: File, Bitstream
        
    • sizeSemantic Unit: size
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Creator, Submitter, or Repository
      Generation: Automated
      Rationale: Needed for server administration, planning, etc.
      Usage Notes: Record value obtained from format validation performed during ingest. Use bytes as unit of measurement.
      Data Constraint: Non-negative integer
      Repeatability: Not repeatable
      Applicable Object Categories: File, Bitstream
      
    • formatSemantic Unit: format
      Obligation (PREMIS): Mandatory
      Obligation (Yale Full Profile): Mandatory
      Responsibility: See components.
      Generation: Automated
      Rationale: Needed to identify format unambiguously and consistently.
      Usage Notes: Record by value in formatDesignation or by reference in formatRegistry. Requires policy decision by DPC.
      Data Constraint: Container
      Repeatability: Not repeatable
      Applicable Object Categories: File, Bitstream
      
      • formatDesignationSemantic Unit: formatDesignation
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Creator, Submitter, or Repository
        Generation: Automated
        Rationale: Needed to record name and version of the object format.
        Usage Notes: Use a controlled vocabulary.
        Data Constraint: Container
        Repeatability: Not repeatable
        Applicable Object Categories: File, Bitstream
        
        • formatNameSemantic Unit: formatName
          Obligation (PREMIS): Mandatory
          Obligation (Yale Full Profile): Mandatory
          Responsibility: Creator, Submitter, or Repository
          Generation: Automated
          Rationale: Needed to identify format by name.
          Usage Notes:
          Data Constraint: Controlled Vocabulary
          Repeatability: Not repeatable
          Applicable Object Categories: File, Bitstream
          
        • fomatVersionSemantic Unit: fomatVersion
          Obligation (PREMIS): Optional
          Obligation (Yale Full Profile): Mandatory
          Responsibility: Creator, Submitter, or Repository
          Generation: Automated
          Rationale: Needed to specify version of the format type.
          Usage Notes:
          Data Constraint: Controlled Vocabulary
          Repeatability: Not repeatable
          Applicable Object Categories: File, Bitstream
          
      • formatRegistrySemantic Unit: formatRegistry
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Semi-automated
        Rationale: Identifies source of format information. Entry for format in registry may provide additional information about the format.
        Usage Notes: Identify appropriate global registry or develop local registry. See Usage Notes for creatingApplication.
        Data Constraint: Container
        Repeatability: Repeatable
        Applicable Object Categories: File, Bitstream
        
        • formatRegistryNameSemantic Unit: formatRegistryName
          Obligation (PREMIS): Mandatory
          Obligation (Yale Full Profile): Mandatory
          Responsibility: Repository
          Generation: Semi-automated
          Rationale: Needed to reference the registry by name, URI, etc.
          Usage Notes: Use formal name, local name, or URI consistently. Requires policy decision by DPC.
          Data Constraint: None
          Repeatability: Not repeatable
          Applicable Object Categories: File, Bitstream
          
        • formatRegistryKeySemantic Unit: formatRegistryKey
          Obligation (PREMIS): Mandatory
          Obligation (Yale Full Profile): Mandatory
          Responsibility: Repository
          Generation: Semi-automated
          Rationale: Needed to uniquely cite the entry in the register.
          Usage Notes: Requires policy decision by DPC.
          Data Constraint: None
          Repeatability: Not repeatable
          Applicable Object Categories: File, Bitstream
          
        • formatRegistryRoleSemantic Unit: formatRegistryRole
          Obligation (PREMIS): Optional
          Obligation (Yale Full Profile): Recommended
          Responsibility: Repository
          Generation: Semi-automated
          Rationale: Indicates type of information provided by registry (e.g., specification, validation), if more than one is used.
          Usage Notes: Requires policy decision by DPC.
          Data Constraint: Controlled Vocabulary
          Repeatability: Not repeatable
          Applicable Object Categories: File, Bitstream
          
    • significantPropertiesSemantic Unit: significantProperties
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Recommended
      Responsibility: Creator, Submitter, or Repository
      Generation: Semi-automated
      Rationale: Used to record properties a repository plans to preserve.
      Usage Notes: Develop a local controlled vocabulary identifying properties, attributes, or features of objects. Investigate designation of significant properties by profile, e.g., a profile for records might include signatureInformation.
      Data Constraint: None
      Repeatability: Repeatable
      Applicable Object Categories: Representation, File, Bitstream
      
    • inhibitorsSemantic Unit: inhibitors
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Creator or Submitter
      Generation: See components.
      Rationale: Needed to decrypt files or bypass other protections, e.g., passwords.
      Usage Notes: Inhibitors may not be detected when a file is parsed. If applicable, require in Submission Information Package (SIP).
      Data Constraint: Container
      Repeatability: Repeatable
      Applicable Object Categories: File, Bitstream
      
      • inhibitorTypeSemantic Unit: inhibitorType
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Creator or Submitter
        Generation: Semi-automated
        Rationale: Needed to identify the inhibitor method employed on the object.
        Usage Notes: Use registry. Until a global registry becomes available, create and maintain a local registry of encryption algorithms by type: hash algorithms, symmetric algorithms, asymmetric algorithms. If encryption is used, use entries in the symmetric algorithm subregistry to populate this semantic unit. If password protection is used, use this value: password protection. Requires policy decision by DPC.
        Data Constraint: Controlled Vocabulary
        Repeatability: Not repeatable
        Applicable Object Categories: File, Bitstream
        
      • inhibitorTargetSemantic Unit: inhibitorTarget
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Creator or Submitter
        Generation: Semi-automated
        Rationale: Needed to identify the content or function is inhibited.
        Usage Notes: Use a controlled vocabulary.
        Data Constraint: Controlled Vocabulary
        Repeatability: Repeatable
        Applicable Object Categories: File, Bitstream
        
      • inhibitorKeySemantic Unit: inhibitorKey
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Creator or Submitter
        Generation: Semi-automated
        Rationale: Needed to override the inhibitor.
        Usage Notes: Integrate storage of keys with university-wide Public Key Infrastructure (PKI).
        Data Constraint: None
        Repeatability: Not repeatable
        Applicable Object Categories: File, Bitstream
        
  • creatingApplicationSemantic Unit: creatingApplication
    Obligation (PREMIS): Optional
    Obligation (Yale Full Profile): Mandatory
    Responsibility: Creator or Submitter
    Generation: Semi-automated
    Rationale: The creating application may have an effect on software and hardware compatibility even if the format is known (cf., Web pages created with Microsoft Front Page vs. Web pages created with Dreamweaver), which, in turn, is likely to affect migration.
    Usage Notes: Use registry. Until a global format registry becomes available, create and maintain a local registry of file formats with information, by function (create, render, identify, validate, etc.), on compatible software. For each application, provide a standard name, version, vendor, and system requirements. Use this registry to populate creatingApplication. Requires policy decision by DPC.
    Data Constraint: Container
    Repeatability: Repeatable
    Applicable Object Categories: Representation, File, Bitstream
    
    • creatingApplicationNameSemantic Unit: creatingApplicationName
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Creator or Submitter
      Generation: Semi-automated
      Rationale:
      Usage Notes:
      Data Constraint: Controlled Vocabulary
      Repeatability: Not repeatable
      Applicable Object Categories: Representation, File, Bitstream
      
    • creatingApplicationVersionSemantic Unit: creatingApplicationVersion
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Creator or Submitter
      Generation: Semi-automated
      Rationale: Compatibility may be specific to versions.
      Usage Notes:
      Data Constraint: None
      Repeatability: Not repeatable
      Applicable Object Categories: Representation, File, Bitstream
      
    • dateCreatedByApplicationSemantic Unit: dateCreatedByApplication
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Optional
      Responsibility: Creator or Submitter
      Generation: Semi-automated
      Rationale:
      Usage Notes: Express dates in the extended format with hyphens. Express times in UTC (Coordinated Universal Time) with the UTC designator ("Z").
      Data Constraint: ISO 8601
      Repeatability: Not repeatable
      Applicable Object Categories: Representation, File, Bitstream
      
  • originalNameSemantic Unit: originalName
    Obligation (PREMIS): Optional
    Obligation (Yale Full Profile): Recommended
    Responsibility: Creator or Submitter
    Generation: Automated
    Rationale: Used to relate a submitted object and to a derivative object held by the repository.
    Usage Notes: Use the file name designated in the Submission Information Package (SIP).
    Data Constraint: None
    Repeatability: Not repeatable
    Applicable Object Categories: File
    
  • storageSemantic Unit: storage
    Obligation (PREMIS): Mandatory
    Obligation (Yale Full Profile): Not Recommended
    Responsibility: Repository
    Generation: Semi-automated
    Rationale: Used to describe the location of two or more bit-wise identical copies of an object, directly under the repository's control, that have the same objectIdentifier and are managed as a unit by the repository.
    Usage Notes:
    Data Constraint: Container
    Repeatability: Repeatable
    Applicable Object Categories: File, Bitstream
    
    • contentLocationSemantic Unit: contentLocation
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Not Recommended
      Responsibility: Repository
      Generation: Semi-automated
      Rationale:
      Usage Notes: If a handle system is implemented, contentLocation is implicit in objectIdentifier.
      Data Constraint: Container
      Repeatability: Not repeatable
      Applicable Object Categories: File, Bitstream
      
      • contentLocationTypeSemantic Unit: contentLocationType
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Not Recommended
        Responsibility: Repository
        Generation: Semi-automated
        Rationale:
        Usage Notes: If a handle system is implemented, contentLocationType is identical to objectIdentifierType.
        Data Constraint: Controlled Vocabulary
        Repeatability: Not repeatable
        Applicable Object Categories: File, Bitstream
        
      • contentLocationValueSemantic Unit: contentLocationValue
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Not Recommended
        Responsibility: Repository
        Generation: Semi-automated
        Rationale:
        Usage Notes: If a handle system is implemented, the information needed to resolve handles to file locations is implicit in the handle system. Documentation for the handle system should be stored by the repository but does not need to be recorded in the metadata for each object.
        Data Constraint: None
        Repeatability: Not repeatable
        Applicable Object Categories: File, Bitstream
        
    • storageMediumSemantic Unit: storageMedium
      Obligation (PREMIS): Mandatory
      Obligation (Yale Full Profile): Not Recommended
      Responsibility: Repository
      Generation: Semi-automated
      Rationale:
      Usage Notes: Implicit. Determined by repository architecture.
      Data Constraint: Controlled Vocabulary
      Repeatability: Not repeatable
      Applicable Object Categories: File
      
  • environmentSemantic Unit: environment
    Obligation (PREMIS): Optional
    Obligation (Yale Full Profile): Mandatory
    Responsibility: See components.
    Generation: See components.
    Rationale: Used to describe dependent files and hardware/software combinations required to render or interact with content. Applies to Representation and File, i.e., if the repository has made a commitment to preserve usable versions of intellectual entities over time. May be omitted if the repository is only responsible for bit-level preservation.
    Usage Notes: Record information on functions supported by hardware and software in a registry, not in the metadata for each object. See Usage Notes for creatingApplication. Record information on dependent files in the metadata for each object.
    Data Constraint: Container
    Repeatability: Repeatable
    Applicable Object Categories: Representation, File, Bitstream
    
    • environmentCharacteristicSemantic Unit: environmentCharacteristic
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Not Recommended
      Responsibility: Creator or Submitter
      Generation: Semi-automated
      Rationale: Used to distinguish levels of functionality provided by hardware/software combinations if more than one combination supports a particular purpose.
      Usage Notes:
      Data Constraint: Controlled Vocabulary
      Repeatability: Not repeatable
      Applicable Object Categories: Representation, File, Bitstream
      
    • environmentPurposeSemantic Unit: environmentPurpose
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Not Recommended
      Responsibility: Creator or Submitter
      Generation: Semi-automated
      Rationale: Used to designate how an object may be manipulated using a particular combination of software and hardware.
      Usage Notes:
      Data Constraint: Controlled Vocabulary
      Repeatability: Repeatable
      Applicable Object Categories: Representation, File, Bitstream
      
    • environmentNoteSemantic Unit: environmentNote
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Not Recommended
      Responsibility: Creator or Submitter
      Generation: Manual
      Rationale: Used to provide information on the environment that cannot be recorded elsewhere.
      Usage Notes:
      Data Constraint: None
      Repeatability: Repeatable
      Applicable Object Categories: Representation, File, Bitstream
      
    • dependencySemantic Unit: dependency
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Creator or Submitter
      Generation: Semi-automated
      Rationale: Needed for complex objects that depend on other objects.
      Usage Notes: Use for non-executable components of an object, e.g., a font, style sheet, or schema. Do not use for software or hardware.
      Data Constraint: Container
      Repeatability: Repeatable
      Applicable Object Categories: Representation, File, Bitstream
      
      • dependencyNameSemantic Unit: dependencyName
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Creator, Submitter, or Repository
        Generation: Semi-automated
        Rationale: Clarifies nature of dependency if not made apparent by the dependencyIdentifier.
        Usage Notes:
        Data Constraint: None
        Repeatability: Repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
      • dependencyIdentifierSemantic Unit: dependencyIdentifier
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Semi-automated
        Rationale: Identifies a dependent object.
        Usage Notes: Use objectIdentifier of dependent object.
        Data Constraint: Container
        Repeatability: Repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
        • dependencyIdentifierTypeSemantic Unit: dependencyIdentifierType
          Obligation (PREMIS): Mandatory
          Obligation (Yale Full Profile): Mandatory
          Responsibility: Repository
          Generation: Semi-automated
          Rationale: Designates the domain in which the dependencyIdentifier is unique.
          Usage Notes:
          Data Constraint: Controlled Vocabulary
          Repeatability: Not repeatable
          Applicable Object Categories: Representation, File, Bitstream
          
        • dependencyIdentifierValueSemantic Unit: dependencyIdentifierValue
          Obligation (PREMIS): Mandatory
          Obligation (Yale Full Profile): Mandatory
          Responsibility: Repository
          Generation: Semi-automated
          Rationale: Designates the value of the dependencyIdentifier.
          Usage Notes:
          Data Constraint: None
          Repeatability: Not repeatable
          Applicable Object Categories: Representation, File, Bitstream
          
    • softwareSemantic Unit: software
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Not Recommended
      Responsibility: Creator, Submitter, or Repository
      Generation: Automated
      Rationale: The software needed to render the object
      Usage Notes: Software can be inferred from creatingApplication and does not need to recorded in the metadata for each object. See Usage Notes for creatingApplication.
      Data Constraint: Container
      Repeatability: Repeatable
      Applicable Object Categories: Representation, File, Bitstream
      
      • swNameSemantic Unit: swName
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Not Recommended
        Responsibility: Creator, Submitter, or Repository
        Generation: Automated
        Rationale: Needed to identify the manufacturer and name of software product.
        Usage Notes:
        Data Constraint: None
        Repeatability: Not repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
      • swVersionSemantic Unit: swVersion
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Not Recommended
        Responsibility: Creator, Submitter, or Repository
        Generation: Automated
        Rationale: Needed to identify the version number of the software product.
        Usage Notes:
        Data Constraint: None
        Repeatability: Repeatable (File); Not repeatable (Representation, Bitstream)
        Applicable Object Categories: Representation, File, Bitstream
        
      • swTypeSemantic Unit: swType
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Not Recommended
        Responsibility: Creator, Submitter, or Repository
        Generation: Automated
        Rationale: Needed to identify the role of the software product e.g., operating system, renderer, driver, etc.
        Usage Notes:
        Data Constraint: Controlled Vocabulary
        Repeatability: Not repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
      • swOtherInformationSemantic Unit: swOtherInformation
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Not Recommended
        Responsibility: Creator, Submitter, or Repository
        Generation: Automated
        Rationale: Used to describe additional requirements or instructions related to the software product.
        Usage Notes:
        Data Constraint: None
        Repeatability: Repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
      • swDependencySemantic Unit: swDependency
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Not Recommended
        Responsibility: Creator, Submitter, or Repository
        Generation: Automated
        Rationale: Used to identify and additonal software needed by that in swName.
        Usage Notes:
        Data Constraint: None
        Repeatability: Repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
    • hardwareSemantic Unit: hardware
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Not Recommended
      Responsibility: Creator, Submitter, or Repository
      Generation: Automated
      Rationale: The hardware needed to render or use the object
      Usage Notes: Hardware can be inferred from creatingApplication and does not need to be recorded in the metadata for each object. See Usage Notes for creatingApplication.
      Data Constraint: Container
      Repeatability: Repeatable
      Applicable Object Categories: Representation, File, Bitstream
      
      • hwNameSemantic Unit: hwName
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Not Recommended
        Responsibility: Creator, Submitter, or Repository
        Generation: Automated
        Rationale: Needed to identify the manufacturer, model and version of hardware product.
        Usage Notes:
        Data Constraint: None
        Repeatability: Not repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
      • hwTypeSemantic Unit: hwType
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Not Recommended
        Responsibility: Creator, Submitter, or Repository
        Generation: Automated
        Rationale: Needed to identify the class or category of the hardware.
        Usage Notes:
        Data Constraint: Controlled Vocabulary
        Repeatability: Not repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
      • hwOtherInformationSemantic Unit: hwOtherInformation
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Not Recommended
        Responsibility: Creator, Submitter, or Repository
        Generation: Semi-automated
        Rationale: Used to describe additional requirements or instructions related to the hardware product.
        Usage Notes:
        Data Constraint: None
        Repeatability: Repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
    • signatureinformationSemantic Unit: signatureinformation
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Optional
      Responsibility: Repository
      Generation: See components.
      Rationale: Used to confirm the origin and integrity of objects signed by the repository.
      Usage Notes: Do not use to record information about digital signatures that authenticate agents; use the Event Entity instead.
      Data Constraint: Container
      Repeatability: Repeatable
      Applicable Object Categories: File, Bitstream
      
      • signatureinformationEncodingSemantic Unit: signatureinformationEncoding
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Automated
        Rationale: Used to record encoding of signatureValue and keyInformation.
        Usage Notes: Use registry.
        Data Constraint: Controlled Vocabulary
        Repeatability: Not repeatable
        Applicable Object Categories: File, Bitstream
        
      • signerSemantic Unit: signer
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Optional
        Responsibility: Repository
        Generation: Semi-automated
        Rationale: Needed to determine who created the signature.
        Usage Notes: Use the name provided in the Submission Information Package (SIP).
        Data Constraint: None
        Repeatability: Not repeatable
        Applicable Object Categories: File, Bitstream
        
      • signatureMethodSemantic Unit: signatureMethod
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Automated
        Rationale: Needed for signature encryption and validation.
        Usage Notes: Use registry. Create and maintain a local registry of encryption algorithms by type: hash algorithms, symmetric algorithms, asymmetric algorithms. Use entries in the asymmetric algorithm registry and hash algorithm registry to populate signatureMethod. Record the encryption algorithm for the signature first (the asymmetric algorithm), followed by a hyphen, followed by the hash algorithm, e.g., DSA-SHA1. Requires policy decision by DPC.
        Data Constraint: Controlled Vocabulary
        Repeatability: Not repeatable
        Applicable Object Categories: File, Bitstream
        
      • signatureValueSemantic Unit: signatureValue
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Automated
        Rationale: The value of the digital signature
        Usage Notes:
        Data Constraint: None
        Repeatability: Not repeatable
        Applicable Object Categories: File, Bitstream
        
      • signatureValidationRulesSemantic Unit: signatureValidationRules
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Automated
        Rationale: Used to maintain documentation on signature algorithms, canonicalization algorithms, transform algorithms, etc.
        Usage Notes: May be a pointer to external documentation. See <http://www.w3.org/TR/xmldsig-core/>. Requires policy decision by DPC.
        Data Constraint: None
        Repeatability: Not repeatable
        Applicable Object Categories: File, Bitstream
        
      • signaturePropertiesSemantic Unit: signatureProperties
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Optional
        Responsibility: Repository
        Generation: Automated
        Rationale: Used to verify the authenticity of the signature.
        Usage Notes: Define suitably granular structure for time of signature generation, serial number of cryptographic hardware used, etc., as needed. Requires policy decision by DPC.
        Data Constraint: None
        Repeatability: Repeatable
        Applicable Object Categories: File, Bitstream
        
      • keyinformationSemantic Unit: keyinformation
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Optional
        Responsibility: Repository
        Generation: Automated
        Rationale: Used to record information about the signer's public key, for comparison with the and verifiation of the digital signature.
        Usage Notes: See proposed change at <http://www.loc.gov/standards/premis/changes.html>.
        Data Constraint: Container
        Repeatability: Not repeatable
        Applicable Object Categories: File, Bitstream
        
        • keyTypeSemantic Unit: keyType
          Obligation (PREMIS): Mandatory
          Obligation (Yale Full Profile): Mandatory
          Responsibility: Repository
          Generation: Automated
          Rationale: Used to record the encryption algorithm or certification method for authenticating the signer's public key.
          Usage Notes: Use registry. Requires policy decision by DPC.
          Data Constraint: Controlled Vocabulary
          Repeatability: Not repeatable
          Applicable Object Categories: File, Bitstream
          
        • keyValueSemantic Unit: keyValue
          Obligation (PREMIS): Mandatory
          Obligation (Yale Full Profile): Mandatory
          Responsibility: Repository
          Generation: Automated
          Rationale: The value of the signer's public key is needed for comparison with the signature.
          Usage Notes:
          Data Constraint: None
          Repeatability: Not repeatable
          Applicable Object Categories: File, Bitstream
          
        • keyVerificationInformationSemantic Unit: keyVerificationInformation
          Obligation (PREMIS): Optional
          Obligation (Yale Full Profile): Optional
          Responsibility: Repository
          Generation: Automated
          Rationale: Additional information used to verify the signer's key
          Usage Notes: May be used to record information about certificates, etc. If possible, use keyType instead. Requires policy decision by DPC.
          Data Constraint: None
          Repeatability: Not repeatable
          Applicable Object Categories: File, Bitstream
          
    • relationshipSemantic Unit: relationship
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Creator, Submitter, or Repository
      Generation: See components.
      Rationale: Needed to represent relationships between objects.
      Usage Notes: Record all relevant relationships.
      Data Constraint: Container
      Repeatability: Repeatable
      Applicable Object Categories: Representation, File, Bitstream
      
      • relationshipTypeSemantic Unit: relationshipType
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Creator, Submitter, or Repository
        Generation: Semi-automated
        Rationale: Structural or derivational relationship between objects
        Usage Notes: Develop a local controlled vocabulary of relationships.
        Data Constraint: Controlled Vocabulary
        Repeatability: Not repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
      • relationshipSubtypeSemantic Unit: relationshipSubtype
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Creator, Submitter, or Repository
        Generation: Semi-automated
        Rationale: Describes the role of each object in the relationship.
        Usage Notes: Include in a local controlled vocabulary of relationships.
        Data Constraint: Controlled Vocabulary
        Repeatability: Not repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
      • relatedObjectidentificationSemantic Unit: relatedObjectidentification
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Automated
        Rationale: Identifies related objects.
        Usage Notes: Use objectIdentifier of related resource.
        Data Constraint: Container
        Repeatability: Repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
        • relatedObjectidentificationTypeSemantic Unit: relatedObjectidentificationType
          Obligation (PREMIS): Mandatory
          Obligation (Yale Full Profile): Mandatory
          Responsibility: Repository
          Generation: Automated
          Rationale: Designates the domain in which the relatedObjectIdentification is unique.
          Usage Notes:
          Data Constraint: Controlled Vocabulary
          Repeatability: Not repeatable
          Applicable Object Categories: Representation, File, Bitstream
          
        • relatedObjectIdentifierValueSemantic Unit: relatedObjectIdentifierValue
          Obligation (PREMIS): Mandatory
          Obligation (Yale Full Profile): Mandatory
          Responsibility: Repository
          Generation: Automated
          Rationale: Designates the value of the relatedObjectIdentification.
          Usage Notes:
          Data Constraint: None
          Repeatability: Not repeatable
          Applicable Object Categories: Representation, File, Bitstream
          
        • relatedObjectSequenceSemantic Unit: relatedObjectSequence
          Obligation (PREMIS): Mandatory
          Obligation (Yale Full Profile): Mandatory
          Responsibility: Repository
          Generation: Automated
          Rationale: Needed to know the order of components or files.
          Usage Notes: If there is only one related object, assign the value 0 (zero). If objects are unordered, assign each the same value.
          Data Constraint: None
          Repeatability: Not repeatable
          Applicable Object Categories: Representation, File, Bitstream
          
      • relatedEventIdentificationSemantic Unit: relatedEventIdentification
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Automated
        Rationale: Used to identify an event that relates the object to a second object, e.g., migration.
        Usage Notes: Use eventIdentifier of related event.
        Data Constraint: Container
        Repeatability: Repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
        • relatedEventidentifierTypeSemantic Unit: relatedEventidentifierType
          Obligation (PREMIS): Mandatory
          Obligation (Yale Full Profile): Mandatory
          Responsibility: Repository
          Generation: Automated
          Rationale: Designates the domain in which the relatedEventIdentification is unique.
          Usage Notes:
          Data Constraint: Controlled Vocabulary
          Repeatability: Not repeatable
          Applicable Object Categories: Representation, File, Bitstream
          
        • relatedEventidentifierValueSemantic Unit: relatedEventidentifierValue
          Obligation (PREMIS): Mandatory
          Obligation (Yale Full Profile): Mandatory
          Responsibility: Repository
          Generation: Automated
          Rationale: Designates the value of the relatedEventIdentifier
          Usage Notes:
          Data Constraint: Controlled Vocabulary
          Repeatability: Not repeatable
          Applicable Object Categories: Representation, File, Bitstream
          
        • relatedEventSequenceSemantic Unit: relatedEventSequence
          Obligation (PREMIS): Optional
          Obligation (Yale Full Profile): Mandatory
          Responsibility: Repository
          Generation: Automated
          Rationale: Needed to know the order of events.
          Usage Notes: If there is only one related event, assign the value 0 (zero). If events are unordered, assign each the same value.
          Data Constraint: None
          Repeatability: Not repeatable
          Applicable Object Categories: Representation, File, Bitstream
          
    • linkingEventIdentifierSemantic Unit: linkingEventIdentifier
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Repository
      Generation: Automated
      Rationale: Used to identify an event that does not result in the creation of a second object, e.g., validation.
      Usage Notes: Use eventIdentifier of linking event.
      Data Constraint: Container
      Repeatability: Repeatable
      Applicable Object Categories: Representation, File, Bitstream
      
      • linkingEventIdentifierTypeSemantic Unit: linkingEventIdentifierType
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Automated
        Rationale: Designates the domain in which the linkingEventIdentifier is unique.
        Usage Notes:
        Data Constraint: Controlled Vocabulary
        Repeatability: Not repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
      • linkingEventIdentifierValueSemantic Unit: linkingEventIdentifierValue
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Automated
        Rationale: Designates the value of the linkingEventIdentifier.
        Usage Notes:
        Data Constraint: Controlled Vocabulary
        Repeatability: Not repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
    • linkingIntellectualEntityIdentifierSemantic Unit: linkingIntellectualEntityIdentifier
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Optional
      Responsibility: Creator, Submitter, or Repository
      Generation: Automated
      Rationale: Used to link an object to another object or collection that represents the same intellectual entity or a related intellectual entity.
      Usage Notes: Use to identify an object whose content is related to the object designated by the objectIdentifier. Optionally, use to identify a metadata record for the object designated by the objectIdentifier. Requires policy decision by DPC.
      Data Constraint: Container
      Repeatability: Repeatable
      Applicable Object Categories: Representation, File, Bitstream
      
      • linkingIntellectualEntityTypeSemantic Unit: linkingIntellectualEntityType
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Automated
        Rationale: Designates the domain in which the linkingIntellectualEntityIdentifier is unique.
        Usage Notes:
        Data Constraint: Controlled Vocabulary
        Repeatability: Not repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
      • linkingIntellectualEntityValueSemantic Unit: linkingIntellectualEntityValue
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Automated
        Rationale: Designates the value of the linkingIntellectualEntityIdentifier.
        Usage Notes:
        Data Constraint: None
        Repeatability: Not repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
    • linkingPermissionStatementIdentifierSemantic Unit: linkingPermissionStatementIdentifier
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Recommended
      Responsibility: Repository
      Generation: Automated
      Rationale: Used to link an object to a permission statement.
      Usage Notes: Use permissionStatementIdentifier.
      Data Constraint: Container
      Repeatability: Repeatable
      Applicable Object Categories: Representation, File, Bitstream
      
      • linkingPermissionStatementIdentifierTypeSemantic Unit: linkingPermissionStatementIdentifierType
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Automated
        Rationale: Designates the domain in which the linkingPermissionStatementIdentifier is unique.
        Usage Notes:
        Data Constraint: Controlled Vocabulary
        Repeatability: Not repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
      • linkingPermissionStatementIdentifierValueSemantic Unit: linkingPermissionStatementIdentifierValue
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Automated
        Rationale: Designates the value of the linkingPermissionStatementIdentifer.
        Usage Notes:
        Data Constraint: None
        Repeatability: Not repeatable
        Applicable Object Categories: Representation, File, Bitstream
        
• Event Entity
  • eventIdentifierSemantic Unit: eventIdentifier
    Obligation (PREMIS): Mandatory
    Obligation (Yale Full Profile): Mandatory
    Responsibility: Repository
    Generation: Automated
    Rationale: Needed to identify events and to relate them to objects and agents.
    Usage Notes:
    Data Constraint: None
    Repeatability: Not repeatable
    
    • eventIdentifierTypeSemantic Unit: eventIdentifierType
      Obligation (PREMIS): Mandatory
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Repository
      Generation: Automated
      Rationale: Designates the domain in which the eventIdentifier is unique.
      Usage Notes: Use identifiers automatically created by the repository. If information needs to be recorded on events outside the repository, use a registry of repositories. (Each repository is likely to implement its own numbering system for events.)
      Data Constraint: None
      Repeatability: Not repeatable
      
    • eventIdentifierValueSemantic Unit: eventIdentifierValue
      Obligation (PREMIS): Mandatory
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Repository
      Generation: Automated
      Rationale: Designates the value of the eventIdentifier.
      Usage Notes:
      Data Constraint: None
      Repeatability: Not repeatable
      
  • eventTypeSemantic Unit: eventType
    Obligation (PREMIS): Mandatory
    Obligation (Yale Full Profile): Mandatory
    Responsibility: Repository
    Generation: Semi-automated
    Rationale: Used to categorize events that affect the preservation of digital objects. Not limited to preservation treatments.
    Usage Notes: Develop local controlled vocabulary of event types. Requires policy decision by DPC.
    Data Constraint: Controlled Vocabulary
    Repeatability: Not repeatable
    
  • eventDateTimeSemantic Unit: eventDateTime
    Obligation (PREMIS): Mandatory
    Obligation (Yale Full Profile): Mandatory
    Responsibility: Repository
    Generation: Automated
    Rationale: Required for digital provenance.
    Usage Notes: Express dates in the extended format with hyphens. Express times in UTC (Coordinated Universal Time) with the UTC designator ("Z").
    Data Constraint: ISO 8601
    Repeatability: Not repeatable
    
  • eventDetailSemantic Unit: eventDetail
    Obligation (PREMIS): Optional
    Obligation (Yale Full Profile): Not Recommended
    Responsibility: Repository
    Generation: Manual
    Rationale: Additional information about an event; not intended to be machine processible
    Usage Notes:
    Data Constraint: None
    Repeatability: Not repeatable
    
  • eventOutcomeInformationSemantic Unit: eventOutcomeInformation
    Obligation (PREMIS): Optional
    Obligation (Yale Full Profile): Mandatory
    Responsibility: Repository
    Generation: See components.
    Rationale: Machine-processible information about event outcomes
    Usage Notes:
    Data Constraint: None
    Repeatability: Repeatable
    
    • eventOutcomeSemantic Unit: eventOutcome
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Repository
      Generation: Automated
      Rationale: Coded representation of the outcome of an event
      Usage Notes: Develop local controlled vocabulary of event outcomes. Requires policy decision by DPC.
      Data Constraint: Controlled Vocabulary
      Repeatability: Not repeatable
      
    • eventOutcomeDetailSemantic Unit: eventOutcomeDetail
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Recommended
      Responsibility: Repository
      Generation: Semi-automated
      Rationale: Detailed description of the outcome of an event; may be used to record or to point to event logs
      Usage Notes: Establish guidelines for what to record for each event type. Requires policy decision by DPC.
      Data Constraint: None
      Repeatability: Not repeatable
      
  • linkingAgentIdentiferSemantic Unit: linkingAgentIdentifer
    Obligation (PREMIS): Optional
    Obligation (Yale Full Profile): Mandatory
    Responsibility: Repository
    Generation: Automated
    Rationale: Required for digital provenance.
    Usage Notes: Use agentIdentifier.
    Data Constraint: None
    Repeatability: Repeatable
    
    • linkingAgentIdentiferTypeSemantic Unit: linkingAgentIdentiferType
      Obligation (PREMIS): Mandatory
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Repository
      Generation: Automated
      Rationale: Designates the domain in which the agentIdentifier is unique.
      Usage Notes:
      Data Constraint: Controlled Vocabulary
      Repeatability: Not repeatable
      
    • linkingAgentIdentifierValueSemantic Unit: linkingAgentIdentifierValue
      Obligation (PREMIS): Mandatory
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Repository
      Generation: Automated
      Rationale: Designates the value of the agentIdentifier.
      Usage Notes:
      Data Constraint: None
      Repeatability: Not repeatable
      
    • linkingAgentRoleSemantic Unit: linkingAgentRole
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Recommended
      Responsibility: Repository
      Generation: Automated
      Rationale: Used to disambiguate agent role if more than one agent is associated with an event or if the role of the agent is not evident from the eventType.
      Usage Notes:
      Data Constraint: Controlled Vocabulary
      Repeatability: Repeatable
      
  • linkingObjectIdentifierSemantic Unit: linkingObjectIdentifier
    Obligation (PREMIS): Optional
    Obligation (Yale Full Profile): Mandatory
    Responsibility: Repository
    Generation: Automated
    Rationale: Required for digital provenance.
    Usage Notes: Use objectIdentifier.
    Data Constraint: None
    Repeatability: Repeatable
    
    • linkingObjectIdentifierTypeSemantic Unit: linkingObjectIdentifierType
      Obligation (PREMIS): Mandatory
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Repository
      Generation: Automated
      Rationale: Designates the domain in which the objectIdentifier is unique.
      Usage Notes:
      Data Constraint: Controlled Vocabulary
      Repeatability: Not repeatable
      
    • linkingObjectIdentifierValueSemantic Unit: linkingObjectIdentifierValue
      Obligation (PREMIS): Mandatory
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Repository
      Generation: Automated
      Rationale: Designates the value of the objectIdentifier.
      Usage Notes:
      Data Constraint: None
      Repeatability: Not repeatable
      
• Agent Entity
  • agentIdentifierSemantic Unit: agentIdentifier
    Obligation (PREMIS): Mandatory
    Obligation (Yale Full Profile): Mandatory
    Responsibility: Repository
    Generation: Automated
    Rationale: Needed to identify agents, to relate them to events, and to designate their permissions.
    Usage Notes: Create a local registry; create a registry for external agents as needed. For the local registry, use Yale University netIDs and integrate with CAS.
    Data Constraint: None
    Repeatability: Repeatable
    
    • agentIdentifierTypeSemantic Unit: agentIdentifierType
      Obligation (PREMIS): Mandatory
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Repository
      Generation: Automated
      Rationale: Designates the domain in which the agentIdentifier is unique.
      Usage Notes:
      Data Constraint: Controlled Vocabulary
      Repeatability: Not repeatable
      
    • agentIdentifierValueSemantic Unit: agentIdentifierValue
      Obligation (PREMIS): Mandatory
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Repository
      Generation: Automated
      Rationale: Designates the value of the agentIdentifier.
      Usage Notes:
      Data Constraint: None
      Repeatability: Not repeatable
      
  • agentNameSemantic Unit: agentName
    Obligation (PREMIS): Optional
    Obligation (Yale Full Profile): Recommended
    Responsibility: Repository
    Generation: Automated
    Rationale: The agent may not be known by his/her agentIdentifier.
    Usage Notes: Record the agent's name in the event that the agent's CAS account does not persist over the lifetime of objects related to events in which the agent played a role.
    Data Constraint: None
    Repeatability: Repeatable
    
  • agentTypeSemantic Unit: agentType
    Obligation (PREMIS): Optional
    Obligation (Yale Full Profile): Recommended
    Responsibility: Repository
    Generation: Automated
    Rationale: High-level characterization of the type of agent, useful for filtering, etc.
    Usage Notes: Develop a local controlled vocabulary of agent types.
    Data Constraint: Controlled Vocabulary
    Repeatability: Not repeatable
    
• Rights Entity
  • permissionStatementSemantic Unit: permissionStatement
    Obligation (PREMIS): Optional
    Obligation (Yale Full Profile): Mandatory
    Responsibility: Repository
    Generation: Automated
    Rationale: Contains all other semantic units in the Rights Entity. Used to designate the rights of agents with respect to objects held by the repository.
    Usage Notes: If a permissionStatement is not provided, then a linkingPermissionStatementIdentifier is not provided in the Object Entity. Investigate objects or collections, if any, for which a permissionStatement is required and those for which permissions may be set by institution-wide policy.
    Data Constraint: Container
    Repeatability: Repeatable
    
    • permissionStatementIdentifierSemantic Unit: permissionStatementIdentifier
      Obligation (PREMIS): Mandatory
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Repository
      Generation: Automated
      Rationale: Needed to provide unique identifer for permission statement so that it can be related to obects, agents and events.
      Usage Notes:
      Data Constraint: Container
      Repeatability: Not repeatable
      
      • permissionStatementIdentifierTypeSemantic Unit: permissionStatementIdentifierType
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Automated
        Rationale: Designates domain in which the permissionStatementIdentifier is unique.
        Usage Notes: Consider rights management standards informed by the Digital Millennium Copyright Act. Also, see JISC. Digital Rights Management: Final Report <http://www.intrallect.com/drm-study/DRMFinalReportv2.pdf>
        Data Constraint: Controlled Vocabulary
        Repeatability: Not repeatable
        
      • permissionStatementIdentifierValueSemantic Unit: permissionStatementIdentifierValue
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Automated
        Rationale: Designates value of the permissionStatementIdentifier.
        Usage Notes:
        Data Constraint: None
        Repeatability: Not repeatable
        
    • linkingObjectSemantic Unit: linkingObject
      Obligation (PREMIS): Mandatory
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Repository
      Generation: Automated
      Rationale: Identifies the object(s) related to the permission statement.
      Usage Notes: Investigate the appropriate level for designating permissions, e.g., by object, file type, agent, or collection.
      Data Constraint: None
      Repeatability: Repeatable
      
    • grantingAgentSemantic Unit: grantingAgent
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Recommended
      Responsibility: Repository
      Generation: Automated
      Rationale: Identifies the agent granting permission.
      Usage Notes: Use agentIdentifier.
      Data Constraint: None
      Repeatability: Repeatable
      
    • grantingAgreementSemantic Unit: grantingAgreement
      Obligation (PREMIS): Optional
      Obligation (Yale Full Profile): Recommended
      Responsibility: Creator, Submitter, Repository
      Generation: Automated
      Rationale: Refers to a document or contract recording the granting of permission.
      Usage Notes: For objects or collections for which a permissionStatement is required, include a grantingAgreement in the Submission Information Package (SIP).
      Data Constraint: None
      Repeatability: Not repeatable
      
      • grantingAgreementIdentificationSemantic Unit: grantingAgreementIdentification
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Recommended
        Responsibility: Repository
        Generation: Automated
        Rationale: Identifies the agreement that grants permissions.
        Usage Notes: If a permissionStatement is required, ingest the Submission Information Package (SIP) and use the objectIdentifier of the SIP.
        Data Constraint: None
        Repeatability: Not repeatable
        
      • grantingAgreementInformationSemantic Unit: grantingAgreementInformation
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Recommended
        Responsibility: Creator, Submitter, Repository
        Generation: Automated
        Rationale: Text describing the agreement
        Usage Notes: If a permissionStatement is required, optionally paraphrase or quote the text of the grantingAgreement provided in the Submission Information Package (SIP).
        Data Constraint: None
        Repeatability: Not repeatable
        
    • permissionGrantedSemantic Unit: permissionGranted
      Obligation (PREMIS): Mandatory
      Obligation (Yale Full Profile): Mandatory
      Responsibility: Repository
      Generation: Automated
      Rationale: Identifies the allowed actions per permission.
      Usage Notes:
      Data Constraint: None
      Repeatability: Repeatable
      
      • actSemantic Unit: act
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Automated
        Rationale: Details the actions that are allowed.
        Usage Notes: Develop a local controlled vocabulary of acceptable acts. Optionally, define a single controlled vocabulary for eventType and act.
        Data Constraint: Controlled Vocabulary
        Repeatability: Not repeatable
        
      • restrictionSemantic Unit: restriction
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Recommended
        Responsibility: Repository
        Generation: Automated
        Rationale: Identifies the limits on actions (e.g., the number of copies that can be made).
        Usage Notes: Include any restrictions in a local controlled vocabulary of acceptable acts.
        Data Constraint: None
        Repeatability: Repeatable
        
      • termOfGrantSemantic Unit: termOfGrant
        Obligation (PREMIS): Mandatory
        Obligation (Yale Full Profile): Mandatory
        Responsibility: Repository
        Generation: Automated
        Rationale: Declares the term of the grant.
        Usage Notes:
        Data Constraint: None
        Repeatability: Not repeatable
        
        • startDateSemantic Unit: startDate
          Obligation (PREMIS): Mandatory
          Obligation (Yale Full Profile): Mandatory
          Responsibility: Repository
          Generation: Automated
          Rationale: Needed to know the start of term.
          Usage Notes: Record if term of permissions is time bounded. The datatype of this semantic unit is xs:date, which has year, month, and day properties, plus an optional timezone-valued timezone property. Express as a nontimezoned value in the extended format: YYYY-MM-DD. Year, month, and day are required.
          Data Constraint: ISO 8601
          Repeatability: Not repeatable
          
        • endDateSemantic Unit: endDate
          Obligation (PREMIS): Mandatory
          Obligation (Yale Full Profile): Mandatory
          Responsibility: Repository
          Generation: Automated
          Rationale: Needed to know end of term.
          Usage Notes: Record if term of permissions is time bounded. The datatype of this semantic unit is xs:date, which has year, month, and day properties, plus an optional timezone-valued timezone property. Express as a nontimezoned value in the extended format: YYYY-MM-DD. Year, month, and day are required.
          Data Constraint: ISO 8601
          Repeatability: Not repeatable
          
      • permissionNoteSemantic Unit: permissionNote
        Obligation (PREMIS): Optional
        Obligation (Yale Full Profile): Recommended
        Responsibility: Repository
        Generation: Automated
        Rationale: Provides additional information on permissions.
        Usage Notes: Use only if information cannot be recorded elsewhere.
        Data Constraint: None
        Repeatability: Repeatable
        

Tree created with Javascript Tree.

Search / Contact Us / Yale University Library / Yale University / YaleInfo

© 2006 Yale University Library
Last modified 12/13/2006
Send comments to Matthew Beacom