If a North Carolina state agency keeps adding new records to an old database, does that trigger the public-records index requirement under § 132-6.1(b)?
Plain-English summary
In 1995, the General Assembly added § 132-6.1(b) to the Public Records Act. The new law required every state agency, and eventually every covered local government, to create an index of its computer databases. The index had to list the data fields, the format, the update frequency, fields restricted from public access, available export formats, and the agency's fee schedule for copies. State agencies had to have the index built by July 1, 1996; large local governments by 1997; smaller ones by 1998.
The statute carried one important escape hatch. Databases "compiled or created" before each agency's deadline could be indexed at the agency's option. The Department of Cultural Resources asked the AG whether that option survived in practice. State databases often outlive a generation of programmers. The format is set, the layout is arcane, and new records flow in every day. Did the daily addition of new records mean the database was being "compiled" continuously, restarting the clock and dragging it back under the indexing requirement?
The AG said no. The question turned on the word "compile." Senior Deputy Attorney General Ann Reed and Special Deputy Charles J. Murray went to three standard dictionaries (Webster, Oxford American, American Heritage) and read the term in context. To "compile" meant to gather information from several sources into a new work, or to restructure an existing collection, or to assemble a new database by combining several. Loading a fresh row into a database table that already had a defined structure was not compiling. It was updating.
The AG's interpretation also fit the statute's evident purpose. The General Assembly clearly knew how to talk about ongoing data flow if it wanted to. Just one sentence earlier in the same subsection, the statute required the index to include "information as to the frequency with which the database is updated." If the legislature had wanted the grandfather exemption to disappear the moment an agency added new data, it would have written the option to apply only to databases that were no longer being updated. It did not. Limiting the option that way would also gut its purpose. The whole point of the option was to let agencies skip indexing of old, arcane systems where the effort would exceed the public benefit. Old systems that nobody touches are rare; old systems that keep receiving data are the common case. Reading "compile" to include routine updating would shrink the option to almost nothing.
The opinion closed with a practical note: just because an index was optional did not mean it was unwise. All information in any state or local government electronic database is a public record under § 132-1. Indexes help the public exercise that right, and an agency might choose to build one for an old database whenever practicable.
Currency note
This opinion was issued in 1996. Subsequent statutory amendments, court decisions, or later AG opinions may have changed the analysis. Treat this page as historical context, not current legal advice. Verify current law before relying on any specific rule, deadline, or remedy mentioned here. § 132-6.1 has been amended several times since 1996, including amendments addressing electronic data more broadly, geographic information systems, and fee structures. The basic principle of statutory construction, that routine data updates do not equate to compiling, is the kind of textual reasoning courts continue to apply, but a present-day records request should be evaluated against the current statute and current Public Records Office guidance.
Background and statutory framework
The 1995 Public Records Act amendments responded to the rapid growth of state electronic record-keeping in the early 1990s. Before then, public records requests typically pulled paper files; agencies often did not know what was in their own databases at a field-level granularity, and requesters had no way to ask intelligently. The new index requirement was an effort to make the record-keeping itself transparent.
The phased deadline structure (state by 1996, large local by 1997, small local by 1998) reflected the practical reality that small counties and small municipalities had fewer resources and less developed IT operations than state agencies. The grandfather clause for pre-deadline databases was the second adaptation. Lawmakers recognized that retro-indexing a thirty-year-old mainframe system with no surviving documentation could be wildly expensive, and that the public benefit of an index for a database that was already being phased out might be marginal.
The Department of Cultural Resources, which housed the Division of Archives and History, was the agency responsible for developing the statewide index format. It also operated some of the oldest electronic record systems in state government, including registration and finding-aid databases for archival materials. The question was practical: the Division kept loading new records, and it wanted to know whether continuing routine data entry would extinguish the agency's option not to index legacy systems.
The AG's reading kept the option alive in its intended form. "Compile" meant the structural creation of a database, not the routine flow of records through one whose structure was fixed.
Common questions
Does this opinion mean an agency can never be required to index an old database?
The AG opinion only addresses whether ongoing updates trigger the indexing requirement. If an agency restructures a legacy database (changes the record layout, merges it with another database, or builds a new analytical view from several sources), that activity could constitute compiling under the AG's reading and the index option would be lost for the restructured product.
Does the public still have the right to request records from an unindexed database?
Yes. § 132-1 made every record in a public agency's electronic database a public record unless specifically made confidential elsewhere by law. The index requirement under § 132-6.1(b) governs the agency's metadata duty, not the public's access right.
What is the difference between an indexed and an unindexed database, in practice?
For an indexed database, the public can see, in a single document, what fields exist, how they're formatted, how often they're updated, which fields are restricted, what export formats are available, and what copies cost. For an unindexed database, that information has to be developed through correspondence with the agency, often as part of a request.
Does this principle apply to local-government databases too?
The opinion was framed around state agencies, but the same statutory phrase ("compiled or created prior to the date by which the index must be created") applied to local governments under the same statute, just with later deadlines. The AG's reasoning would presumably extend to a local government dealing with the same kind of legacy system, though the local deadlines were 1997 and 1998.
Source
Citations
- N.C.G.S. § 132-1 (public records definition)
- N.C.G.S. § 132-6.1(b) (index requirement; grandfather option)
- Parrish Funeral Home v. Pittman, 104 N.C. App. 268 (1991) (ordinary-meaning canon for undefined statutory terms)
Original opinion text
February 26, 1996
Ms. Elizabeth F. Buford Deputy Secretary Department of Cultural Resources 109 E. Jones Street Raleigh, NC 27601-2807
Re: Advisory opinion; N.C.G.S. § 132-6.1; Public Records; Computer Database Index
Dear Ms. Buford:
The following is submitted in response to your request for an opinion on the following question:
Does the addition of data after July 1, 1996 to a state agency's electronic database which was compiled or created prior to that date have the effect of eliminating the option not to create an index for the database under the provisions of N.C.G.S. § 132-6.1(b)?
It is our opinion that the answer to the question is no based upon the following analysis. Your request involves an interpretation of N.C.G.S. § 132-6.1(b) enacted in 1995 and which reads as follows:
(b) Every public agency shall create an index of computer databases compiled or created by a public agency on the following schedule: State agencies by July 1, 1996; Municipalities with populations of 10,000 or more, counties with populations of 25,000 or more, as determined by the 1990 U.S. Census, and public hospitals in those counties, by July 1, 1997; Municipalities with populations of less than 10,000, counties with populations of less than 25,000, as determined by the 1990 U.S. Census, and public hospitals in those counties, by July 1, 1998; Political subdivisions and their agencies that are not otherwise covered by this schedule, after June 30, 1998.
The index shall be a public record and shall include, at a minimum, the following information, with respect to each database listed therein: a list of the data fields; a description of the format or record layout; information as to the frequency with which the database is updated; a list of any data fields to which public access is restricted; a description of each form in which the database can be copied or reproduced using the agency's computer facilities; and a schedule of fees for the production of copies in each available form. Electronic databases compiled or created prior to the date by which the index must be created in accordance with this subsection may be indexed at the public agency's option. The form, content, language, and guidelines for the index and the databases to be indexed shall be developed by the Division of Archives and History in consultation with officials at other public agencies.
Your request deals specifically with the sentence in the legislation which reads as follows:
Electronic databases compiled or created prior to the date by which the index must be created in accordance with this subsection may be indexed at the public agency's option.
The index for electronic databases is a new requirement which is imposed on various levels of government for databases "compiled or created" after dates set out in the statute. The sentence setting out the option not to index provides that the requirement need not be applied retroactively to existing electronic databases created or compiled prior to the relevant date. Whether an electronic database is created prior to a specified date is easily determined and presents no need for interpretation. The above quoted sentence raises the question with regard to databases created prior to July 1, 1996, as to what activity after that date constitutes "compiling" of a database so as to take the database out from under the exemption from the indexing requirement.
With regard to your question, the issue can be stated as follows. Does the addition of information to an existing database by itself constitute "compilation" of the database? Quite obviously that issue will be determined by the definition of the word "compile". When construing statutes the general rule is that words appearing therein are to be given their natural or ordinary meaning, Parrish Funeral Home v. Pittman, 104 N.C. App. 268 (1991). The word "compile" is defined as follows.
compile 1 To compose (a literary work, etc.) from other works or sources. 2 To gather (facts, data, etc.) into a volume or into orderly form. (Webster Illustrated Contemporary Dictionary, 1988)
compile 1. to collect and arrange (information) into a list or book. 2. to make up (a book, etc.) in this way, compile a dictionary. (Oxford American Dictionary, 1980)
compile 1. To gather into a single book. 2. To put together or compose from materials gathered from several sources; compile an encyclopedia. 3. To convert to machine language. (American Heritage Dictionary, Second College Edition, 1982)
Those definitions establish that the term "compile" means more than merely updating or supplementing information which already is in a fixed form. The definitions lead to the conclusion that the term encompasses the amassing of information from several sources into a new work. In light of the above definitions and the context of the entire text of N.C.G.S. § 132-6.1, it appears that the word compile should be used to refer to the restructuring of an existing database or the gathering together of more than one existing electronic database, as opposed to the mere addition of new information within an existing electronic database whose structure or format does not change because of that addition.
Had the General Assembly intended to have the option only apply to electronic databases which are not being updated by new information, it could easily have so stated. For example, instead of using the wording it did, the General Assembly when enacting the statute could have used a variation of the phrase in the preceding sentence, viz. "information as to the frequency with which the database is updated." Finally, it is pointed out that to limit the option to only those databases that are not being updated with new information would severely limit the effect of the option. Specifically, the option would not be applicable to databases which have been in existence for years and which are built on arcane, unique processing programs and record layouts. Agencies often have valid reasons for using such a database rather than creating a new one and the effort necessary to index such a database may exceed any public benefit. Under those circumstances it appears logical and appropriate that the General Assembly exempted such a database from the requirement for an index.
In summary, it is our opinion that merely adding to, or updating information in an existing electronic database is not the equivalent of "compiling" a database, and therefore such additions do not have the effect of eliminating the agency's option of not creating an index for the database.
It is worthwhile to note that in North Carolina all information in any local or state government electronic database is a public record under N.C.G.S. § 132-1 and, unless otherwise made confidential by law, is subject to access by the public in accordance with Chapter 132. Therefore, a state agency may wish to create an index for an existing electronic database whenever it is practical even though an index is not required under the statute.
Ann Reed Senior Deputy Attorney General
Charles J. Murray Special Deputy Attorney General