What to include in a site about a site: metadata examples

A site about a site has two jobs: preserve the material and explain how the pieces fit together. On the Papajohn Phillips domain, metadata gives archived news, community articles and historical sections a consistent identity. The result is more than a search-friendly index; it is a transparent record of what exists, where it came from and which context a visitor can rely on.

Metadata should do more than repeat a visible title. It captures authorship, dates, language, rights and relationships, then explains whether a document is an original page, an archived copy or a later index entry. That distinction protects historical integrity when sources have uncertain dates, revised text or broken links, and it gives researchers a dependable way to cite material that may no longer exist at its original address.

Australian visitors benefit when this information reflects local context instead of generic automation. English can be identified as en-AU, dates can follow familiar Australian ordering, and community material can retain the names of the places and institutions connected to it. A resource hub of this kind can join personal memory to trusted national collections while giving every preserved page a clear place in the site’s structure.

Why metadata matters for archived pages

Archived pages are valuable because they keep earlier forms of communication available, but their usefulness depends on context. A visitor may arrive from a search result without knowing the publication, period or sponsoring group. A title, concise description, date and source attribution turn that isolated result into a readable item. When the live page has disappeared, an archive location and a clear status label explain what can still be consulted.

Each record should separate content from provenance. The source URL identifies the original location; an archive URL identifies the preserved copy; a capture timestamp records when that copy was made; and a rights statement explains how it may be reused. Relation fields can place a news item within a named historical section or connect it to a related community article. Omitting those distinctions makes pages from different periods appear to be one undated collection.

For the Papajohn Phillips resource hub, lifecycle language should be equally precise. “Historical” describes the function of a section, not the age of every document, and a newly built landing page may point to much older material. Statuses such as archived, superseded, reference only and temporarily unavailable tell visitors whether a link represents an original, a preserved version or a pointer awaiting restoration. Clear labels also reduce duplicate navigation and mistaken citations.

Descriptive metadata examples

Descriptive metadata begins with language people can understand before they open the page. Give each landing page a distinct title that names its subject rather than calling it “Home”, followed by a description that explains the collection, time span or purpose in one or two sentences. For a catalogue of the domain, a title such as “Papajohn Phillips: archived news and community stories” is more informative than a repeated brand name. The same wording can feed search results and social previews without changing its meaning.

Description then needs people, place, time and topic in separate fields. Record the creator or contributor when known, the publisher or archive owner, the original publication date, the date of revision and the date on which a web copy was captured. Subjects should describe the actual article, using a small controlled vocabulary where possible; free-text keywords can support discovery but should not replace a clear summary. Place names such as Sydney or Melbourne belong in spatial coverage when relevant, not merely in an unsearchable sentence in the body.

In JSON-LD, properties such as headline, description, author, publisher, inLanguage, datePublished, dateModified, about, isBasedOn, isPartOf, license and identifier cover much of the essential record. An archived page can use isBasedOn to point to its original source and isPartOf to place it in an archive collection. Dates should distinguish publication, modification and archival capture rather than overloading one value. The visible page and its structured metadata should agree.

Technical metadata that supports preservation

At the technical layer, metadata should help both people and software move through the resource without creating false duplicates. Each page needs a canonical URL, a unique meta description and a place in the XML sitemap. Open Graph fields can provide a readable title, summary, image and en_AU locale for shared links. Canonical tags should clarify which address represents a record, while noindex can keep duplicate snapshots out of search results when they have no independent value. Archived navigation still needs discoverable text and breadcrumbs.

Preservation metadata extends beyond browser tags. A preservation record can note the source address, archive provider, capture time, media type, checksum, redirect history and the result of the most recent link check. Checksums help future custodians confirm that a stored file has not changed; redirect histories prevent a renamed folder from breaking older citations. A failed fetch should be logged with its status, such as not found or gone, and the next review date. These fields distinguish an intentional historical state from a technical failure that needs attention.

Outbound references need their own treatment so they are not mistaken for material owned by the archive. If a record cites Telegram store safety guide, its metadata should preserve the destination, original language, author or publisher where known, access date and reason for the citation. The archive’s interface language may remain English while the source language is recorded separately. If the external page later fails, the citation, capture details and available text should remain together rather than leaving a bare link or an unverified summary.

Community context and editorial stewardship

Community material needs context beyond a list of keywords. A preserved feature such as many mamas, many papas should carry a short editorial summary, the named author or editor when available, the original publication date, both web locations, subjects, rights information and any relevant community or cultural note. If a contributor is uncertain or the page was assembled from several records, say so in the description. This approach helps readers understand the story’s significance without pretending the catalogue knows more than the surviving evidence.

For Australian readers, metadata can make the resource feel properly situated. Set the language to en-AU, use Australian forms such as “organisation” and “licence”, and show dates as 18 March 2025 in the interface while storing machine-readable values in ISO format. Place names such as Sydney, Melbourne and Canberra should remain attached to the stories they describe rather than disappearing from summaries. Trove and the National Library of Australia in Canberra offer useful models for collection-level description, community digitisation and stable citations.

The global .com address does not make the project unrelated to Australia. A stewardship note can identify the Australian market and community networks the hub serves, especially when the archive draws on local newspapers, volunteer groups and neighbourhood publishing. If the owners later consider a .au domain or an auDA-aligned registration, that is a governance decision about identity, continuity and cost, not a metadata shortcut. Existing links should remain stable while any future domain change is planned and tested.

Metadata choices for durable stewardship

A workable metadata record should be proportionate to the page, yet consistent enough to maintain across the collection. Small archival items may need only a title, source, date, status and relation fields; collection landing pages also require coverage, rights, ownership and contact information. Define required fields once, map them to the visible interface and schema.org vocabulary, then document exceptions in the record rather than in a separate temporary spreadsheet.

Before publishing or revising a page, apply these checks:

Use those checks to keep the Papajohn Phillips domain useful beyond a single redesign. Explore the preserved articles and historical sections, follow the internal navigation, and inspect whether each item gives enough information for responsible citation. If you own relevant material, recognise a missing community story or want to clarify an existing record, contact the domain steward with the page address, approximate date and a brief explanation of its provenance. Please do not send sensitive personal information in an initial enquiry. A clear, documented contribution can then be assessed, preserved and connected to the right section without disturbing the wider archive.