pick type of repository (TOOL, ETL, ANALYSIS, ADMIN)
[In two to three sentences state the purpose of this repository, ideally tying it to an existing SDAM milestone. E.g., The purpose of this repository is to provide templates for all future SDAM repositories in order to save precious time and maintain high standards and uniformity of our documentation.]
- Petra Hermankova , SDAM project, petra@ancientsocialcomplexity.org
- [Name], [ORCID], [Institution], [email]
- [Name], [ORCID], [Institution], [email]
- [Name], [ORCID], [Institution], [email]
CC-BY-SA 4.0, see attached License.md
[Here will be DOI or some other identifier once we have it]
[Here will go related articles or other sources we will publish/create]
[Describe the provenance of data used in the scripts contained and clarify how it is harvested and what other prerequisites are required to get the scripts working. In case of pure tool attribute any reused scripts to source, etc., license and specify any prerequisites or technical requirements.]
Anything else on data metadata and data used. Link to data repository or explanatory article.
- Software X, minimum version 123
- Software Y, version 456
- CompanyA
- CompanyB
- Multiple-screen
- Mouse
- Coffee
[Describe the steps necessary to install the tool/package; example: https://gist.github.com/PurpleBooth/109311bb0361f32d87a2]
[Describe first steps, how to use the current repository by a typical user - the digital historian with limited technical skills]
- First, do ...
- Second, do ...
- Third, go to ...