How automatic updates work
Collection runs independently
Scheduled background jobs check configured official and publisher feeds, APIs and permitted pages. They preserve versions, deduplicate records and update the local search index. Routine collection and classification do not use AI. A browser does not need to stay open.
Collection and publication differ
A collected record can be pending editorial review. Supported metadata-only feeds can publish automatically under their configured source policy. Explicit editor holds, rejected records and access restrictions remain enforced.
Understand timestamps
Publication date belongs to the source. First detected records when TLG found the item. Last checked and last successful check describe collection health. Missing dates are never invented. An empty check can be successful.
Failures and restrictions
Robots restrictions, authentication requirements, publisher terms, unsupported connectors and unavailable pages can prevent collection. These are not silently bypassed. Follow the original source or report a coverage issue to info@thelegalgazette.org.
Refresh and corrections
Visible update pages recheck regularly and preserve your search filters. Return to a tab to refresh immediately. A source change can require review again; a withdrawn or superseded notice keeps its history. Report a broken link or correction with the article/notice URL and supporting evidence.
Questions or corrections: info@thelegalgazette.org.