In our regional and publisher research, we experimented with websites, video, embeddings, geographic observations and reconstruction of the larger story around a place. RSS kept returning as a surprisingly useful piece of the system.
A feed is not a complete archive. It usually omits much of the site's history and structure. But it gives a reasonably cheap signal that a publisher released something new and supplies a place to follow up.
Different sources answer different questions §
A website crawl is helpful for understanding pages and their relationships. A video recording provides speech and visual context. A geospatial dataset describes locations. An RSS feed helps answer what changed recently?
That time dimension matters. If a construction project is mentioned in an old article and again in a new one, the two sources should not automatically collapse into a timeless summary. Publication timestamps, corrected URLs and changes to source content belong in the record.
The RSS specification[1] explains how items and channel metadata are represented. It is simple enough that small publishers can support it without a large technology platform.
Feeds are inputs, not identities §
A feed item may point to a page that later changes. Two feeds may syndicate the same article. The source library needs the original publisher, stable article address and observation times to separate identity from delivery.
Aurekai has collected publishers, reading rooms and channels. Their feeds are useful because they give the publication a pulse; profiles and collections give the material context.
The lesson is not to replace newer protocols with RSS. It is to keep a straightforward technology when it solves its part of the problem economically.
Sources and further reading
References point to original material linked in the essay, not independently invented citations.
- RSS specificationrssboard.org↩
Related reading
More articles that explore this subject from another angle.