Category: Metadata Standards

PREMIS

Also known as: PREMIS, Preservation Metadata: Implementation Strategies, PREMIS Data Dictionary, PREMIS Data Dictionary for Preservation Metadata

Simply put

PREMIS is an internationally used standard that defines the metadata needed to preserve digital objects over time and keep them usable. It provides a shared vocabulary and structure so that organizations can describe what a digital object is, what has happened to it, and how it can continue to be accessed and trusted in the future.

Formal definition

PREMIS (Preservation Metadata: Implementation Strategies) is expressed through the PREMIS Data Dictionary for Preservation Metadata, which specifies a core set of preservation metadata that most repositories of digital objects would typically require to support long-term digital preservation. Its stated primary uses include repository design, repository evaluation, and the exchange of archived information packages between systems. PREMIS focuses specifically on preservation metadata for digital objects rather than on descriptive cataloguing, rights management, or general records classification, and it is commonly implemented alongside other metadata and packaging standards depending on organizational and repository context.

Why it matters

Digital objects are inherently fragile. File formats fall out of support, storage media degrade, software dependencies disappear, and the chain of actions performed on an object over time can become obscured. Without structured information about what a digital object is, what has happened to it, and what is required to render it, an organization may retain the bits of a file yet lose the ability to trust or use it. PREMIS matters because it provides a shared vocabulary and structure for the preservation metadata that supports keeping digital objects usable and trustworthy over the long term, which is a distinct concern from descriptive cataloguing or day-to-day access.

For records professionals, this connects directly to the properties that distinguish a record from mere data: authenticity, reliability, integrity, and usability. Preservation metadata of the kind PREMIS describes can help document the history of actions taken on a digital object, supporting the ability to demonstrate over time that an object is what it purports to be and has not been altered in undocumented ways. This becomes increasingly important as retention obligations extend across years or decades and as the systems that originally created records are decommissioned.

PREMIS is also significant for interoperability. Because one of its stated primary uses is the exchange of archived information packages between systems, it helps organizations avoid locking preservation information into a single repository or vendor environment. This supports scenarios such as transfer to another custodian, migration to a new platform, or eventual transfer to a permanent archive, all of which fall within the broader notion of disposition rather than simply retention or destruction. Its value depends, however, on how it is implemented and on the surrounding metadata and packaging standards an organization chooses to use alongside it.

Who it's relevant to

Digital preservation specialists and repository managers

Those responsible for designing, evaluating, or operating digital repositories are the most direct audience, given that repository design, repository evaluation, and package exchange are among PREMIS's stated primary uses. They typically use the data dictionary to determine what preservation metadata to capture and how to structure it within their chosen systems.

Archivists managing long-term custody

Archivists concerned with retaining and eventually transferring or permanently preserving digital objects may find PREMIS relevant to documenting the history and integrity of those objects over time. It supports the exchange of archived information packages between systems, which is pertinent when custody changes or when material moves to a permanent archive.

Records managers dealing with long-term digital records

Records managers whose retention requirements extend over long periods, or who anticipate transfer as part of disposition, may need to understand how preservation metadata supports the continued usability and trustworthiness of digital records. PREMIS addresses preservation metadata specifically and is generally used in conjunction with the classification, retention, and descriptive tools that records management otherwise relies on.

Information governance leads coordinating standards

Those setting policy across preservation, access, privacy, and value considerations may need to position PREMIS within a wider set of standards. Because PREMIS is scoped to preservation metadata rather than descriptive cataloguing, rights, or records classification, governance leads typically consider how it fits alongside complementary standards according to organizational and repository context.

Inside PREMIS

Preservation metadata

PREMIS is fundamentally a specification for the metadata needed to support the long-term preservation of digital objects, focusing on information that helps ensure objects remain viable, renderable, understandable, and authentic over time rather than on descriptive cataloguing metadata.

Data model of core entities

PREMIS is typically organized around a small set of interrelated entities, commonly described as Objects, Events, Agents, and Rights. This structure separates the things being preserved from the actions taken upon them, the actors involved, and the permissions or restrictions that apply.

Object entity

Represents the digital material being preserved and its technical characteristics. Objects are often distinguished at different levels of granularity, such as the intellectual entity, the representation, the file, and the bitstream, allowing preservation information to be recorded at the appropriate level.

Event entity

Documents actions taken on or by objects and agents over time, such as ingest, fixity checks, format migration, or validation. This supports an audit trail that contributes to demonstrating the integrity and authenticity of preserved material.

Agent entity

Represents the people, organizations, or software involved in preservation events or associated with rights statements, providing accountability for the actions recorded against objects.

Rights entity

