How to build a simple RSS feed for an archive’s new additions
How to build a simple RSS feed for an archive’s new additions comes down to a publishing habit: tell readers when the collection has grown. A syndication feed turns new catalogue records, restored pages and community articles into a repeatable stream. It does not replace the archive. It acts as a signpost, helping subscribers move from a recent item to the full record and its preserved context.
This matters for a small resource hub such as the resource hub, where historical sections sit behind menus and archived reports. A feed creates a direct route into those sections without asking visitors to inspect the whole site. It also supports people who follow the archive through software rather than bookmarks, giving them a timely view of newly added material.
Australian readers may encounter the archive through a library service, local historical society or community newsletter. The State Library of New South Wales in Sydney and Museums Victoria in Melbourne connect individual items with wider collecting stories and public programmes. A focused feed carries that sense of discovery: one concise entry at a time, with enough context to decide why a record is worth opening.
Little technical equipment is needed to begin. A text editor, a small script or a publishing-system feed feature is enough, along with a stable place to host an XML file. Decide what the feed describes, create a channel, add each new item and test the result. Keeping the process small and repeatable makes it easier to sustain than a service the archive cannot maintain.
Define what counts as a new addition
Begin with an inclusion rule. “New” might mean an accession created this week, a newly digitised photograph, a recovered web page or a community submission accepted into the collection. Each category can have a different pace, so “latest” may hide useful distinctions. Write the rule down and keep it consistent; readers trust a feed that behaves predictably.
Give every entry a permanent landing page, even if its descriptive page moves later. A stable permalink lets feed readers return to the same record and gives you room to reorganise navigation. The website preservation timeline is a useful reminder that preservation work has stages: a newly found artefact may still need metadata checks, rights review or a durable URL before syndication.
Group material thoughtfully. A digitised bundle may contain forty pages, but publishing forty almost identical entries can overwhelm subscribers. One item can represent the bundle while its description names the collection, date range and level of description. For large releases, publish representative records and link each to the full catalogue view. This preserves detail without turning the feed into a second catalogue.
Create a small RSS channel
The feed can live at a permanent address such as /feeds/archive.xml. Use the same address whenever possible, because changing it breaks subscriptions unless you configure a redirect. Reserve the path before launch, include it in the site footer and test it from a browser. A short explanatory page beside it can show recent additions in ordinary HTML for people whose reader cannot display XML.
Start with a valid RSS 2.0 document. The channel identifies the archive, while each item points to one addition:
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Community Archive New Additions</title>
<link>https://example.org/archive/</link>
<description>New records, restored pages and community contributions.</description>
<language>en-AU</language>
<lastBuildDate>Sun, 05 Oct 2025 09:00:00 +1100</lastBuildDate>
<atom:link href="https://example.org/feeds/archive.xml"
rel="self" type="application/rss+xml"/>
<item>
<title>Community radio transcript added</title>
<link>https://example.org/archive/items/community-radio-transcript</link>
<guid isPermaLink="true">https://example.org/archive/items/community-radio-transcript</guid>
<pubDate>Sun, 05 Oct 2025 09:00:00 +1100</pubDate>
<description>A transcript from the 1978 local radio collection is now available.</description>
<category>Community submissions</category>
</item>
</channel>
</rss>
Channel-level title, link and description are required for a dependable feed; language, publication time and a self-reference help software interpret it. Keep the channel title stable as items change. The self-link identifies the XML document aggregators loaded and reduces the chance of copying an item into the wrong feed.
Save the file as UTF-8 and escape special characters such as ampersands in titles. Validate the document before deployment, then open it in two feed readers. Browser display confirms that the XML is reachable; reader testing confirms that titles, links and summaries arrive correctly.
Make each entry useful
Item titles should name the addition rather than announce the feed’s existence. “Community radio transcript added” is more informative than “New from the archive”. Put the permanent item URL in the link element and repeat it as a GUID when the URL is stable. If records have catalogue identifiers, those can become GUIDs instead, provided an identifier will never be reused.
The description can contain a short summary, collection name, date, creator and rights credit. This is enough for a reader to judge relevance before opening the record. Avoid stuffing every catalogue field into the feed: long encoded HTML is difficult to scan and harder to maintain. Categories such as “Local history”, “Web archive” and “Community submissions” help readers filter a busy stream. For multimedia, add enclosures only when files are hosted at stable public addresses; otherwise link to the landing page.
Dates need particular care in Australia. Store source timestamps in UTC when your system manages multiple time zones, then show the relevant local offset. Sydney uses AEST or AEDT depending on daylight-saving rules, while other states and territories have different offsets and seasonal changes. An incorrect local time can make a new item look older than it is, so test daylight-saving boundaries as well as ordinary dates.
Publish and refresh the file reliably
For a static site, build the XML during each deployment. A script can read the newest records from a JSON file, CSV sheet or database query, sort them by publication date and write the feed to a fixed path. A content management system may provide RSS output that can be copied to your chosen address. The important result is one public XML document containing recent entries.
Schedule refreshes to match the archive’s publishing rhythm. Weekly may suit a slow-moving historical collection; daily can suit a busy project adding community submissions. An automated job reduces missed updates, but it should not overwrite the last good file with an empty result after a failed query. Keep a previous copy, check the expected item count and publish only after validation succeeds.
Treat the feed address as part of the archive’s long-term infrastructure. Put it in the website repository, include it in backups and redirect any old feed URL to the new location. Monitoring can be modest: check the HTTP response, inspect the newest dates and review a monthly error log. This preserves the simple public interface while giving stewards evidence that subscriptions still work.
Reach readers across Australia
Discovery does not end with the feed icon. Add a visible “Subscribe” link on the archive homepage and new-material section. Mention the feed in newsletters and community mailing lists, but describe what arrives—perhaps a weekly roundup of catalogue additions—so people know what they are signing up for. The main domain, collection pages and article pages can all point to the same permanent feed.
Local channels can amplify an archive without making the feed feel promotional. The National Library of Australia’s Trove service offers a familiar national context for catalogue records, while local libraries and historical societies can share relevant additions. For material involving place, include suburb, state or territory names in the description so searches by residents can surface it.
Community sources need respectful presentation. The material gathered through Rise in PACT illustrates how local history gains value when people connect records to lived experience. Syndicate those additions under a clear community label, retain creator credits and avoid presenting institutional summaries as direct testimony. Readers can discover the material through an ordinary subscription and understand who produced it.
Design for mobile use and uneven connections. Keep descriptions brief, make destination pages lightweight and ensure images have useful alternative text. Many Australians check updates on a phone during a commute or while using mobile data, so a fast feed is more useful than a heavy alternative version. Provide the full record on the web, but do not force every reader to download large files before deciding whether an item matters.
Compare formats and keep the archive visible
RSS 2.0 is usually the shortest route to a dependable archive feed. Atom can carry richer links and authorship details, while JSON Feed is convenient for custom applications. The choice matters less than consistency: publish at a stable URL, retain readable summaries and test with the readers your audience actually uses. For a small team maintaining historical material, a static RSS file is often easier to explain and preserve.
The comparison below focuses on syndication rather than preservation. An archive still needs durable landing pages, metadata checks and clear provenance; a feed only announces the material. A static file avoids a permanent dependency on a third-party feed service, although it requires occasional maintenance. Use richer formats when a genuine requirement calls for them, not merely because newer syntax is available.
| Format | Best fit | Main strength | Main limitation |
|---|---|---|---|
| RSS 2.0 | A small, static archive | Familiar format with broad reader support | Carries less rich metadata than Atom |
| Atom 1.0 | Feeds needing fuller links and authorship | Strong linking and extensible metadata | Reader support and implementation vary |
| JSON Feed | Custom applications and internal dashboards | Clean, accessible JSON for developers | Fewer traditional feed readers recognise it |
Publish the first feed with a clear Subscribe link on the resource hub, a permanent XML address and a short explanation of the updates readers will receive. Test it in a browser and two feed readers, then keep the same schedule and format as the collection grows. This small publishing routine gives the archive a living connection with its audience while leaving the underlying records durable, understandable and easy to steward.