Direct answer and scope
Request a file manifest rather than a format verdict. The manifest can list each requested asset and its role, such as a documented master, an approved display copy, an export, or a supporting description. It can also state whether a format description has been supplied, whether metadata has been designated private or displayable, whether a rights note has been written, and whether an independently readable copy has been identified. An unanswered item should remain unresolved rather than being marked complete.
The handoff may include a version map showing which file is intended to serve each stated role. The personal-digital-records guidance supports deciding which versions have long-term value, using descriptive names, organizing files, and documenting the folder structure. It does not establish how many versions a commission must contain or require a particular format, resolution, color space, layer structure, or naming convention.
The scope is documentation and questioning. It does not include requesting or examining a photograph, device, account, upload, filename, folder, or file path. It does not inspect readability, convert files, select a preferred version, determine image quality, or establish ownership, authorship, permission, or legal status.
How to use the official evidence
Use the Library of Congress personal-digital-archiving guidance as a method reference for inventory and documentation. For a photograph, ask whether the relevant source location has been identified and whether the source file and version to be used have been documented. For hosted memorial material, ask whether an independently readable export has been identified, what it contains, and which metadata accompanies it. The guidance does not establish that a hosted service provides an export, that a saved page is complete, or that an export preserves functionality.
Use the records and photograph guidance to separate a preservation copy from a display copy. Ask whether a copy outside the commissioned service exists and whether the parties have a process for checking copies for readability. The guidance recommends multiple copies in different locations and periodic readability checks, but it does not approve a particular medium, location, provider, recovery method, or replacement schedule for every file.
Use the National Archives material as an optional naming and backup reference, not as a commission standard. Consistent alphanumeric names with separators such as hyphens or underscores are described as one approach, and basic metadata may describe who, what, where, and when. The three-copy, two-media, one-off-site model can be recorded as a planning reference while each copy and location remains an evidence state to be confirmed.
Decision framework
Start with the asset inventory. Identify the categories of material that the handoff is intended to cover, such as a source image, commissioned portrait, approved display version, or export of hosted material. Record the role requested for each item without adding a file or feature that has not been supplied. The inventory should say where the important material is understood to exist, while leaving its completeness unresolved.
Next, create a version map. Ask which item is designated as the master, which is approved for display, which is an export, and which document explains the set. These labels describe different decisions; they do not prescribe a file format or prove that a file is the highest-quality, authentic, restorable, or suitable for a particular reproduction. Where multiple versions exist, the source guidance supports asking which version is intended for preservation without selecting or grading it.
Then document names, folders, and metadata at the level needed for the handoff. A private metadata decision can identify which descriptive information should accompany preservation copies and which information should not be displayed. The record should not require publishing a person's name, relationship, date, location, biography, or image description. A folder-manifest question can ask whether the structure has been described without collecting the underlying personal material.
Finally, separate readability from rights. A readability or copy status can state whether an independent copy has been identified and whether a check has been documented. A rights note can separately identify the source material, creator, deliverables, and intended reproduction or display permissions. Copyright guidance states that copyright protects original works once fixed and that owning a copy does not by itself establish copyright ownership; it does not decide the status of a particular portrait or source photograph.
Limits and what to verify next
The supplied evidence does not validate a portrait artist, digital-memorial vendor, hosting platform, QR provider, domain operator, processor, product, account-control arrangement, export, file format, backup, restore process, privacy practice, succession path, price, availability, review, or turnaround. Those values should remain unknown until a separate primary-evidence manifest is available. Nothing in the preservation guidance endorses a vendor, platform, format, cloud host, QR system, portrait workflow, or memorial service.
Before accepting a handoff, request the unresolved documents or statements relevant to the intended use: the asset and version list, the format manifest if one is available, the metadata privacy decision, the folder or export description, the readability or copy status, and the rights note. Verify each item with the responsible party rather than treating possession of a file, a live memorial, or a copy as proof of permission, ownership, completeness, continuity, or preservation.
Preservation is an active review process. Official guidance recommends periodic checks that selected files remain readable and recommends maintaining copies in different locations. Those recommendations do not guarantee that a file will remain readable, that a service will remain available, that a copy can be restored, or that any particular storage arrangement is independent. Contract, copyright, privacy, export, backup, and continuity questions therefore remain separate evidence states.
Questions people ask
Use these questions to request a documented handoff without asking for a photograph, account, upload, filename, or other personal material. Each answer should identify what has been documented and leave unsupported items unresolved.
Document format and metadata questions without a filename
Separate file-format, readability, metadata and private handoff questions. The page accepts no file and does not certify compatibility, preservation quality or ownership.
Evidence behind this page
Each point below is restricted to what the cited primary source supports. Administrative listing status is not a quality endorsement.
| Evidence | Supported point | Scope and limitation |
|---|---|---|
| Evidence 1 | Use a controlled source-location inventory status without asking for a photograph, device, service, account, or file path. | Do not scan devices, discover files, connect to accounts, upload photos, or claim that the inventory is complete. |
| Evidence 2 | Prompt the commissioner to verify which source file and version the artist will use without uploading or grading it. | Do not determine image quality, resolution, authenticity, ownership, restoration potential, print suitability, or which version a user should select. |
| Evidence 3 | Include file-naming, metadata, and folder-manifest questions in the portrait handoff checklist. | Do not collect names, relationships, dates, locations, descriptions, tags, filenames, folders, or other metadata from a visitor. |
| Evidence 4 | Ask whether an independently readable preservation copy exists outside the commissioned service. | Do not claim that two copies prevent loss, approve a medium or location, or treat a vendor-hosted copy as independent without evidence. |
| Evidence 5 | Describe preservation as an active review process rather than a one-time permanence promise. | Do not guarantee readability, prescribe a universal replacement schedule for every medium, automate a reminder, or claim that an online service will remain available. |
| Evidence 6 | Ask whether a hosted memorial provides an independently readable export, what the export contains, and which metadata accompanies it. | Do not claim that a vendor offers export, that a browser-saved page is complete, that an export preserves functionality, or that a format will remain readable. |
| Evidence 7 | Separate live memorial availability from possession of independent exported copies and from testing those copies. | Do not promise website uptime, domain renewal, redirect continuity, service survival, full export, restore capability, or long-term link operation. |
| Evidence 8 | Include master, approved, display, export, and documentation version-status questions without inventing a required file set. | Do not prescribe a file format, resolution, color space, layer structure, naming convention, or number of versions for a commission. |
| Evidence 9 | Keep the vendor copy, commissioner copy, and independent backup evidence states separate. | Do not count an unverified copy, guarantee recovery, approve a storage provider, or state that an inaccessible file is preserved. |
| Evidence 10 | Use the hub as the federal preservation-method route and keep vendor features and file decisions separately evidenced. | Do not claim that the Library endorses a vendor, format, platform, QR system, portrait workflow, cloud host, or memorial service. |
| Evidence 11 | Offer this as one official naming approach for a private archive, not as a required artist filename. | Do not rename files, collect filenames, state that another naming scheme is invalid, or claim that naming alone preserves a file. |
| Evidence 12 | Prompt the visitor to decide privately which nonpublic metadata should accompany preservation copies and which should not be displayed. | Do not ask for or publish a person's name, relationship, date, location, event, biography, image description, or other memorial metadata. |
| Evidence 13 | Use the official approach as a planning reference and show each copy and location category as an unresolved evidence state. | Do not guarantee data survival, prescribe a vendor or medium, verify a backup, treat synchronization as backup, or claim that an off-site copy can be restored. |
| Evidence 14 | Explain why a portrait commission should state the source material, creator, deliverables, and intended reproduction and display permissions in writing. | Do not decide originality, fixation, copyrightability, authorship, ownership, infringement, public-domain status, or whether a specific portrait is protected. |
| Evidence 15 | Distinguish possession of a source photograph, portrait file, print, or exported memorial copy from copyright ownership and permission. | Do not decide who owns a physical or digital copy, who owns copyright, whether a use is licensed, or whether a source photograph may be used. |
| Evidence 16 | Publish official method guidance and vendor-question fields only, leaving vendor-specific values unknown until a separate primary-evidence manifest passes review. | Do not name, list, rank, recommend, contact, quote, compare, review, or imply a feature or capability of any vendor or platform. |
| Evidence 17 | Show selected labels, unresolved questions, scope notes, and internal reading routes with a reset action. | Do not calculate a score, select a vendor, provide a legal result, or recommend proceeding with a commission or hosted memorial. |
Questions people ask
Which file format should a memorial portrait use?
The supplied guidance does not prescribe a format for a memorial portrait. Ask for the format used, the role assigned to the file, and any available manifest, while keeping format, resolution, color space, layers, and long-term readability as separate questions.
What is a master file versus a display copy?
They are version-role labels that can be recorded in a handoff. A master may be identified as a version retained for a stated purpose, while a display copy may be identified as the version intended for display. The guidance does not define a required file set or decide which version belongs in either role.
Which metadata should be kept private?
Decide privately which descriptive information should accompany preservation copies and which should not be displayed. Official guidance discusses basic descriptive metadata, including who, what, where, and when, but it does not determine the appropriate privacy decision for a particular memorial.
Should an export include a file manifest?
Ask whether an independently readable export has been identified, what it contains, which metadata accompanies it, and whether a file or folder description is available. The guidance does not establish that a vendor offers an export, that an export is complete, or that it preserves hosted functionality.
Does a readable file prove permission to use it?
No. Readability concerns access to the file as a copy; it does not establish copyright ownership or permission to reproduce or display the work. Keep the readability status and the rights note separate, and verify the source, creator, deliverables, and intended permissions in writing.
Can this page inspect, convert, or store a memorial file?
No. The scope is limited to documentation questions and official method guidance. It does not request or examine files, scan devices, connect to accounts, upload photographs, determine image quality, convert formats, or store memorial material.
Primary sources
- Library of Congress — Personal Digital Archiving Verified 2026-08-26
- Library of Congress — Keeping Personal Digital Photographs Verified 2026-08-26
- Library of Congress — Keeping Personal Websites, Blogs and Social Media Verified 2026-08-26
- Library of Congress — Keeping Personal Digital Records Verified 2026-08-26
- National Archives — Digitizing Family Papers and Photographs Verified 2026-08-26
- U.S. Copyright Office — What Is Copyright? Verified 2026-08-26
- U.S. Copyright Office — Copyright Basics, Circular 1 Verified 2026-08-26
- Memorial Portrait and Digital Continuity Desk validated source and checklist methodology Verified 2026-08-26