Captures permissions, restrictions, and the legal or statutory basis for actions relevant to preservation, such as the authority to migrate or copy an object. The specifics of applicable rights depend on jurisdiction, sector, and organizational policy.

Data dictionary and semantic units

PREMIS is often expressed through a data dictionary that defines semantic units and their meanings, which implementers can map to concrete encodings such as XML schemas. It defines what information is needed rather than mandating a single storage format.

Common questions

Answers to the questions practitioners most commonly ask about PREMIS.

Is PREMIS a file format or a piece of preservation software?

No. PREMIS is a data model and metadata dictionary for the information needed to support digital preservation, not a file format or an application. It defines what preservation metadata to record rather than prescribing a single storage format or tool. Implementations typically express PREMIS in a serialization such as XML, and many preservation systems incorporate PREMIS concepts, but PREMIS itself is a specification for preservation metadata rather than executable software or a container format.

Does adopting PREMIS mean I no longer need descriptive or records management metadata?

Not typically. PREMIS focuses on preservation metadata, the information supporting the long-term viability, renderability, and understandability of digital objects, rather than on descriptive metadata for discovery or on the recordkeeping metadata that documents records as evidence of activity. In practice it is often used alongside other metadata schemes, with each addressing a different purpose. Relying on PREMIS alone would generally leave descriptive, contextual, and recordkeeping needs unmet, depending on organizational requirements.

How does PREMIS relate to the entities we already track in a preservation repository?

PREMIS is generally organized around core entities that commonly include objects, events, agents, and rights. Objects represent the digital material being preserved, events record actions taken on those objects, agents identify the people, organizations, or software involved, and rights capture permissions and restrictions bearing on preservation actions. Mapping your repository's existing concepts to these entities is often an early implementation step, though the exact alignment depends on your systems and workflows.

Where in a preservation workflow should PREMIS metadata be captured?

Preservation metadata is often captured at multiple points across the lifecycle rather than at a single moment. Information about objects and their technical characteristics is frequently recorded at ingest, while event metadata typically accumulates as actions such as fixity checks, format migrations, or replications occur over time. Because PREMIS is designed to document preservation activity, capture is generally treated as ongoing, with the specific triggers depending on your workflow and system capabilities.

How can PREMIS be implemented alongside other metadata standards?

PREMIS is commonly implemented in combination with complementary standards, and it is often embedded or referenced within broader packaging or wrapper structures used in preservation contexts. Organizations typically decide how PREMIS elements coexist with descriptive and structural metadata, how identifiers are shared across schemes, and where each type of metadata is authoritatively maintained. The appropriate arrangement depends on the tools in use and on institutional policy.

What should we consider when deciding how much PREMIS detail to record?

The level of detail is generally a policy decision balancing preservation needs against the cost of capturing and maintaining metadata. Considerations often include which preservation events are significant enough to document, how much technical characterization to record for objects, and how rights information will be sourced and kept current. Because requirements vary by collection, risk profile, and jurisdiction, many organizations define their own local implementation profile rather than adopting every element uniformly.

Common misconceptions

PREMIS is a descriptive metadata standard comparable to cataloguing schemes.

PREMIS is concerned primarily with preservation metadata that supports the ongoing viability, integrity, and authenticity of digital objects. Descriptive metadata that supports discovery and cataloguing is generally handled by other schemes, and PREMIS is often used alongside, rather than in place of, such standards.

Implementing PREMIS by itself preserves digital records.

PREMIS provides a structured way to record the metadata that supports preservation, but it is not a preservation system or process on its own. Actual preservation depends on the surrounding repository infrastructure, policies, storage, and preservation actions; PREMIS documents and supports those activities rather than performing them.

PREMIS mandates a specific file format or encoding for its metadata.

PREMIS is typically framed as a data model and data dictionary defining what preservation information is needed. It can be expressed in different encodings, and implementation choices such as serialization format depend on the repository environment and organizational decisions.

Best practices

Treat PREMIS as complementary to descriptive and structural metadata standards, mapping it deliberately to the other schemes in use rather than expecting it to serve discovery and cataloguing needs.

Decide and document the level of granularity at which you record Object information, distinguishing intellectual entities, representations, files, and bitstreams to match your repository's needs.

Use the Event entity to maintain a consistent audit trail of preservation actions such as ingest, fixity checking, and migration, so that integrity and authenticity can be demonstrated over time.

Record Agents responsibly so that people, organizations, and software associated with events and rights are identifiable, supporting accountability for preservation actions.

Capture Rights information with attention to the jurisdictional, sectoral, and policy basis for preservation actions, since the authority to copy, migrate, or retain material varies by context.

Position PREMIS within a broader preservation environment, recognizing that the surrounding repository, policies, and processes carry out preservation while PREMIS documents and supports it.