Administrators Introduction to Atlas System - KolderTech/aodtdoc GitHub Wiki

Administrator's Introduction to the Atlas Of Drowned Towns System

Welcome to the Atlas of Drowned Towns

Welcome to your role as an Atlas Administrator! This manual provides a comprehensive introduction to the Atlas of Drowned Towns system, your responsibilities as an administrator, and how to effectively manage this important digital humanities project.

What is the Atlas of Drowned Towns?

The Atlas of Drowned Towns is a digital humanities platform dedicated to preserving and sharing the history of communities that were submerged by dam construction across the United States. Led by Dr. Bob H. Reinhardt, Associate Professor of History and Project Director at Boise State University, this project serves as a vital historical archive and educational resource.

Project Mission

  • Preserve History: Document and preserve the stories, artifacts, and memories of communities lost to dam construction
  • Educate the Public: Provide accessible historical information about the social and environmental impacts of dam projects
  • Support Research: Enable academic research and scholarly analysis of this important historical phenomenon
  • Community Engagement: Allow community members to contribute their own stories and artifacts

Historical Context

Throughout the 20th century, hundreds of communities across the United States were flooded by dam construction projects. These "drowned towns" represent lost communities, displaced families, and submerged cultural heritage. The Atlas project works to ensure these stories are not forgotten.

System Architecture Overview

The Atlas of Drowned Towns system is a complex, multi-component digital platform that combines web applications, databases, and content management systems. Understanding this architecture is crucial for effective operation.

System Components

Frontend Applications

Backend Infrastructure

  • AWS MySQL Database

    • Stores all collection metadata
    • Asset records, tags, and relationships
    • User accounts and system configuration

  • AWS Lambda Functions

    • Serverless data processing
    • API endpoints for data access
    • Dynamic content generation

  • AWS API Gateway

    • REST API for data access
    • Connects frontend applications to backend services
    • Handles data requests from map and website

  • BSU MEC402 Server (mec402.boisestate.edu)

    • File storage for collection artifacts
    • Hosts uploaded images, documents, and media files
    • Provides direct file access URLs

  • WordPress.com

    • Content management for narratives and stories
    • Blog posts and project updates
    • Community story submissions

Development Infrastructure

  • GitHub Repositories
    • Source code for all system components
    • Documentation and project files
    • Version control and collaboration

Understanding the Collection

The Atlas Collection is the heart of the system - a carefully curated digital archive containing historical materials related to drowned towns.

Collection Structure

Files vs. Assets

The collection uses a two-tier system:

  • Files: The actual digital objects (photos, documents, audio files, etc.)

    • Uploaded through the Portal
    • Stored on MEC402 server
    • Each file gets a unique URL for access

  • Assets: Metadata records that describe and organize the files

    • Stored in AWS MySQL database
    • Contain tags, descriptions, and relationships
    • Control how items appear on the website and map

Document Types

Assets are organized into specific document types:

Geography

  • Locale: Regions, Basins, Projects, and Places
  • Dams: Information about dam construction projects
  • Towns: Historical data about submerged communities

Artifacts

  • Photo: Historical photographs
  • News: Newspaper articles and clippings
  • Threedart: 3D objects and models
  • Oral: Oral history recordings and transcripts
  • Official: Government documents and official records
  • Personal: Personal papers and family documents
  • Birdseye: Bird's eye view images
  • Aerial: Aerial photographs
  • Maps: Historical maps and cartographic materials

Stories and Articles

  • Narrative: Scholarly articles and historical analysis
  • Community: User-submitted stories and memories

Internal

  • File: Basic file records (not publicly visible)
  • Deleted: Items marked for removal
  • Missing: Items without proper document type

Metadata Schema

Each asset contains structured metadata:

Required Tags (for public display):

  • atlasname: Unique identifier
  • longitude/latitude: Geographic coordinates
  • region/project/place: Geographic organization
  • uri: File URL (for artifacts)

Tombstone Tags (descriptive information):

  • name: Display name
  • year: Date information
  • sources: Attribution and provenance
  • approximate: Data quality indicators

Your Role as an Administrator

As an Atlas Administrator, you are responsible for the day-to-day management and curation of the collection. Your work directly impacts how the public experiences and learns from this historical archive.

Primary Responsibilities

