-
Notifications
You must be signed in to change notification settings - Fork 227
DARIAH
charlottejmc edited this page May 31, 2024
·
15 revisions
Our lessons by Programming Historian in English from 2022 onwards are indexed by DARIAH-Campus.
We send [quarterly?] updates using their GitHub-based CMS. DARIAH has their own documentation to help with the process. Follow the steps below for more details:
- Once logged into the DARIAH-Campus CMS using a GitHub username, you will see three tabs at the top of the page: Contents, Workflow and Media. Contents is the space to add new resources, while Workflow shows what has been saved as a draft (in the left-hand column), and what has been sent for publication that is waiting to be approved by the administrators (on the right-hand side).
- The first step is to add the missing People: authors, editors, translators and reviewers which have not yet been added to the CMS. To check whether they are already in the system, search their name under Collections (search all).
- If the name is not found, go back to the main Contents page, and click People > New Person.
- Fill in First Name and Last Name, and leave the rest blank. Click Save, then toggle the blue drop-down from Status: Draft to Status: In review.
- Now, this entry is visible in the Workflow tab, under In-review.
- You must submit every missing name needed for each batch, and wait until they are approved by the administrators, before you can move on to submitting the resources themselves.
Once these have been approved, we can move on to submitting the resources.
- Navigate to Contents > New resource and fill in the fields in the following manner:
- Title: [Full title]
- Short title (optional): Leave blank
- Language: English
- Publication Date: [Now]
- Version: 1.0.0
- 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