Atlas project retired

iBoss Web History Archive Search Utility

Historical utility for searching archived iBoss web-history logs for investigations or compliance requests.

Internal-only entry. Do not publish externally without review.

Type: System
Lifecycle: Retired
Last touched: 2026-03-24
Visibility: Internal

Purpose

Preserve a retired investigative utility record without presenting it as part of the current BOUSD integration inventory.

Current state

Aether includes `iBossArchiveSearch.sh`, which pre-processes archived log files, applies IP or criteria filters, and produces result datasets. The tool is now considered old and irrelevant to the current integration inventory, so Atlas keeps it only as retired historical context.

Next step

Either archive the record long-term or add any required retention or legal-handling notes if this historical utility must remain documented.

Interfaces

Inputs

iBoss web-history archives.

Outputs

filtered result files and investigation reports.

Reality to Action trace

Reality Ingestion

Not in scope.

Canonical Storage

Not in scope.

Automation Engines

Not in scope.

Human Interfaces

Contributes in this stage.

Operational Adoption

Contributes in this stage.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Data integrity and contracts

Source of truth rules

iBoss web-history archives. remain the authoritative upstream inputs for this workflow.
filtered result files and investigation reports. should be treated as downstream copies, recipients, or operational consumers rather than the authoring system.

Safe handling

Protect credentials, generated files, logs, and any transient export artifacts.
Treat student identifiers, rosters, and related records as FERPA-restricted data.
Limit staff identity, employment, or account data to approved administrators and business owners.

Operational notes

Reliability posture

script output and result files provide run evidence; centralized monitoring is not documented. Failure impact: slower compliance response and manual analysis burden. Manual fallback: vendor console review or manual log parsing..

Observability

script output and result files provide run evidence; centralized monitoring is not documented.
Failure impact: slower compliance response and manual analysis burden..
Manual fallback: vendor console review or manual log parsing..

Security and privacy

access to web-history archives. Classification: highly sensitive student and staff browsing data. access must follow legal and policy requirements.

Dependencies

Upstream

archive availability, criteria accuracy, and storage capacity.

Downstream

filtered result files and investigation reports.

Ownership

Owners

Technology Services

Users

Technology Services, Technology Services / compliance stakeholders

iBoss Web History Archive Search Utility

Operational Notes

Method: log pre-processing, filtering, and TSV/CSV output generation.
Implementation: iBossArchiveSearch.sh, criteria files under config/iboss/, and archive/result storage under data/iboss/.
Trigger / frequency: on-demand investigations or records requests.
Failure impact / fallback: slower compliance response and manual analysis burden. Manual fallback: vendor console review or manual log parsing..
Related references: iBossArchiveSearch.sh.

Registry Alignment

Registry status: removed from the current BOUSD integration inventory; former INT-075 should be treated as obsolete.
Registry clarified: Aether includes iBossArchiveSearch.sh, but Atlas no longer treats it as an active integration or helper workflow.
Validation gaps: none for active-inventory alignment; only historical retention expectations remain if the page is kept.