DARIAH

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:

1. First, we must propose a new resource for each lesson to be added.
2. Fill in the fields in the following manner:

• Issue title: [new resource]: Lesson Title
• Title: Lesson Title
• Resource type: External Resource
• Authors, editors and contributors: All names, separated by commas
• Topics: [DH, Open Education, Open Access, + any relevant topics (see their list of topics)]
• Learning outcomes: Ideally, we can find these within the opening paragraphs of the lesson. Otherwise, they should be drafted as best as possible from the the lesson objectives. They should follow the format:

After completing this lesson, you will be able to:
- [Action verb in present tense] ...    
- [Action verb in present tense] ...  
- [Action verb in present tense] ...  

• Abstract: Use the lesson abstract

---

1. The next step is to log 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).
2. First, we need 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 first name under Collections (search all).
3. If the name is not found, go back to the main Contents page, and click People > New Person.
4. 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.
5. Now, this entry is visible in the Workflow tab, under In-review.
6. 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.

1. 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: Date of publication of the lesson/translation
• Version: 1.0.0
• Authors: Type in their first name and select the correct name from the list
• Editors: Type in their first name and select the correct name from the list
• Contributors: (Reviewers and translators) Type in the first name and select the correct name from the list
• Tags: Use the same tags provided in the Resource Proposal form in the fist step
• Sources: select only Programming Historian
• Featured image: Provide a large version of the image avatar, ideally found in the originals folder on Jekyll.
• Abstract: Lesson abstract as provided in the Resource Proposal form
• Contents: Toggle to 'Markdown'. First, write a longer introduction to the lesson, using the lesson abstract, introduction, and sometimes conclusion. Then, insert the heading ## Learning Outcomes in markdown, and follow with the Learning Outcomes as provided in the Resource Proposal form.
• Domain: Social Sciences and Humanities
• Target group: Domain Researchers
• Content type: Training Module
• Remote Host:
  • Publication date: Original date of publication of the lesson/translation
  • URL: Lesson DOI
  • Publisher: ProgHist Ltd
• Licence: CC-BY 4.0
• Show table of contents: Toggle to No
• Hide resource: Toggle to No