When a record recognizes a person's former identity

A record can find the right history and still fail to recognize the person standing in front of it. The difficulty lies in what the institution treats as authoritative when a retained identifier and a current identity no longer agree.

Lars Z. Mackenzie’s 2017 study of trans credit reporting makes that problem concrete. Drawing on online discussions, Mackenzie examines how legally changed names encountered credit files organized around continuing identification. The study concerns historical United States credit reporting, rather than the current procedure at every bureau or advice about an individual’s credit.

For librarians, the work raises a question inside the profession’s own commitment to continuity. What must a system retain to connect a person with the relevant record, and which retained information needs to remain visible or operative once that connection has been established?

Continuity can become an obstacle to recognition

Mackenzie’s cases describe people encountering a conflict between current names and credit histories connected to former names. The difficulty could affect authentication beyond a lending decision, including housing and employment. The research shows the range of reported experiences; it does not provide a population estimate of every trans person’s encounter with a credit bureau.

The study’s account of a data afterlife concerns continued use. An old value matters because another institution can treat it as evidence about the present person, making the retained history consequential at the moment someone seeks recognition under their current identity.

The Atlas interprets this relation as a failure of a promised passage. Legal change and documented continuity do not necessarily produce usable recognition. A system organized to preserve a historical connection can make that very connection difficult to revise without disclosing information the person did not choose to make relevant to the encounter.

I find the relation between retention and authority more precise than saying that the database simply contains an error. A historical name may have been recorded accurately. The question concerns the later decision to use or display it, particularly when the institution makes an old value more decisive than the person’s current account.

That distinction prevents a false choice between retaining everything in every interface and destroying all continuity. A record may support several purposes whose information requirements differ, so a value needed for one controlled administrative task does not automatically need to appear in another person’s search results or routine conversation.

The case also complicates a simple correction story. If an institution recognizes a new name while continuing to expose the former one, a technically successful update may leave the consequential disclosure unchanged. An evaluation needs to inspect the particular use and display through which the retained value still acts.

Mackenzie’s critical account remains specific to the financial and surveillance relations studied. The library comparison does not transfer those institutions’ entire history onto a patron database. It borrows an exact question about whose present identity a record can recognize and which evidence the institution allows to govern that recognition.

Separate the need to connect from the permission to display

A library has several kinds of identity work. Distinguishing authors, administering borrower accounts, and documenting archival provenance involve different purposes and different authority. A common field label does not settle which practice applies.

The PCC FAQs for authors and creators address correction requests and the role of information from the represented person. They also describe the complication of distributed bibliographic data. Those guidelines concern authority work; they should not be presented as the policy governing every patron account.

I would begin with one actual record system and identify the purpose of each retained identity field. Ask which operation requires the historical value, who can see it, and what happens if the value is removed from ordinary display while the institution preserves whatever justified connection the task requires.

A hypothetical creator record might need a relationship between works issued under different names. That does not by itself decide whether every historical name needs prominent display in every interface. A patron account presents another problem, where operational continuity should be assessed against the institution’s current account and privacy purposes.

The IFLA privacy statement provides professional grounds for attending to unnecessary exposure and user control. It supplies a normative responsibility, not a universal retention period or a legal answer for every jurisdiction.

The represented person’s request should help define the review. Ask what needs correction and where the current display causes a problem, rather than requiring a complete personal history before staff can identify the controlled field. Retain only the explanation the institution has a legitimate reason to hold.

Then inspect the result from the relevant reader’s position. The staff record, the public display, and a supplier’s copy may differ. An account of completion needs to name which of those changed and which remain beyond the library’s verified control.

A record review is ready to close when the institution can explain why each remaining identity value is needed, where it can appear, and how the person can contest that use. The history should serve the justified task without silently overruling the identity under which the person is now asking to participate.