Master Progress Log Maintenance Guidance
This document provides the operational instructions for updating and maintaining the Master Progress Log, which serves as the central ledger for all files within the Scole Archive. It outlines the precise procedures for logging new entries, exporting data, and verifying strict date formats to ensure total compliance with the Scole Archive Naming Standard (SANS).
Archive file
Scole-01-ADM-01-Master-Progress-Log-Maintenance-Guidance.txt [Drive]
Document content
Below is the plaintext HTML extraction of the Archive file.
=====
FILE ID: Scole-01-ADM-01-Master-Progress-Log-Maintenance-Guidance.txt
LOCATION: 01-ADM-Administrative/ADM-01-SANS-Documentation/
ARCHIVE-ID: Scole-01-ADM-GUI-03
PURPOSE: Instructional guide for maintaining the Master Progress Log.
=====
---
ARCHIVE-ID: Scole-01-ADM-GUI-03
LOCATION: 01-ADM-Administrative/ADM-01-SANS-Documentation/
SUBJECT: Master Progress Log Maintenance Guidance
DATE: 05/10/2026
TAGS: #MasterLog #DataEntry #SpreadsheetMaintenance
---
1. OVERVIEW
The Master Progress Log serves as the primary ledger for all files created within the Scole Archive. To ensure 100% compliance with the Scole Archive Naming Standard (SANS), the log is maintained via the Gemini Research Interface.
2. LOGGING NEW FILES
When a researcher adds a new file to the archive, they must notify the AI interface to update the ledger.
- Command: "Add [Full File Name] to the Progress Log in [Internal Path]."
- Requirement: The file name must include the full numerical-alpha prefix (e.g., Scole-08-SES-).
3. EXPORTING THE LOG
At regular intervals, or upon completion of a series, the researcher should request a full export of the log for synchronisation with the master internal spreadsheet.
- Command: "Generate a Progress Log update."
- Output: The system will provide an A-Z sorted table by path and name.
4. AUDIT & VERIFICATION (DATE STANDARDS)
The AI interface performs an automated check during the logging process to ensure adherence to the dual-date standard:
A. FILENAME DATE (System): Must use YYYY-MM-DD with hyphens. This ensures correct chronological sorting in digital directories.
Example: Scole-03-TRX-1996-07-13-218.txt
B. CONTENT DATE (Human): Must use DD/MM/YYYY with slashes within the file metadata and text body for British readability.
Example: Date of Session: 13/07/1996
-----
ARCHIVAL NOTES:
This item in the 01-ADM folder of the Scole Archive has been included for its potential usefulness to researchers when studying the archive content.
CROSS-REFERENCES:
- Scole-01-ADM-01-Archive-Folder-Structure.txt
- Scole-01-ADM-02-Master-Progress-Log (Internal Google Sheet)
=====
REVISION HISTORY:
v1.5 - 17/10/2026 - Updated structural dividers to 5-character and 3-character SANS responsive standard.
v1.4 - 05/10/2026 - Renamed file to include 'Master' for accuracy, updated cross-references to use filenames, and removed internal .xlsx extension.
v1.3 - 18/03/2026 - Clarified dual-date standard (System vs. Content).
v1.2 - 18/03/2026 - Updated to British Date Format and Plaintext standards.
v1.1 - 11/03/2026 - Added Archive-ID: Scole-01-ADM-GUI-03 for SANS consistency.
v1.0 - 08/03/2026 - Established AI-Assisted logging procedures for researchers.
=====
