-
Notifications
You must be signed in to change notification settings - Fork 228
Tracking lesson phase changes
charlottejmc edited this page May 23, 2024
·
5 revisions
Contents of this page:
In order to keep track of each lesson's current phase, and be notified when a lesson phase has reached its agreed deadline, we use a simple Google Calendar workflow outlined below.
- Upon each phase change, the Publishing Manager posts a mermaid diagram in the lesson issue which outlines the current phase and the expected completion date for the work associated.
- The Publishing Manager navigates to Google Calendar and sets up a corresponding Event:
- TITLE: #XXX (issue number) – Phase X Deadline
- DATE: [Expected completion date as agreed in the issue] (no need to set a time)
- CALENDAR: either
EN Lesson Tracker
,ES Lesson Tracker
,FR Lesson Tracker
orPT Lesson Tracker
as appropriate - ADD GUESTS: invite the lesson editor by email
- The Publishing Manager, Publishing Assistant and Managing Editor for that journal are by default added to the event. All participants will receive a notification 1 week before the deadline, and another 1 day before the deadline. This will allow them to check into the issue and determine whether the work is likely to be completed on time.
- If the work has been completed by the agreed deadline, the Publishing Manager will move the lesson to the next phase and repeat the process.
- If the work is not yet completed, the team will coordinate within the issue to agree a new deadline, and update the Google Calendar event to reflect this change.
- Calendar name:
EN/ES/FR/PT Lesson Tracker
, [OR AS AGREED BY EACH JOURNAL] - Share with specific people or groups: includes the Publishing Manager, Publishing Assistant and Managing Editor for that journal
- All-day event notifications: 1 week before at 9:00am, and 1 day before at 9:00am
- Other notifications: email for New events, Changed events and Deleted events
- Copyediting
- Copyedit comments
- Typesetting
- Archival Hyperlinks
- Copyright
- DOI
- Gallery image
- Checklist comment
- Handover comment
- Closing comment
- Opening comment Phase 0
- Phase change comment 1 to 2
- Phase change comment 2 to 3
- Phase change comment 3 to 4
- Opening comment Phase 4
- Phase change comment 4 to 5
- Phase change comment 5 to 6
- Phase change comment 6 to 7
- Tracking lesson phase changes
- Organisational Structure
- Trustee Responsibilities
- Trustee and Staff Roles
- Services to Publications
- Funding
Training
- Onboarding-Process-for-New-Editors
- Leading-a-Shadowing-process
- Board-of-Director---Continuing-Development
The Ombudsperson Role
Technical Guidance
- Making Technical Contributions
- Creating Blog Posts
- Service Integrations
- Brand Guidelines
- French Translation Documentation
- Technical Tutorial on Translation Links
- Technical Tutorial on Setting Up a New Language
- Technical Tutorial on Search
- Twitter Bot
- Achieving-Accessibility-Alt-text-Colour-Contrast
- Achieving-Accessibility:-Training-Options
Editorial Guidance
- Achieving Sustainability: Copyediting, Typesetting, Archival Links, Copyright Agreements
- Achieving Sustainability: Lesson Maintenance Workflow
- Achieving Sustainability-Agreed-terminology-PH-em-português
- Training and Support for Editorial Work
- The-Programming-Historian-Digital-Object-Identifier-Policy-(April-2020)
- How to Request a New DOI
- Service-Agreement-Publisher-and-Publications
- ProgHist-services-to-Publications
- Technical Tutorial on Setting Up a New Language
- Editorial Recruitment
Social Guidance
Finances
- Project Costs
- Spending-Requests-and-Reimbursement
- Funding Opportunities
- Invoice Template
- Donations and Fundraising Policies
Human Resources
- Privileges-and-Responsibilities-of-Membership
- Admin-when-team-members-step-down
- Team-Leader-Selection-Process
- Managing-Editor-Handover
- Checklist-for-Sabbaticals
- New Publications Policy
- Parental-Leave-Policy
Project Management
Project Structure
Board of Trustees