Road Map

Partner organizations currently store documents and data in many locations. This can make it difficult to:

• find information later
• determine which version is current
• maintain access when staff leave
• safely share restricted information
• publish selected information to the public

SAGEinfo is intended to provide one durable place to organize, protect, find, update, and publish shared environmental and conservation information.

SAGEinfo now has a working foundation for organizing, protecting, finding, reviewing, and publishing shared information. Delivered work includes:

• validated uploads with clear results and safe cleanup when an upload fails
• titles, descriptions, dates, organizations, projects, visibility, document types, and controlled tags
• authorized search, document details, previews, protected downloads, and archive exports
• Public, Internal, and Private access enforced by the backend
• separate review, approval, publication, and unpublication actions
• document version history with one current version and retained authorized older versions
• organizations, shared projects, invitations, account settings, and delegated permissions
• manual tagging, Auto-Tag assistance, reviewed tag lists, and incorrect-tag removal
• public Published and Contact pages, user documentation, and targeted accessibility improvements
• validated backup packages, a detailed recovery procedure, health checks, and expanded regression testing

The recovery procedure is documented and ready to use. Current work turns that procedure and the stable application into a dependable operating practice for a controlled partner beta. Priorities are:

• a named operational owner and clear escalation contact
• automatic scheduled backups with success and failure monitoring
• a secure off-site backup destination
• regular recovery drills using the documented staging and validation procedure
• alerts for service, readiness, disk, log, and backup problems
• a repeatable release, deployment, verification, and rollback process
• external verification of the public production path after each release
• minimum rules for acceptable data, access, publishing, retention, takedown, and incident response
• one formal beta feedback process with clear blocker and completion criteria

After the controlled-beta operating foundation is in place, improvements should follow real partner feedback and careful review of existing records. Strong candidates include:

• classification of older archive files without guessing at missing information
• reviewed backfill of useful legacy metadata and tags
• manager and administrator operating guides
• formal accessibility testing in addition to the improvements already delivered
• dependency, license, and software inventory maintenance
• a decision about malware scanning before accepting higher-risk uploads
• account recovery by email
• clear definitions for programs, locations, sites, sources, and record status before adding new structures

Beta findings should determine which of these items provides enough value to enter the next release.

These features may improve collaboration after beta feedback confirms the need and the required information structures are agreed upon:

• controlled programs, locations, specific sites, and source records
• public organization, program, project, and collection pages
• links from partner websites to SAGEinfo collections
• notifications when content is uploaded or updated
• record sharing between authorized users
• favorites or pinned content for quick access
• CSV exports of search and collection results
• site maps for browsing
• expanded partner onboarding and page-specific help
• search inside supported document contents

These are candidates, not promises. Each item should have a clear user need, permission model, owner, and acceptance test before implementation.

These optional capabilities require separate security, privacy, capacity, cost, and maintenance planning:

• selected-folder, one-way imports from Google Drive, OneDrive, or SharePoint
• revocable connection permissions, duplicate prevention, and source tracking for imports
• ArcGIS and mapping connections
• GIS and raster file support
• support for large files
• video and audio support
• natural-language search or a source-linked retrieval assistant
• broader regional participation

They remain deferred until controlled-beta operations are dependable and partner evidence shows that the expected value justifies the added risk and upkeep.

SAGEinfo is not initially intended to replace:

• email
• Microsoft Teams
• Google Drive
• OneDrive
• SharePoint
• ArcGIS
• live document editing systems
• partner organization websites

Instead, SAGEinfo is intended to provide the organized archive, discovery, controlled-sharing, and public-publishing layer that works across those systems. Partners continue using their existing tools while SAGEinfo serves as the shared record layer.