Electronic Records Management Guidelines
Metadata
Summary
Data about data. Information (e.g., creator name, creation date) that is used to facilitate intellectual control of, and structured access to, other information. Metadata is usually defined as "data about data." Metadata allows users to locate and evaluate data without each person having to discover it anew with every use. Its basic elements are a structured format and a controlled vocabulary, which together allow for a precise and comprehensible description of content, location, and value.
While the term itself might sound new and trendy, the concept it describes is not. In some fashion, metadata has always been with us, apparent in everything from program listings in TV Guide to the nutritional information on the back of a cereal box. For government
According to the State of Minnesota, an item that documents an official government transaction or action.
"All cards, correspondence, disks, maps, memoranda, microfilm, papers, photographs, recordings, reports, tapes, writings and other data, information or documentary material, regardless of physical form or characteristics, storage media or condition of use, made or received by an officer or agency of the state and an officer or agency of a county, city, town, school, district, municipal, subdivision or corporation or other public authority or political entity within the state pursuant to state law or in connection with the translation of public business by an officer or agency…. The term 'records' excludes data and information that does not become part of an official translation, library and museum material made or acquired and kept solely for reference or exhibit purpose, extra copies of documents kept only for convenience of reference and stock of publications and process documents, and bond, coupons, or other obligations or evidence of indebtedness, the destruction or other disposition of which is governed by other laws" (Minnesota Statutes, section 138.17, subd.1).
"Information that is inscribed on a tangible medium or that is stored in an electronic or other medium and is retrievable in perceivable form" (Minnesota Statutes, section 325L.02).
records,
the familiar forms of metadata are the recordkeeping metadata standard and the records retention schedule.
Anyone who has suffered the exercise in irrelevance offered by an The vast network of computer systems that enables worldwide connectivity among users and computers. Internet search engine will appreciate the value of precise metadata. Because "Data, text, images, sounds, codes, computer programs, software, databases, or the like" (Minnesota Statutes, section 325L.02). information in a digital format is only legible through the use of intermediary hardware and software, the role of metadata in information technology is fundamentally important. In any system, given the volume of information it contains, the uses to which it can be put, and the costs involved, metadata is the basic tool for efficiency and effectiveness.
Whatever you want to do with the information (e.g., protect its confidentiality, present it as evidence, provide citizens access to it, broadcast it, share it, preserve it, destroy it) will be feasible only if you and your partners can understand and rely upon the metadata describing it. Using metadata effectively means understanding and applying the standards appropriate to your needs.
Key Concepts
To understand, create, and use metadata effectively, you will need to know more about:
Metadata Functions
Government agencies routinely use metadata to fulfill a variety of functions, but the primary uses are for:
- Legal and statutory reasons (e.g., to satisfy records management laws and the rules of evidence)
- Technological reasons (e.g., to design and document systems)
- Operational or administrative reasons (e.g., to document decisions and establish accountability)
- Service to citizens, agency staff, and others (e.g., to locate and share information)
In all of these cases, metadata standards will be effective only if they rely on a structured format and controlled vocabulary. "Structured format" means the metadata is defined in terms of specific, standardized elements or fields. For example, a library catalog entry for a book will identify its author, title, subject(s), and location, among other things. Unless all the elements are there, users will not be able to evaluate the metadata; they won't be able to answer the question "Is this the book I want?"
"Controlled vocabulary" means that there is a standard as well for the content of the elements. For example, the nutritional information on the back of a box of cereal is often defined in terms of weight per serving. We know what “sugar: three grams” means. It refers to a standard unit of measurement that allows us to compare the sugar content of one cereal to that of another. But if the box read "just the way you like it" or "pretty sweet," that would mean different things to different people. We couldn't compare a subjective review like that to what's on the back of another box of cereal.
To work effectively, the elements and components of metadata should have an accepted, precise meaning that reflects a common understanding among its creators and its users. That allows for evaluation and comparison, for selecting the information you want from all the information available.
Legal Needs and Statutory Mandates
Because you are part of a government entity, you need to pay particular attention to metadata's value to help you achieve basic legal needs and meet statutory mandates.
For example, Minnesota's Records Management Act mandates that government agencies cannot dispose of records without the approval of the state's Records Disposition Panel. The only way to get that approval is to describe the records: what they are, where they are, what their significance is, and how they should be disposed. All that information is metadata. In the The planning, controlling, directing, organizing, training, promoting, and other managerial activities related to the creation, maintenance, use, and disposition of records. See also Recordkeeping. records management process, metadata usually takes two forms, either a A plan for the management of records listing types of records and how long they should be kept; the purpose is to provide continuing authority to dispose of or transfer records to the Minnesota State Archives. records retention schedule or an Application for Authority to Dispose of Records form (PR–1).
Similarly, the Minnesota Government Data Practices Act classifies data under nine different categories which specify how, when, or if the public may gain access to government data. You cannot guess what level of access or security to provide just by looking at the data itself. You need some additional information—some metadata—in order to follow the letter of the law.
These are some of the laws most pertinent to the use of metadata:
- Official Records Act (Minnesota Statutes, Chapter 15.17) (available at: http://www.revisor.leg.state.mn.us/stats/15/17.html), which mandates that government agencies must keep records in order to be accountable for their actions and decisions.
- Records Management Act (Minnesota Statutes, Chapter 138.17) (available at: http://www.revisor.leg.state.mn.us/stats/138/17.html), which creates the Records Disposition Panel and establishes the records management process for government records.
- Minnesota Government Data Practices Act (MGDPA) (Minnesota Statutes, Chapter 13) (available at: http://www.revisor.leg.state.mn.us/stats/13/), which mandates that your records should be accessible to the public, unless categorized as not-public by the state legislature.
The metadata requirements of all of these statutes are encompassed in the state's Recordkeeping Metadata Standard. For more information on the legal framework you must consider when dealing with government records, refer to the Introduction and Appendix D of the Trustworthy Information Systems Handbook.
Metadata and Information Technology
Metadata is useful for the management of information in any storage format, paper or digital. But it is critically important for information in a digital format because that is only legible through the use of intermediary hardware and software. We can open up a book or even hold microfilm up to a light to determine what it says. But we can't just look at a CD and say what's on it. We cannot possibly hope to locate, evaluate, or use all the files on a single PC, let alone the Internet, without metadata.
If information technology makes metadata necessary, it's information technology that makes metadata useful. Special software applications, such as TagGen, make the creation of standardized metadata simpler. Databases store and provide access to metadata. Most software applications automatically create metadata and associate it with files. One example is the header and routing information that accompany an e-mail message. Another is the set of properties created with every Microsoft Word document; certain elements such as the title, author, file size, etc., are automatically created, but other elements can be customized and created manually. Normally, some combination of automatically and manually created information is best for precise and practical metadata.
Most important, metadata can inform business rules and software code that transforms it into "executable knowledge." For example, metadata can be used for batch processing of files. A date element is critical to records management, as most record retention schedules are keyed to a record's date of creation. Metadata in more sophisticated data formats, such as eXtensible Markup Language (XML), allow for extraction, use, and calculation based on specific components of a metadata record.
Metadata Standards
To work effectively, metadata has to be precise and comprehensible. The entire community of creators and users has to understand what it means. There is a variety of metadata standards in use across the world, but there are three principal standards in general use in Minnesota government today. Minnesota's Office of Enterprise Technology (http://www.oet.state.mn.us/) recommends the following standards in its
enterprise architecture:
- Minnesota Metadata Guidelines – Dublin Core
- Minnesota Geographic Metadata Guidelines
- Minnesota Recordkeeping Metadata Standard
Minnesota Metadata Guidelines – Dublin Core (MMG-DC)
The
A widely used set of metadata elements that is easily embedded in a web page.
Dublin Core
is a metadata standard with fifteen elements that is an official international standard (NISO Standard Z39.85; ISO Standard 15836). It was designed principally by the library and archives community, and its primary application is to describe information resources, particularly web content. When you use the search engine on the state's North Star site, Dublin Core metadata helps you find exactly what you're looking for.
The MMG-DC set includes these elements:
- Title. The name of the resource given by the creator or publisher.
- Subject. The topic of the resource.
- Description. A short, text description of the resource's contents.
- Creator. The name of the person who created the resource.
- Publisher. The name of the entity that published the resource. Note that the publisher is not the person who posted the resource to the web site, but the entity responsible for the publication of the resource, such as your agency.
- Contributor. Someone aside from the creator who made a significant contribution to the resource.
- Date.Either the creation date or the publication date. Your agency will need to determine which date to use.
- Resource Type. The category the resource belongs to, such as committee minutes, press release, or report.
- Format.The file format of the resource. For more information on file formats refer to the File Formats guidelines
- Identifier. A text string or number unique to the resource, such as a URL or other formal name. See the File Naming guidelines for more information on naming web site files for longevity and ease of use.
- Relation. An element that refers to related resources.
- Source.Information about the source from which the current resource is derived (e.g., an abstract of a report).
- Rights Management.A text statement regarding copyright and use permission.
- Language.The language used in the resource (e.g., English, Spanish).
- Coverage.Either geographic (e.g., Minnesota) or temporal (e.g., the years 2000–2001).
To populate these elements and to describe web content, the State of Minnesota uses an established and maintained set of terms along with the MMG-DC. Information on the Legislative Indexing Vocabulary is available online, at http://www.bridges.state.mn.us. The State also has a license to use a specific software application, TagGen, as a tool for the creation or capture of metadata. It is available free to Minnesota government agencies. Information on using and acquiring TagGen is also online, at http://www.bridges.state.mn.us, along with an instructional manual, the Best Practices Guidelines for Web Metadata.
Minnesota Geographic Metadata Guidelines
The Minnesota Geographic Metadata Guidelines provide a common approach for documenting all types of geographic data. They have been designed to be straightforward, intuitive, and complete. The guidelines are based on a standard developed by the Federal Geographic Data Committee in 1993: The Content Standards for Digital Geospatial Metadata. In developing the Minnesota Geographic Metadata Guidelines, the Standards Committee of the Minnesota Governor's Council on Geographic Information created a streamlined implementation of the federal standard, while retaining the essence of its original content. Information about the guidelines is available at http://www.gis.state.mn.us/stds/metadata.htm.
The Minnesota Geographic Metadata Guidelines includes a number of metadata elements, arranged in seven sections:
- Identification Information
- Data Quality Information
- Spatial Data Organization Information
- Spatial Reference Information
- Entity and Attribute Information
- Distribution Information
- Metadata Reference Information
Minnesota Recordkeeping Metadata Standard
The Minnesota Recordkeeping Metadata Standard is designed to support the accountability of government and the proper use of government records as mandated by law. It is based on the Dublin Core, and its fields can be easily mapped to the Minnesota Geographic Metadata Guidelines.
The standard consists of twenty elements, ten of which are mandatory and ten optional. In addition, many of these elements contain a number of sub-elements, some mandatory and some optional. To ensure compatibility across metadata sets, six of the ten mandatory elements have direct counterparts both in the Dublin Core and the geographic metadata standards. Overall, the recordkeeping metadata elements are:
- Agent. An agency or organizational unit that is responsible for some action on or usage of a record, or an individual who performs some action on a record, or who uses a record in some way.
- Rights Management.Legislation, policies, and caveats that govern or restrict access to or use of records.
- Title.The names given to the record.
- Subject.The subject matter or topic of a record.
- Description.An account, in free text prose, of the content and/or purpose of the record.
- Language.The language of the content of the record.
- Relation.A link between one record item and another, between various aggregations of records, or a link between a record and another information resource.
- Coverage. The jurisdictional, spatial, and/or temporal characteristics of the content of the record.
- Function.The general or agency-specific business function(s) and activities that are documented by the record.
- Date. The dates and times at which such fundamental recordkeeping actions as of the record's or records series' creation and transaction occur.
- Type.The recognized form or genre a record takes, which governs its internal structure.
- Aggregation Level.The level at which the record(s) is/are being described and controlled or the level of aggregation of the unit of description.
- Format.The logical form (content medium and data format) and physical form (storage medium and extent) of the record.
- Record Identifier. A unique code for the record.
- Management History. The dates and descriptions of all records management actions performed on a record from its registration into a recordkeeping system until its disposal.
- Use History. The dates and descriptions of both legal and illegal attempts to access and use a record, from the time of its registration into a recordkeeping system until its disposal.
- Preservation History. The dates and descriptions of all actions performed on a record after its registration into a recordkeeping system which ensure that the record remains readable and accessible for as long as it has value to the agency and to the community at large.
- Location. The current (physical or system) location of the record or details about where the record usually resides.
- Disposal. Information about policies and conditions that pertain to or control the authorized disposal of records or information about the current retention schedule and disposal actions to which the record is subject.
- Mandate. A source of recordkeeping requirements. For example, a piece of legislation, formal directive, policy, standard, guideline, set of procedures, or community expectation which (explicitly or implicitly) imposes a requirement to create, keep, dispose of, or control access to and use of a record.
Key Issues to Consider
Now that you are familiar with some of the basic concepts and types of metadata, you can consider some of the issues that have to be addressed in order to use metadata effectively. The most important are:
- Audiences: Most people who rely on metadata are unaware they're using it or even that it exists. Nevertheless, when you create metadata, you have to be aware of the audiences for your information in order to determine the appropriate standards and approaches. To make your decisions, you should know which information resources your audiences use, which questions they ask, and what their level of expertise is.
- Partnerships: To increase the value of both metadata and the information it describes, you need to work with other creators, custodians, and users of information. If you agree on metadata standards, tools, and practices in collaboration with others, you will create a much more beneficial information management program for your whole organization.
- Implementation: Selecting a standard is a good first step. Putting it into practice is a more useful and difficult one. Creating and maintaining metadata over time will demand attention, resources, and staff. You will get a good return on that investment if you keep in mind your legal mandates, your business processes, and your customers as you choose what standards and practices are most appropriate for you.
- Education: One critical element of a practical metadata program to keep in mind is education. You will need to know about what others are doing with the standards, the tools, and the uses of metadata. As these change, you will need to keep up with those developments.
- Promotion: To promote the understanding, use, and creation of metadata, as well as to ensure that there are enough resources to support a metadata program, it is important to draw people's attention to metadata and its importance. The State of Minnesota's Information Policy Council supports a metadata awareness program designed by the Land Management Information Center and the State Archives Department of the Minnesota Historical Society. The program promotes reliable and standardized metadata with an educational resource online and a symbol: When you see this symbol, you are looking at information that is described by metadata created according to a recognized standard. On a web page, the symbol will act as a hot link to a page describing the value and uses of metadata and offering information about specific metadata standards used in Minnesota.
Discussion Questions
- What are the business functions your metadata is supposed to fulfill?
- Who is the audience for your metadata? What are their needs?
- Does your agency have an information and/or technical architecture? What metadata standards does it recommend?
- Are your software applications creating metadata?
- What are your legal needs? Does your agency have a records management or data practices office?
- Do the managers and resource allocators in your agency support a metadata program? Have you made a business case to them?
- Are the offices or departments of your agency already creating metadata? Are they using different standards?
- What are the metadata standards pertinent to your profession or business functions?
Download a copy of the Metadata Key Issues to Consider and Discussion Questions. ![]()
Metadata, Annotated List of Resources
Electronic Records Management Guidelines, March 2004, Version 4.