Data Management

  • Upload and organize new artifacts and files
  • Create and maintain asset records with proper metadata
  • Ensure data quality and accuracy of all collection items
  • Manage file organization and storage structure

Content Curation

  • Review and approve community submissions
  • Add descriptive metadata to enhance discoverability
  • Maintain content standards and quality guidelines
  • Organize items by geographic and thematic categories

Quality Control

  • Verify accuracy of historical information
  • Check file integrity and accessibility
  • Ensure proper attribution and source documentation
  • Maintain consistent metadata standards

Public Interface Management

  • Control visibility of items on website and map
  • Manage featured content and highlights
  • Respond to user feedback and requests
  • Monitor system performance and user experience

Skills and Knowledge Required

Technical Skills

  • Basic computer literacy and file management
  • Understanding of metadata and data organization
  • Familiarity with web interfaces and content management
  • Attention to detail for data accuracy

Historical Knowledge

  • Understanding of US history and dam construction projects
  • Knowledge of historical research methods and standards
  • Familiarity with archival practices and documentation
  • Appreciation for community history and cultural heritage

Communication Skills

  • Clear written communication for metadata and descriptions
  • Professional interaction with community contributors
  • Collaboration with project team members
  • User support and assistance

Getting Started: Your First Steps

1. Access the System

2. Familiarize Yourself with the Portal

The Portal has three main pages:

  • Sheet Page: Spreadsheet-like interface for browsing and searching assets
  • Asset Page: Individual asset editing and creation
  • File Explorer: File upload and organization interface

3. Understand the Workflow

Typical administrator workflow:

  1. Receive new materials or community submissions
  2. Upload files to appropriate folders
  3. Create asset records with proper document types
  4. Add metadata and descriptive tags
  5. Review and approve for public display
  6. Monitor public interface for issues

4. Learn the Tools

  • Search and Filter: Use the Sheet page to find existing assets
  • Edit Metadata: Use the Asset page to modify asset information
  • Upload Files: Use the File Explorer to add new materials
  • Quality Check: Verify items appear correctly on public interfaces

Next Steps: Detailed Documentation

This introduction provides the foundation for your work as an Atlas Administrator. For detailed procedures and specific tasks, refer to these additional manuals:

Essential Reading

  1. Atlas Portal Manual - Detailed Portal interface guide
  2. Atlas HowTo Add Data - Step-by-step data addition procedures
  3. Atlas Collection Data Structure - Complete data organization guide
  4. Data Collection Schema - Metadata standards and requirements

Advanced Topics

  1. Atlas Administrator Cookbook - Complete procedures and workflows
  2. Atlas Portal Data Management Cookbook - Specific data management tasks
  3. Supported File Types - File format specifications and requirements
  4. Content Quality Standards - Guidelines for maintaining collection quality

System Administration

  1. Where Is What - System component locations and architecture
  2. BSU Servers - Infrastructure and server information
  3. Security Procedures - Access control and data protection
  4. Backup and Recovery - Data protection procedures

Getting Help and Support

Team Resources

  • Project Director: Dr. Bob H. Reinhardt
  • Development Team: Technical support and system maintenance
  • Fellow Administrators: Peer support and knowledge sharing
  • Community Contributors: Source of new materials and feedback

Documentation Resources

  • Complete Manual List - Overview of all available documentation
  • Documentation Index - Navigation guide for finding specific information
  • FAQ and Troubleshooting - Common issues and solutions
  • Training Materials - Additional learning resources

Contact Information

  • Technical Issues: Contact development team
  • Content Questions: Reach out through project channels
  • Training Needs: Coordinate with project leadership
  • System Access: Contact system administrator

Continuous Learning

The Atlas system continues to evolve, and your role as an administrator will grow with it. Stay informed about:

  • System Updates: New features and improvements
  • Best Practices: Evolving standards for digital humanities projects
  • Community Needs: Changing requirements from users and contributors
  • Technical Advances: New tools and methods for digital archiving

Welcome to the Atlas of Drowned Towns team! Your work helps preserve important historical heritage and makes it accessible to researchers, students, and community members worldwide. Together, we ensure that the stories of drowned towns are never forgotten.

Last Updated: [Current Date]
Document Version: 1.0
Next Review: [Future Date]