What to Recheck After a Digital Memorial Account, Domain, or File Change

Direct answer and scope

Start by identifying the claimed change category: account, destination, domain, redirect, portrait version, export, or file. Then identify the evidence layer connected to that change. A domain change calls for a domain and redirect review; a changed portrait file calls for version, export, copy, and readability questions; an account change calls for a review of the account-related evidence and any dependent destination or handoff records. The change category itself is not a conclusion about any layer.

Keep the prior evidence state and current evidence state in separate records. The prior record can show what had been documented before the change, while the current record can show what has been supplied or observed afterward. Do not fill an unanswered field merely because another field changed.

A QR image is only one layer in the continuity review. The underlying destination, account or domain control, redirect control, human-readable fallback, export, independent copies, periodic tests, and continuity handoff require their own questions. The review therefore remains unresolved wherever the relevant evidence has not been supplied.

How to use the official evidence

For each affected layer, preserve the earlier evidence and request the corresponding current evidence rather than treating a replacement record as a complete history. Useful questions include what changed, which document or record reflects the change, whether the supplied record corresponds to the affected evidence layer, and whether an independent copy or test addresses the same layer.

For hosted web content, ask whether an independently readable export exists, what it contains, and which metadata accompanies it. The Library of Congress guidance identifies selected information, metadata such as a site name or creation date, and organized exported files as subjects to document. It does not establish that a particular service supplies an export or that an export preserves every function.

For digital records and portrait files, distinguish master, approved, display, export, and documentation version-status questions without assuming that every project has each version. Use descriptive records and document how files are organized. Keep the vendor copy, commissioner copy, and independent backup evidence states separate, and do not treat an unverified copy as evidence that the file can be recovered.

Readability is a separate question from possession. The Library of Congress guidance advises checking photo files at least annually, making new media copies periodically or when needed, and checking saved files periodically for readability. These are review actions, not a universal replacement schedule or a conclusion about any particular file.

Decision framework

First, classify the change without expanding it. A destination change concerns the destination record and any related route question. A domain or redirect change concerns those corresponding records. An account change concerns the account-related evidence and any documented handoff question. A portrait or file change concerns version status, copies, export questions, and readability testing. If the change category is not documented, leave that classification open.

Second, map the change to affected layers. Ask whether the prior and current records refer to the same memorial destination and whether a human-readable fallback is documented. Separately ask about independent copies, periodic tests, and continuity handoff. Keep the answers as individual states; do not substitute one answer for another.

Third, compare the evidence dates and descriptions. Record what the earlier evidence said, what the current evidence says, and which source or record supports each statement. If a current export is supplied, document its stated contents and accompanying metadata questions separately from the questions about readability, copies, or restoration. If a changed file is supplied, document its version status separately from any question about the other memorial layers.

Finally, mark each unanswered question for follow-up. The method is designed to keep selected evidence states and unresolved questions separate, so a changed record can trigger a focused recheck without producing an overall positive conclusion.

Limits and what to verify next

A current URL, redirect record, account record, or domain record does not answer every continuity question. Keep separate questions about the destination, control, fallback, export, copies, readability testing, and handoff. The evidence review should show which layer was rechecked and which layers were not addressed by the reported change.

A new export does not replace a readability check or evidence about independent copies. Possessing a copy does not by itself document that the copy has been tested, and a test of one copy does not answer the status of another copy. Preserve those distinctions in the record.

For a changed portrait file, ask which version is being discussed and whether the current file is identified as a master, approved, display, export, or documentation version. Do not invent a required file set, file format, resolution, color profile, layer structure, or naming convention. The next verification should address the specific missing record rather than assume a standard package.

No vendor-specific capability, account-control arrangement, export behavior, file format, backup practice, restore path, privacy practice, succession path, price, availability, or service term is established in the supplied launch pack. Such values remain unknown until a separate primary-evidence manifest passes review.

Questions people ask

Use the questions below to identify the evidence layer that needs attention. Each answer preserves the difference between a documented state and an unanswered question.

Evidence behind this page

Each point below is restricted to what the cited primary source supports. Administrative listing status is not a quality endorsement.