Build a wildlife archive as three connected layers: a structured catalog of observations or collection items, original media stored at a stable location, and a public interface for searching and exploring the records. Give every record and media item a durable identifier, describe the relationship between them in metadata, and decide early whether the archive should publish data through GBIF or serve it only through its own site.
How do I build a wildlife archive website?
Start with the collection and its uses, not the choice of web framework. A useful archive connects descriptive records, original media, and the visitor-facing experience without forcing those pieces into one system. Keep a canonical record store and media catalog; build the site’s search index or browsing layer from that data so the public interface can evolve without losing the underlying records.
As an Amazon Associate I earn from qualifying purchases.
1. Define what an archive item represents
Decide whether a record describes a specimen, an observation, a media asset, or another collection object. These are related but not necessarily identical things: one observation may have several photographs or recordings, and one media item may document more than one taxon or event. Model those relationships explicitly rather than repeating all descriptive details in every file name.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsAt minimum, give each record a stable identifier and record the descriptive fields your organization can maintain consistently. Depending on the collection, that may include a title, taxon or species association, creator, date, location, rights information, and links to associated media. Keep uncertain or unavailable values distinguishable from confirmed values.
#1 Best Overall
2. Store media separately and link it reliably
Host original photographs, audio, and video in a media system suited to file delivery. The catalog should store a stable reference to each asset, its type, and useful context. Do not treat GBIF as the archive’s original-file store: GBIF says it does not host original multimedia. Dataset publishers host the media elsewhere and include a direct URL for each file. GBIF can integrate still images, sound, and moving images; other linked media types may require a visitor to follow the supplied link. Its guidance also cautions against using iNaturalist as dataset image hosting when that would duplicate observations. See GBIF’s multimedia guidance.
3. Build the discovery interface around real tasks
Provide a search field and filters that reflect the fields people actually use, such as taxon, place, date, media type, or collection. Make results understandable before a visitor opens an item: show a useful title, a thumbnail where available, and enough metadata to distinguish similar records. Item pages should connect the descriptive record to its media and any relevant source or rights details.
For larger collections, the public site can query the archive’s data service or use an index derived from the canonical records. GBIF’s REST API can support repeatable JSON-based queries and integrations in other websites; its developer documentation describes available API services. Treat an API as a way to exchange or retrieve data, not as a replacement for designing the archive’s own navigation and item pages.
How do I make a searchable wildlife database?
A searchable database needs consistent fields, stable relationships, and a plan for keeping search results current. Keep the data model independent of the visual layout: a record should remain identifiable and useful even if the website’s theme or search tool changes.
Choose a practical record model
- Record identity: assign a durable identifier that remains attached to the item when titles, URLs, or interface components change.
- Description: store a meaningful title and the taxonomic or collection context needed to interpret the item.
- Time and place: include date and location when appropriate, and distinguish unknown or withheld details from ordinary empty values.
- Media relationship: link records to one or more media assets using stable references rather than relying on a filename as the only connection.
- Rights and attribution: record creator and usage information when known, so the interface and any export can communicate it clearly.
These are implementation recommendations for a durable catalog, not a claim that GBIF requires every field listed here. Align the fields and formats with the collection’s publishing goals and the data standards it intends to use.
Make search and browsing maintainable
Define how edits reach the public search index, how deleted or withdrawn items are handled, and how links are checked over time. Test searches with real collection questions: can a visitor find a species by its accepted name, browse records from a place or date range, and reach a media item from its record? For map-based discovery, provide a text or tabular route to the same essential information rather than making the map the only way to explore it.
Can I use GBIF data on my website?
Yes. GBIF provides biodiversity data that can be incorporated into other websites through its API, and organizations can publish datasets to the GBIF network so they can be discovered beyond the local archive. Those are related but distinct uses: querying GBIF data helps a site integrate records, while publishing a dataset makes an organization’s own data available through GBIF’s network. Neither choice builds the visitor-facing archive interface for you. See GBIF occurrence search and its API overview.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →For organizations preparing their own datasets, GBIF’s Integrated Publishing Toolkit (IPT) is free open-source software. GBIF describes several hosting patterns: an organization can self-host it, use a national or thematic node or trusted hosting centre, or use a regional cloud IPT. GBIF currently accepts datasets directly from organizations; individuals should work through an affiliated organization or consider publishing a data paper. Consult GBIF’s IPT page for the publishing route and hosting context.
Publishing is not automatic merely because records appear on a website. The organization needs to prepare a dataset and choose a suitable publishing route. If the archive is run by an individual rather than an organization, GBIF’s stated guidance points to working through an affiliated organization or considering a data paper.
Rank #4
Where should I host wildlife photos and audio?
Keep original files on storage or a media service designed to serve them, and preserve stable direct URLs in the catalog or published dataset. The archive should still retain useful metadata if an asset temporarily fails to load: a descriptive title, media type, creator or rights information when known, and the item’s connection to a taxon, place, or date where appropriate.
Separate original files from derivatives such as thumbnails. That lets the site offer quick-loading previews without treating a small display copy as the archival source. Establish who is responsible for backups, link stability, and access controls before choosing a host; the appropriate arrangement depends on the project’s collection, staff, geography, and service requirements. The available guidance does not establish a universally best provider or price tier.
What is IIIF, and do I need it?
IIIF (the International Image Interoperability Framework) is a set of APIs for interoperable delivery and presentation of digital objects. Its Image API describes how to request selected image regions and sizes, which can support thumbnails and deep zoom. Its Presentation API packages an object’s structure and metadata. The IIIF Image API and IIIF Presentation API explain those roles.
IIIF is worth considering when high-resolution access, portability between institutions, annotation, structured sequences, or reuse in compatible viewers matters. A small archive with ordinary image delivery and basic search may not need the extra infrastructure. A typical IIIF implementation involves an image server or compatible hosted service, manifests describing resources and structure, and a viewer. Viewer capabilities vary: pan, zoom, rotation, annotation, comparison, and audiovisual playback depend on the viewer and the available manifests. The IIIF implementation overview describes the general approach.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How do I make an image and audio archive accessible?
Plan accessibility as part of the record model and publishing workflow. WCAG 2.2 requires text alternatives for non-text content and includes media-specific provisions, such as captions for prerecorded synchronized media and alternatives for prerecorded audio-only and video-only content. See the W3C WCAG 2.2 Recommendation.
- Write meaningful text alternatives for content images, rather than repeating filenames or leaving visitors without equivalent information.
- Label search fields, filters, media controls, and viewer tools; ensure visitors can operate them by keyboard.
- For prerecorded synchronized video, plan captions. For audio-only or video-only items, provide the applicable alternatives under the project’s conformance target.
- Include transcripts or descriptions in the item workflow when speech or other essential information is present in a recording.
- Offer a text or tabular route to essential map information, rather than requiring visitors to interpret a visual map.
The exact conformance target depends on the project and jurisdiction. Check applicable current law before describing a particular accessibility requirement as a legal obligation.
Recommended Free Tools
How should I choose an implementation route?
Choose based on operational capacity and the archive’s needs, rather than treating one platform or standard as a universal answer.
| Decision | Consider this route when | What to plan for |
|---|---|---|
| Self-host or use hosted IPT | The organization intends to publish datasets through GBIF. | Self-hosting provides direct operational control but requires staff to maintain the service. A node, trusted hosting centre, or regional cloud IPT shifts some operations to a host; GBIF does not provide a neutral cost comparison. GBIF IPT |
| Ordinary image delivery or IIIF | Basic image display may suit a small catalog; IIIF is relevant when deep zoom, structured presentations, annotation, or reuse across viewers is important. | IIIF adds server, manifest, and viewer decisions. IIIF overview |
| Local search or GBIF integration/publication | Use local discovery for the archive’s own experience; consider GBIF integration or publication when broader biodiversity-data discovery is a goal. | API integration and dataset publication solve different problems; publication requires dataset preparation and an appropriate organizational route. GBIF API |
| Media hosting arrangement | The archive has original photographs, recordings, or video to serve and maintain. | Choose a system and workflow that preserve stable direct links and assign responsibility for file delivery and upkeep. GBIF multimedia guidance |
| Accessibility workflow | Every archive, particularly one expecting to grow or publish varied media. | Budget editorial capacity for alternatives, captions, transcripts, and labeled controls as part of record creation and publication. WCAG 2.2 |
Before selecting services, document the collection’s scale and formats, staffing, geographic and procurement constraints, rights, expected availability, and service-level needs. The standards and service documentation above support an architecture, not a vendor ranking, project budget, or jurisdiction-specific legal opinion.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
