We are happy to announce the publication of the latest instalment in our series “The School of Salamanca Working Papers” (ISSN 2509-5080):
The writings of Erasmus of Rotterdam (1466/69–1536) exerted a significant influence in 16th-century Spain. Based on classical and recent historiography, the present essay examines this religious and cultural phenomenon, with side glances at Luther: After sketching out the life and work of the Christian humanist, the second part deals with Erasmianism in Spain from its widespread reception in the 1520s (at the royal court, at universities and in translations) to the inquisitorial persecution of its followers since the 1530s. Thirdly, newer research trends are discussed that both correct and further develop the classical image shaped by Marcel Bataillon, also with regard to the ambivalent relationship between scholasticism and humanism. To demonstrate Erasmus’ influence in New Spain (Mexico), the final part of this essay turns its attention to the attitudes of (arch)bishops and friars as well as to early colonial case studies.
Continue reading “Otto Danwerth: Erasmus, christlicher Humanismus und Spiritualität in Spanien und Neu-Spanien (16. Jahrhundert)”
The idea: automatic depositing the project’s TEI files at Zenodo
We have been using the github-zenodo integration for a while already with our source code releases. This allows us to deposit our code, update the deposit with new releases and get a persistent identifier for each of the versions. Since we are facing similar requirements for our TEI XML files, I have investigated how we could take profit of this or a similar mechanism. The crucial difference is this: The integration as it is makes deposits from releases/snapshots of the whole github repository, i.e. of all the files that are in the version control system. This is good for software, where all the files depend on each other and make sense only in the context of an encompassing application. But for our TEI sources, it would be better to have deposits for individual files (and persistent identifiers for them) rather than for the collection as a whole.
So I have developed a “TEI2Zenodo” service (in the following just “t2z”) that can take care of uploading our files to zenodo. The idea is that a project or an institution that regularly wants to commit TEI XML files to long-term archival can host an instance of it and do its uploads via this instance. I have used it to upload 16 of our source TEI files automatically from our github repository.
Continue reading “TEI XML to Zenodo service published: Automatic depositing the project’s TEI files at a long-term archive”